Bug 1427666 – Cassandra logs don't contain date in timestamp

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1427666 - Cassandra logs don't contain date in timestamp

Summary:	Cassandra logs don't contain date in timestamp

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Hawkular (Show other bugs)
Sub Component:
Version:	3.5.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wringe
QA Contact:	Peng Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-02-28 15:42 EST by Matt Wringe
Modified:	2017-07-24 10 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-04-12 15:14:15 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0884	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.5 RPM Release Advisory	2017-04-12 18:50:07 EDT

Groups: None (edit)

Description Matt Wringe 2017-02-28 15:42:06 EST

The stdout logs for Cassandra do not contain the date timestamp, this can make it more difficult to determine when things have occurred from the logs.

Comment 1 Peng Li 2017-03-01 01:12:47 EST

Verified.

Version:
metrics-cassandra     3.5.0      cf1ab8076e6c        9 hours ago         543.7 MB

Part of log:

INFO  [SharedPool-Worker-7] 2017-03-01 06:05:45,976 MigrationManager.java:413 ....

THe whole Cassandra pod log is attched.

Comment 4 errata-xmlrpc 2017-04-12 15:14:15 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0884

Note You need to log in before you can comment on or make changes to this bug.