Bug 1427666 - Cassandra logs don't contain date in timestamp
Summary: Cassandra logs don't contain date in timestamp
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matt Wringe
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-28 20:42 UTC by Matt Wringe
Modified: 2017-07-24 14:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-12 19:14:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0884 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 22:50:07 UTC

Description Matt Wringe 2017-02-28 20:42:06 UTC 
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 06:12:47 UTC 
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 19:14:15 UTC 
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.