First date in logs wrong in New Year

Bug #319627 reported by eiffel
4
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(gdm:auth): cannot determine username
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(gdm:session): session opened for user maff by (uid=0)

Looks like the Jan 1st entries are really Jan 5th.

Could this have something to do with the Leap Second adjustment?

Revision history for this message
David Tombs (dgtombs) wrote :

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.

affects: ubuntu → sysklogd (Ubuntu)
Changed in sysklogd (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for sysklogd (Ubuntu) because there has been no activity for 60 days.]

Changed in sysklogd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.