Ask Your Question

Craig's profile - activity

2017-03-10 11:09:47 -0600 commented question How can I find what called for a reboot.

I'm going to assume an update on 3/6/2017 fixed what ever the problem was. My machine has been working since that update. I just wish I could have seen something in the logs that showed the problem.

2017-03-08 11:46:27 -0600 commented question How can I find what called for a reboot.

I don't think so. The computer stayed up since the reboot yesterday morning. One thing I noticed today is my LAN is different. It has been enp2s0 and now its enp3s0. I'm not sure which scripts you're referring to but some of it is me using Putty from my laptop to log in and monitor.

2017-03-07 12:47:57 -0600 commented question How can I find what called for a reboot.

Posted above thanks.

2017-03-07 12:36:32 -0600 received badge  Editor (source)
2017-03-06 14:54:50 -0600 commented question How can I find what called for a reboot.

I have rebooted/crashed approximately 12 times since Friday.

2017-03-06 14:40:36 -0600 commented question How can I find what called for a reboot.

I'm still trying to track this down. I have monitored the sensors and the highest temp I saw was 41* C for an instant then back down to 31*C. I don't think its temp related. The logs are different each time and the time of day is not consistent. I brought the computer to the shop (hoping it was a hardware issue) but they didn't find anything relating to hardware. I wonder if my best bet is to reinstall.

2017-02-21 09:42:00 -0600 commented question How can I find what called for a reboot.

I'm using Fedora 25 with Gnome. Is there a way to log the temp in Fedora? The power should be stable its on battery backup.

2017-02-20 21:23:05 -0600 received badge  Student (source)
2017-02-20 20:07:10 -0600 asked a question How can I find what called for a reboot.

Over the weekend my system rebooted on its own. The reboot hung and when I came in to work Monday I had to kill the system and start over. I looked in journalctl and didn't see anything interesting. the last three entries were from audit [7811] USERAUTH, USERACCT & CRED_ACQ all res=success. The next line is --Reboot-- . My system is Gigabyte H170M-DS3H with Intel i5-6500 using Raid 1.

Out put of Journalctl -xe after a reboot this morning.

-- The start-up result is done.
Mar 07 10:18:19 Server2 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/syst
Mar 07 10:18:19 Server2 nm-dispatcher[3941]: req:1 'dhcp4-change' [enp3s0]: new request (6 scripts)
Mar 07 10:18:19 Server2 nm-dispatcher[3941]: req:1 'dhcp4-change' [enp3s0]: start running ordered scripts...
Mar 07 10:18:19 Server2 dhclient[1276]: bound to 192.168.101.5 -- renewal in 1715 seconds.
Mar 07 10:18:29 Server2 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/syste
Mar 07 10:22:32 Server2 audit[3969]: CRYPTO_KEY_USER pid=3969 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=server fp=SHA256:a2:58:b3:51:42:b1:20:57:11:c4:1
Mar 07 10:22:32 Server2 audit[3969]: CRYPTO_KEY_USER pid=3969 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=server fp=SHA256:2a:cc:9e:ab:de:63:12:44:21:be:c
Mar 07 10:22:32 Server2 audit[3969]: CRYPTO_KEY_USER pid=3969 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=server fp=SHA256:3e:f8:f7:8e:f2:e6:d1:51:d8:cb:8
Mar 07 10:22:32 Server2 audit[3968]: CRYPTO_SESSION pid=3968 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-server cipher=aes256-ctr ksize=256 mac=hm
Mar 07 10:22:32 Server2 audit[3968]: CRYPTO_SESSION pid=3968 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-client cipher=aes256-ctr ksize=256 mac=hm
Mar 07 10:22:38 Server2 audit[3968]: USER_AUTH pid=3968 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/sbin/ssh
Mar 07 10:22:38 Server2 audit[3968]: USER_ACCT pid=3968 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="root" exe="/us
Mar 07 10:22:38 Server2 sshd[3968]: Accepted password for root from 192.168.101.25 port 53979 ssh2
Mar 07 10:22:38 Server2 audit[3968]: CRYPTO_KEY_USER pid=3968 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=session fp=? direction=both spid=3969 suid=74 rp
Mar 07 10:22:38 Server2 audit[3968]: USER_AUTH pid=3968 uid=0 auid=4294967295 ses=4294967295 msg='op=success acct="root" exe="/usr/sbin/sshd" hostname=? addr=192.168.10
Mar 07 10:22:38 Server2 audit[3968]: CRED_ACQ pid=3968 ...
(more)