[ https://issues.apache.org/jira/browse/CASSANDRA-12004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394461#comment-15394461 ]
Paulo Motta commented on CASSANDRA-12004: ----------------------------------------- Sorry for the delay here, this slipped through the cracks. Patch LGTM, will mark as ready to commit after CI results look good: ||trunk|| |[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-12004]| |[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-12004-testall/lastCompletedBuild/testReport/]| |[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-12004-dtest/lastCompletedBuild/testReport/]| > Inconsistent timezone in logs > ----------------------------- > > Key: CASSANDRA-12004 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12004 > Project: Cassandra > Issue Type: Bug > Reporter: Jérôme Mainaud > Priority: Trivial > Fix For: 2.1.x > > Attachments: 12004-trunk.patch2.txt, patch.txt > > > An error in provided logback.xml lead to inconsistent timestamp usage in logs. > In log files, local time zone is used. > On the console, UTC time zone is used (and millisconds are missing.) > Example, the same log line (Local time zone: CEST) : > in system.log > {code} > INFO [main] 2016-06-14 14:01:51,638 StorageService.java:2081 - Node > localhost/127.0.0.1 state jump to NORMAL}} > {code} > in console > {code} > INFO 12:01:51 Node localhost/127.0.0.1 state jump to NORMAL > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)