First date in logs wrong in New Year
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysklogd (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Over the New Year my computer was turned off and physically unplugged.
Looking at messages.0, I have:
Jan 1 00:01:23 intelp3pc syslogd 1.5.0#2ubuntu6: restart.
through to
Jan 1 00:01:34 intelp3pc kernel: [ 42.908413] NET: Registered protocol family 17
the next log entry being
Jan 5 22:28:23 intelp3pc pulseaudio[5536]: ltdl-bind-now.c: Failed to find original dlopen loader.
i believe the second date to be accurate
looking at auth.log, I have:
Dec 18 16:32:45 intelp3pc gdm[4981]: pam_nologin(
Jan 1 00:01:25 intelp3pc sshd[4543]: Server listening on :: port 22.
Jan 1 00:01:25 intelp3pc sshd[4543]: Server listening on 0.0.0.0 port 22.
Jan 5 22:28:20 intelp3pc gdm[5063]: pam_unix(
Looks like the Jan 1st entries are really Jan 5th.
Could this have something to do with the Leap Second adjustment?
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.