Re: what just happened (time went backwards?)

[Chris Murphy <lists@xxxxxxxxxxxxxxxxx>]

On Feb 25, 2014, at 11:58 AM, Dale Dellutri <daledellutri@xxxxxxxxx> wrote:

On Tue, Feb 25, 2014 at 12:30 PM, Neal Becker <ndbecker2@xxxxxxxxx> wrote:

This f20 server has been running just fine for months.  Today it became
unresponsive.  Couldn't ssh into it (ping ok).  Not thrashing disk (disk light
not continuously on).

I hit the power button and rebooted.  After reboot, checked /var/log/messages:

Feb 25 12:06:18 nbecker7 kernel: [   49.667251] tun: Universal TUN/TAP device
driver, 1.6
Feb 25 12:06:18 nbecker7 kernel: [   49.667254] tun: (C) 1999-2004 Max
Krasnyansky <maxk@xxxxxxxxxxxx>
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...
Jan  8 10:48:32 nbecker7 systemd: Stopping OpenSSH server daemon...

How did the date just become Jan 8??

It didn't.  Systemd is in control, and /var/log/messages is no longer necessarily

written in order.  You need to use journalctl to read the log for F20.

Ahh I didn't pick up on these being from messages. 

journalctl -b  --no-pager     # for the current boot

journalctl -b -1 --no-pager  # for the boot before current, -2 for the one before that, -3, -4, etc.

To get more information

journalctl -xb

It can also be piped

journalctl -b -1 | grep -i time

systemd itself doesn't manage or change time.

Chris Murphy

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org