Unless you took a backup I guess it's not relevant anymore but if it happens again you can narrow down files last changed around some timestamp like so: find /var -mmin +4 -mmin -5
I always forget that find is that flexible. Thanks.
In the offchance that shenanigans are afoot, some malware will fudge mtimes (but not always ctimes) to prevent detection.
If you get files showing up as changed with -cmin but not modified with -mmin, that's a bright red one.
Which logs did you look at already?
If you're using journalctl, I think you should have shutdown messages in the log. You might need to filter by the previous boot for them though (https://linuxhandbook.com/journalctl-boot-logs/).
For dmesg, you might have old, rotated logs from previous boots in your /var/logs folder.
I'd expect any logs around power management to end up in one or both of those places.
You could also try manually triggering a suspend or hibernate to see what happens. I remember having a machine that would suspend fine, but if it was suspended too long, it would hibernate. And for some reason it didn't know how to come back up after a hibernate.
I think I'm just going to keep an eye on it and see if it happens again, since this is the first time it's ever shut itself down unprompted like this. My cat has also figured out where the power button is and likes to press it occasionally, so unless it happens again I'm just going to chalk it up to that. Might replace the PSU just for good measure, since it's getting kinda old and was made by EVGA, about whose reliability I'm entirely ignorant.
journalctl -b -1 will show you the logs from the previous boot. journalctl -k -b -1 will do the same for the kernel logs. If you've rebooted again since, just use -2 instead of -1.
Even better do journalctl -r -b -1 to get the latest logs first
Or you can just do journalctl -r --since "5min ago" if it just happened
When this happens to me I mostly assume Linux shutdown automatically because of a critical over temperature event. I've seen it in the logs a few times but I don't usually check anymore.
There's an example of this here https://unix.stackexchange.com/questions/502226/how-do-you-find-out-if-a-linux-machine-overheated-before-the-previous-boot-and-w
Does it happen at a consistent time or frequency? Like at 8pm or after 2 hours of being turned on?
The last few weeks I've had a similar problem and I can't find a solution. Same installation of manjaro for around 7 years. I made no system setting changes. All I do is update the system with the package manager. When I check some systemd logs or dmesg it all looks normal except from wake it mentions something about an unresponsive disk, but it always works fine after the second wake or if I just shut it down and then boot it up. It's only a problem from suspend to wake. I can type in my password and log in but it pretty much seems after 10 seconds it suspends itself again for the first time.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0