Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rame syslog entries have wrong timestamp #58

Open
jlauha opened this issue Jun 16, 2018 · 2 comments
Open

Rame syslog entries have wrong timestamp #58

jlauha opened this issue Jun 16, 2018 · 2 comments
Labels
bug NICE

Comments

@jlauha
Copy link
Contributor

jlauha commented Jun 16, 2018 •
edited
Loading

In the current 1.2.0 release (possibly some earlier ones as well), all syslog entries are marked with "Jan 1 03:59:59" timestamp.

The system clock and hw clock all work fine, there doesn't seem to be issue with them. Also, if some entirely different process opens and writes to syslog, the timestamps are correct.
jlauha added a commit to rameplayerorg/rameplayer-alpine that referenced this issue Apr 13, 2019
@jlauha
Workaround for wrong timestamp in syslog entries.
359e34c 
See:
rameplayerorg/rameplayer-backend#58
https://bugs.alpinelinux.org/issues/8028
@jlauha
Copy link
Contributor Author

jlauha commented Apr 13, 2019

The above workaround fixes the issue with timestamps always being marked with same date/time.

But with the workaround the timestamps won't be in local time but in UTC time instead.

@jlauha
Copy link
Contributor Author

jlauha commented Apr 13, 2019

https://bugs.alpinelinux.org/issues/8028

@jlauha jlauha removed the IMPORTANT label Apr 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug NICE
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jlauha