Linux why did server reboot

Thanks, Mahesh. Jalal Hajigholamali Posted June 17, 0 Comments. Rupesh kumar Posted June 19, 0 Comments. Register or Login. Welcome back! Reset Your Password We'll send an email with a link to reset your password. Stay ahead! Get the latest news, expert insights and market research, tailored to your interests. Sign in with email Enter the email address associated with your account. You auth link is expired or incorrect, please try again. Sign up with email Get the latest news, expert insights and market research, tailored to your interests.

I'm not aware of any technology that can reliably collect that information. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Can you elaborate on how the output of dmesg is supposed to help?

My machine has just randomly rebooted, and if I understand your suggestion right, then dmesg cannot help here, right? Running last reboot showed that the kernel version was usually newer after the sudden reboots: reboot system boot 4. Sign up or log in Sign up using Google. Sign up using Facebook.

Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.

Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile.

Linked 8. Related 1. Hot Network Questions. Question feed. Here's an example of how to do it. Example output:. Note: If you're trying to diagnose a potential crash right now, this will not help unless you have previously configured systemd to persist the journal to disk. Optionally use journalctl --list-boots to get a list of boots in ascending chronological order 0 refers to current runtime logs since the system was booted; -1 covers logs from the previous boot; -2 the boot before that, etc Example:.

Use journalctl -b -1 -n to look at the last 10 lines of the previous boot The following example output shows that the previous system reboot was graceful. Note from the author: In my experiences troubleshooting RHEL 7 problems for customers in Red Hat support in the years leading up to when I wrote this article , this was somewhat less reliable than the other methods. When bad things happen, it was definitely possible for the indexing in journald to get so bad that the journalctl -b -1 command only gives an error.