You are not logged in.

#1 2018-03-24 14:31:45

boogiewoogie
Member
Registered: 2017-03-30
Posts: 11

Random shutdown?

Hey everybody,

I've got a strange issue: my system shuts down (properly as it seems, I get the usual shutdown text) without me being able to make sense of it.


Two cases so far:

- When I tried to compile something (the Rust package), it would shutdown many times at roughly the same part of the compilation. This has then magically worked at a later time.

- It shut down without me doing anything which feels relevant. I just clicked on another firefox tab that was open already and being used seconds before.


The arch installation is completely fresh on a Lenovo T400s, using xfce4. This is the latest part of the output of $ journalctl --since=today:

Mar 24 14:53:11 woogie dbus-daemon[4015]: [session uid=1000 pid=4015] Successfully activated service 'org.gnome.GConf'
Mar 24 15:10:45 woogie systemd[3972]: Stopping Accessibility services bus...
Mar 24 15:10:45 woogie systemd[3972]: Stopping Sound Service...
Mar 24 15:10:45 woogie gpg-agent[4031]: SIGTERM received - shutting down ...
Mar 24 15:10:45 woogie systemd[3972]: Stopping XFCE notifications service...
Mar 24 15:10:45 woogie systemd[3972]: Stopping GnuPG cryptographic agent and passphrase cache...
Mar 24 15:10:45 woogie systemd[3972]: Stopped target Default.
Mar 24 15:10:45 woogie systemd[3972]: Stopping D-Bus User Message Bus...
Mar 24 15:10:45 woogie gpg-agent[4031]: gpg-agent (GnuPG) 2.2.5 stopped
Mar 24 15:10:45 woogie systemd[3972]: Stopped GnuPG cryptographic agent and passphrase cache.
Mar 24 15:10:45 woogie systemd[3972]: Stopped XFCE notifications service.
Mar 24 15:10:45 woogie systemd[3972]: Stopped D-Bus User Message Bus.
Mar 24 15:10:46 woogie pulseaudio[4035]: W: [pulseaudio] module-x11-publish.c: PulseAudio information vanished from X11!
Mar 24 15:10:46 woogie pulseaudio[4035]: XIO:  fatal IO error 1 (Operation not permitted) on X server ":0.0"
Mar 24 15:10:46 woogie pulseaudio[4035]:       after 12 requests (6 known processed) with 0 events remaining.
Mar 24 15:10:46 woogie systemd[3972]: Stopped Accessibility services bus.
Mar 24 15:10:46 woogie systemd[3972]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Mar 24 15:10:46 woogie systemd[3972]: pulseaudio.service: Failed with result 'exit-code'.
Mar 24 15:10:46 woogie systemd[3972]: Stopped Sound Service.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Basic System.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Timers.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Paths.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Sockets.
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 15:10:46 woogie systemd[3972]: Closed D-Bus User Message Bus Socket.
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG network certificate management daemon.
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 24 15:10:46 woogie systemd[3972]: Closed Sound System.
Mar 24 15:10:46 woogie systemd[3972]: Reached target Shutdown.
Mar 24 15:10:46 woogie systemd[3972]: Starting Exit the Session...
Mar 24 15:10:46 woogie systemd[3972]: Started Exit the Session.
Mar 24 15:10:46 woogie systemd[3972]: Received SIGRTMIN+24 from PID 12637 (n/a).
-- Reboot --
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 24 15:11:37 woogie systemd[688]: Starting D-Bus User Message Bus Socket.
Mar 24 15:11:37 woogie systemd[688]: Reached target Timers.
Mar 24 15:11:37 woogie systemd[688]: Reached target Paths.
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG network certificate management daemon.
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 15:11:37 woogie systemd[688]: Listening on Sound System.
Mar 24 15:11:37 woogie systemd[688]: Listening on D-Bus User Message Bus Socket.
Mar 24 15:11:37 woogie systemd[688]: Reached target Sockets.
Mar 24 15:11:37 woogie systemd[688]: Reached target Basic System.
Mar 24 15:11:37 woogie systemd[688]: Reached target Default.
Mar 24 15:11:37 woogie systemd[688]: Startup finished in 37ms.
Mar 24 15:11:59 woogie systemd[688]: Started D-Bus User Message Bus.
Mar 24 15:11:59 woogie dbus-daemon[967]: [session uid=1000 pid=967] Activating service name='org.xfce.Xfconf' requested by ':1.2' (uid=1000 pid=969 comm="xfce4-session ")
Mar 24 15:11:59 woogie dbus-daemon[967]: [session uid=1000 pid=967] Successfully activated service 'org.xfce.Xfconf'
Mar 24 15:11:59 woogie systemd[688]: Started GnuPG cryptographic agent and passphrase cache.
Mar 24 15:11:59 woogie gpg-agent[983]: gpg-agent (GnuPG) 2.2.5 starting in supervised mode.
Mar 24 15:11:59 woogie gpg-agent[983]: using fd 3 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Mar 24 15:11:59 woogie gpg-agent[983]: using fd 4 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Mar 24 15:11:59 woogie gpg-agent[983]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Mar 24 15:11:59 woogie gpg-agent[983]: using fd 6 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Mar 24 15:11:59 woogie gpg-agent[983]: listening on: std=3 extra=5 browser=6 ssh=4
Mar 24 15:11:59 woogie systemd[688]: Starting Sound Service...
Mar 24 15:11:59 woogie systemd[688]: Started Sound Service.
Mar 24 15:12:00 woogie dbus-daemon[967]: [session uid=1000 pid=967] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.11' (uid=1000 pid=998 comm>
Mar 24 15:12:00 woogie tumblerd[1008]: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.7: cannot open shared object file: No such file or directory
Mar 24 15:12:00 woogie tumblerd[1008]: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
Mar 24 15:12:00 woogie tumblerd[1008]: Failed to load plugin "tumbler-odf-thumbnailer.so": libgsf-1.so.114: cannot open shared object file: No such file or directory
Mar 24 15:10:46 woogie systemd[3972]: pulseaudio.service: Failed with result 'exit-code'.
Mar 24 15:10:46 woogie systemd[3972]: Stopped Sound Service.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Basic System.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Timers.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Paths.
Mar 24 15:10:46 woogie systemd[3972]: Stopped target Sockets.
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 15:10:46 woogie systemd[3972]: Closed D-Bus User Message Bus Socket.
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG network certificate management daemon.
Mar 24 15:10:46 woogie systemd[3972]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 24 15:10:46 woogie systemd[3972]: Closed Sound System.
Mar 24 15:10:46 woogie systemd[3972]: Reached target Shutdown.
Mar 24 15:10:46 woogie systemd[3972]: Starting Exit the Session...
Mar 24 15:10:46 woogie systemd[3972]: Started Exit the Session.
Mar 24 15:10:46 woogie systemd[3972]: Received SIGRTMIN+24 from PID 12637 (n/a).
-- Reboot --
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 24 15:11:37 woogie systemd[688]: Starting D-Bus User Message Bus Socket.
Mar 24 15:11:37 woogie systemd[688]: Reached target Timers.
Mar 24 15:11:37 woogie systemd[688]: Reached target Paths.
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG network certificate management daemon.
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 15:11:37 woogie systemd[688]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 15:11:37 woogie systemd[688]: Listening on Sound System.
Mar 24 15:11:37 woogie systemd[688]: Listening on D-Bus User Message Bus Socket.
Mar 24 15:11:37 woogie systemd[688]: Reached target Sockets.
Mar 24 15:11:37 woogie systemd[688]: Reached target Basic System.
Mar 24 15:11:37 woogie systemd[688]: Reached target Default.
Mar 24 15:11:37 woogie systemd[688]: Startup finished in 37ms.
Mar 24 15:11:59 woogie systemd[688]: Started D-Bus User Message Bus.
Mar 24 15:11:59 woogie dbus-daemon[967]: [session uid=1000 pid=967] Activating service name='org.xfce.Xfconf' requested by ':1.2' (uid=1000 pid=969 comm="xfce4-session ")
lines 80-99/133 69%

