First thing I would check is the CMOS battery if you have one or can get to
it. Sounds like system time is not being held. Go through boot log. If the
system corrects shortly after a. Nts comes up and b. Network connection is
established then this may be the case. Couple dollars for a button battery
will have you right.
Fred Roller
On Jul 24, 2016 1:00 AM, "Stephen Davies" <sdavies(a)sdc.com.au> wrote:
My F22 randomly crashes to a frozen state that requires a power cycle
to
restart.
When this happens, the time stamp on log files such as /var/log/messages
changes for a while before reverting to the correct date and time.
Today,the sequence was:
Jul 24 10:55:55 mustang rsyslogd: [origin software="rsyslogd"
swVersion="8.8.0" x-pid="853"
x-info="http://www.rsyslog.com"] start
Jul 15 11:19:20 mustang systemd: Stopped target Default.
Jul 15 11:19:25 mustang systemd: Stopping Default.
followed by some 17,000 lines with Jul 15 through to:
Jul 15 19:28:11 mustang named[1221]: client 122.61.143.143#39431 (
isc.org):
query (cache) 'isc.org/ANY/IN' denied
Jul 24 10:56:14 mustang rsyslogd-2177: imjournal: begin to drop messages
due to rate-limiting
Sun Jul 24 10:56:16 ACST 2016 rc.fw
Jul 24 11:06:11 mustang rsyslogd-2177: imjournal: 2971956 messages lost
due to rate-limiting
A similar thing happens in /var/log/secure (though with fewer Jul 15
entries).
The Jul 15 dates have been appearing at/after the last two or three
crashes.
Even though the Jul 15 entries look to span over eight hours, the actual
time span was only a minute or so.
Any suggestions as to what is happening here?
Cheers and thanks,
Stephen
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
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