this post was submitted on 24 Jan 2025
21 points (100.0% liked)
Linux
49244 readers
775 users here now
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
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Someone already linked to journalctl, but if you just quickly want to look, the command journalctl and the flag —since will get you going.
Journalctls output can be piped, so if you know what you’re looking for you can grep it easily.
Yeah I really don't know that I'm looking for unfortunately. I was something would jump out at me. I'm pretty new to Linux altogether so I'm kind of winging a lot
So go ahead and take a look at your journalctl output. The left hand side should be timestamps, so you can immediately figure out if it’s starting a million years in the past or sometime you know you had the problem.
If it is a million years in the past, use the —since flag and specify the time you want to start at as enumerated in the manual file (man journalctl).
Once you’re looking at the logs in journalctl from a day you know the problem happened, go ahead and use arrow keys and pgup/pgdn to find a reboot. You’ll know when you find a reboot because it’ll look different. The messages will be about figuring out what hardware is attached and changing runlevels and whatnot.
Once you found where the reboot is, go backwards to find something weird happening in the logs.
E: By default the parser (program used to handle text) of journalctls output is “less”. If you want to get out of it, press “q”, and if you want to know more “man less”.
I greatly appreciate the additional info. I'll finally be able to take a look in the morning. Hopefully I find something obvious and easy to fix lol