crwdns2915892:0crwdne2915892:0
It's not uncommon for a Linux system to restart unexpectedly due to a software or hardware error, however finding and fixing the core cause of the issues may help prevent it in the future.
This guide will demonstrate one such method for finding the cause for a restart using some of the built in software that is preinstalled in Kali Linux.
-
-
Press Ctrl + Alt + T to open the Terminal Interface.
-
-
-
Enter the command sudo mkdir /var/log/journal
-
-
-
-
Enter the command: sudo systemd-tmpfiles --create --prefix /var/log/journal 2>/dev/null
-
-
-
sudo systemctl -s SIGUSR1 kill systemd-journald
-
-
-
See your logged boots from your journal with the following: journalctl --list-boots
-
Locate a specific reboot using this command: journalctl -b {num} -n
-
Optionally you can use killall -USR1 systemd-journald rather than restarting your services. This way a user can keep all the logging from the current session.
Optionally you can use killall -USR1 systemd-journald rather than restarting your services. This way a user can keep all the logging from the current session.
crwdns2935221:0crwdne2935221:0
crwdns2935227:0crwdne2935227:0
