Chris Murphy wrote:
On Feb 25, 2014, at 11:45 AM, Neal Becker <ndbecker2(a)gmail.com> wrote:
>
> Don't know if it's related, but I just saw this:
>
> Feb 25 12:06:18 nbecker7 kernel: [ 59.015938] Ebtables v2.0 registered
> Feb 25 12:06:18 nbecker7 kernel: [ 59.601221] ip6_tables: (C) 2000-2006
> Netfilter Core Team
> Feb 25 12:06:18 nbecker7 kernel: [ 65.646938] Bridge firewalling registered
> Feb 25 12:06:18 nbecker7 kernel: [ 65.671316] device virbr0-nic entered
> promiscuous mode
> Feb 25 12:06:18 nbecker7 kernel: [ 66.410670] virbr0: port 1(virbr0-nic)
> entered listening state
> Feb 25 12:06:18 nbecker7 kernel: [ 66.410678] virbr0: port 1(virbr0-nic)
> entered listening state
> Feb 25 12:06:18 nbecker7 kernel: [ 66.410724] IPv6: ADDRCONF(NETDEV_UP):
> virbr0: link is not ready
> Feb 25 12:06:18 nbecker7 kernel: [ 66.668588] virbr0: port 1(virbr0-nic)
> entered disabled state
> Feb 25 12:06:54 nbecker7 kernel: [ 109.855407] fuse init (API version 7.22)
> Jan 8 10:48:32 nbecker7 systemd: Stopped target Graphical Interface.
> Jan 8 10:48:32 nbecker7 systemd: Stopping Multi-User System.
> Jan 8 10:48:32 nbecker7 systemd: Stopped target Multi-User System.
> Jan 8 10:48:32 nbecker7 systemd: Stopping ABRT kernel log watcher...
> Jan 8 10:48:32 nbecker7 systemd: Stopping Command Scheduler...
> Jan 8 10:48:32 nbecker7 systemd: Stopping Install ABRT coredump hook...
> Jan 8 10:48:32 nbecker7 systemd: Stopping ABRT Xorg log watcher…
Yeah I'd see if the journal has these date/time changes or if it's just in
/var/log/messages - it might be a rsyslog bug. Is the time really changing?
timedatectl
Chris Murphy
Here's what might be a big clue:
Just after the hunk of prehistoric lines, when we get back to Feb, the 1st thing
I see is:
Feb 25 12:07:55 nbecker7 rsyslogd-2177: imjournal: begin to drop messages due to
rate-limiting
Feb 25 12:18:40 nbecker7 rsyslogd-2177: imjournal: 145977 messages lost due to
rate-limiting
Seems very suspicious to me.
journalctl doesn't seem to show time warps.