My my work system in power off state today, but i left it running yesterday .

English Install/Boot/Login
1

Hi,
as stated in the topic, i found my work pc (opensuse tumbleweed) in the power off state today but i left it running yesterday and also had ssh access from home in the evening.
I want to find out what is the reason for that, especially i want to rule out that it was heat related.

My only idea was to run journalctl, i scolled down to the last entrys from yesterday, which were:

Jan 10 00:26:16 WORKPC sshd[20163]: Received disconnect from xxx.xxx.xxx.xxx port yyyyy:11: disconnected by user
Jan 10 00:26:16 WORKPC sshd[20163]: Disconnected from xxx.xxx.xxx.xxx port yyyyy
Jan 10 02:22:30 WORKPC systemd[20147]: pam_unix(systemd-user:session): session closed for user sabo
Jan 10 02:22:30 WORKPC systemd[20146]: Reached target Shutdown.
Jan 10 02:22:30 WORKPC systemd[20146]: Stopped target Default.
Jan 10 02:22:30 WORKPC systemd[20146]: Stopped target Basic System.
Jan 10 02:22:30 WORKPC systemd[20146]: Stopped target Sockets.
Jan 10 02:22:30 WORKPC systemd[20146]: Starting Exit the Session...
Jan 10 02:22:30 WORKPC systemd[20146]: Stopped target Paths.
Jan 10 02:22:30 WORKPC systemd[20146]: Stopped target Timers.
Jan 10 02:22:30 WORKPC systemd[20146]: Received SIGRTMIN+24 from PID 20518 (kill).

The first two entrys are from my ssh session, everything looks normal, then two hours later the system seems to shutdown but why?
Is there a way to find out?
btw. the running session for sabo was the session i left running as i leaved the office yeserday.

2

Was the screen locked? Else I would bet that somebody passed by and did it.
BTW, IIRC, shutdown can also be started from a locked screen can’t it?

3

Short power disruption tends to shut things off :open_mouth:

4

The screen was locked yes. Is there a way to find out if there was a manual shutdown (directly or remotely from the it department) or a power disruption?
I just what to find out if there is something i have to keep an eye one (like a hardware problem) or if it was something harmless or a one-time event.

5

Check the desktop environment’s power / energy settings, whether they are set to shutdown after X minutes of inactivity,

6

No it is not, also this system in not new and never did that before.

7

No way to really know if the power went out unless some one was watching or you have some form of power line monitor. Also if some one just shut it down with the power button or pulled the plug. Shutting down with software should leave traces in the logs but generally you have to be root or you have set users to be able to shutdown. Doubtful any over heat on an idle machine. You can run top in a console to see CPU usage. Power is proportionate to CPU/GPU usage

8

But in my understanding the log makes it clear that there was a regular shutdown, at least the running session was ended an the system reached the shutdown target. I think both events have the same reason.
If there was a power failure there should not be any log entries, right?

So when there was a regular shutdown, then there should by any log about where it was initiated. If it was a shell command, or a process. I cannot image that this stuff is not logged somewhere.

9

Yes, there should be some clues from the last boot. For example…

journalctl -b -1 -n200

You may need to adjust the number of messages to suit eg -n250

10

This is user session log, do not be confused. It has nothing to do with system shutdown.