Difficulty

Easy

Steps

5

Time Required

                          5 minutes

Sections

1

  • How to determine the cause for a restart in Kali Linux
  • 5 steps

Flags

2

Needs More Images

A few more images would make this guide’s procedures crystal clear.

Member-Contributed Guide

An awesome member of our community made this guide. It is not managed by iFixit staff.

  • BackKali

  • Full Screen

  • Options

  • History

  • Save to Favorites

  • Download PDF

  • Edit

  • Translate

  • Get Shareable Link

  • Embed This Guide

  • Notify Me of Changes

  • Stop Notifications

Introduction

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.

Step 1

              Open Kali's command line Terminal
  • Press Ctrl + Alt + T to open the Terminal Interface.

Press Ctrl + Alt + T to open the Terminal Interface.

1024

Step 2

              Create your journal directory
  • Enter the command sudo mkdir /var/log/journal

Enter the command sudo mkdir /var/log/journal

Step 3

              Create your prefix
  • Enter the command: sudo systemd-tmpfiles –create –prefix /var/log/journal 2>/dev/null

Enter the command: sudo systemd-tmpfiles –create –prefix /var/log/journal 2>/dev/null

Step 4

              Restart system-journald
  • sudo systemctl -s SIGUSR1 kill systemd-journald
  • Once this command is run, you will need to restart your machine to get your current system logs.

sudo systemctl -s SIGUSR1 kill systemd-journald

Once this command is run, you will need to restart your machine to get your current system logs.

Step 5

              Retrieving your system logs
  • See your logged boots from your journal with the following: journalctl –list-boots
  • Locate a specific reboot using this command: journalctl -b {num} -n

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.

Cancel: I did not complete this guide.

                                                                                      One other person completed this guide.

Author

                                      with 1 other contributor 


                    Jacob Mehnert

Member since: 10/18/2021

12,621 Reputation

                                      31 Guides authored                  



                       Badges:
                       42







                                                        +39 more badges

Team

                       iFanatics                        

                                                  Member of iFanatics 



                    Community                     


                                            49 Members                     


                                            102 Guides authored