Remember this was ONE shutdown (eventhough somehow there's several reboots listed there. The timestamps confirm it can only have been one). I've included the first line there to put it in chronological context.
I cannot make sense of this. Maybe one of you guys can?

Cheers,
boogie

Offline

#2 2018-03-24 15:51:40

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,304

Re: Random shutdown?

What you see is the user journal, not all the system journal ('systemd[688]' is the user manager, different from 'systemd[1]').
Either add the user to the group "systemd-journal" or run the command as root.
And 'since=today' will list all the journal entries from '00:00' independently of the number of shutdowns/boots.
Rather run 'journalctl -b' for last boot entries or 'journalctl -b -1' for the previous boot entries.

As for your initial problem, it seems a hardware problem.
Try a live distro to confirm that, and start by checking the memory.

Offline

#3 2018-03-26 10:45:24

boogiewoogie
Member
Registered: 2017-03-30
Posts: 11

Re: Random shutdown?

Okay, I've checked the journal as root, that was super helpful. It actually said my CPU reached critical temperature, so your hardware assumption was correct!

I have renewed the thermal glue and haven't encountered such a problem since. Thanks again for your help. smile

Offline

#4 2018-03-26 10:48:53

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: Random shutdown?

Please remember to mark this thread [SOLVED].
CoC - How to post


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

Board footer

Powered by FluxBB