3 Effective Methods to Reboot a Linux Server from the Command Line

Written by

Ojash

Reviewed by

Akshat

Last updated: July 10, 2023

Expert verified

Rebooting a Linux server may seem like a simple task, but its significance goes far beyond just a system restart. It serves as a vital maintenance procedure that keeps your server running smoothly and optimally. From resolving software glitches and memory leaks to freeing up system resources and improving overall performance, rebooting a Linux server is the secret sauce to maintaining a stable and high-performing server environment. In this comprehensive guide, I will explore different methods to reboot a Linux server, how to do scheduled reboots, best practices to follow, and common errors that can occur during the process.

How to Reboot a Linux Server

To reboot a Linux server from the command line, you have three methods at your disposal. The reboot command offers a quick and immediate reboot, while the shutdown command provides more control and scheduling options. If your server becomes unresponsive, you can use SysRq Magic Keys to trigger a reboot after switching to raw mode, sending signals, syncing file systems, and remounting them.

1. reboot Command

The reboot command is a simple and straightforward way to reboot a Linux server. It is best used when you need to initiate a quick and immediate reboot of the server. Follow these steps:

1. Open the command line interface.

2. Execute the following command: 

<strong>sudo reboot</strong>

3. This command requires root privileges, so it may prompt you for the root password. After entering the password, the server will initiate a reboot process.

2. shutdown Command

The shutdown command provides more control over the reboot process. It is best used when you want to schedule a reboot or when you require additional options for shutting down and restarting the server. Follow these steps:

1. Enter your Terminal window and execute the following command: 

<strong>sudo shutdown -r now</strong>

2. The -r option indicates a reboot. The now keyword specifies an immediate reboot. Enter the root password if prompted.
3. The server will begin the shutdown process, followed by a reboot.

3. SysRq Magic Keys

Leveraging SysRq Magic Keys is used when your Linux server becomes unresponsive, and traditional reboot methods do not work. This method allows you to switch the keyboard to raw mode, send signals to processes, sync file systems, and remount them in read-only mode before triggering the reboot. Follow these steps:

1. Press and hold the Alt and SysRq (Print Screen) keys simultaneously.

2. While holding those keys, enter the following key sequence: r → e → i → s → u → b.
3. Each key corresponds to a specific action:
   • r: Switch the keyboard to raw mode.
   • e: Send a SIGTERM signal to all processes except init.
   • i: Send a SIGKILL signal to all processes except init.
   • s: Sync all mounted file systems.
   • u: Remount file systems in read-only mode.
   • b: Reboot the system.
4. Release the keys, and the server will initiate a reboot.

How to Do Scheduled Reboots of Linux Server

Scheduled reboots are best used to maintain server stability and performance by regularly restarting the system. By using cron jobs, you can automate the process of scheduling reboots at specific times. Follow these steps to create a scheduled reboot task using cron jobs:

1. Launch your command window.
2. Execute the command: 

<strong>crontab -e</strong>

3. The command will open the crontab configuration file.

4. In the crontab file, add a new line with the following syntax to schedule a reboot at a specific time. For example, to reboot the server every Sunday at 3 AM, add the line:

<strong>0 3 * * 0 sudo reboot</strong>

5. This line represents the minute, hour, day of the month, month, and day of the week, respectively.
6. Save the file and exit. The server will automatically reboot according to the defined schedule.

3 Best Practices for Server Rebooting

When it comes to reboot a Linux server, following best practices ensures a smooth and successful process while minimizing potential issues. By adhering to these best practices, you can mitigate potential risks, maintain system stability, and optimize the server reboot process for your Linux server environment. Here are three best practices to follow:

• 🔒 Take Regular Backups: Before initiating a server reboot, it’s crucial to take regular backups of your important data and configurations. Backups serve as a safety net in case any unexpected issues arise during or after the reboot. Implementing a reliable backup strategy, whether through automated tools or manual processes, helps protect against data loss and ensures you can restore your system to a known working state if needed.
• 🔄 Keep Your System Up to Date: Maintaining an updated system is vital for optimal performance and security. Before rebooting, ensure that your Linux server is up to date with the latest patches, security updates, and bug fixes. Regularly installing system updates helps address known vulnerabilities, enhances stability, and ensures compatibility with the latest software and hardware. Consider using package managers or automated update tools to streamline the update process and keep your server in peak condition.
• 🔎 Check Service Dependencies: Identifying and understanding the dependencies between services running on your server is crucial to avoid disruptions during the reboot process. Take the time to analyze which services rely on each other and ensure they gracefully stop and start in the correct order. Examining service dependencies helps prevent potential conflicts, ensures proper shutdown and startup sequences, and minimizes the risk of service failures or data inconsistencies when rebooting a Linux server.

3 Common Errors When Rebooting a Linux Server

Rebooting a Linux server is a crucial task, but it can sometimes encounter errors that may disrupt the process. Understanding these common errors and their solutions can help ensure a successful server reboot. Here are three frequent errors that you may encounter while rebooting a Linux server:

• ⚠️ “Failed to Unmount File System” error: When rebooting a Linux server, you may come across the error message “Failed to unmount file system.” This error occurs when a file system is still in use or has open files during the reboot process. It can prevent the server from shutting down properly and may lead to data corruption. To resolve this issue, you can manually identify and close any open files or processes associated with the affected file system before initiating the reboot.
• ⛔️ “Service Not Responding” error: Another common error during a server reboot is encountering a non-responsive service. This error typically occurs when a service fails to stop gracefully within the given time frame. It may result in a prolonged reboot process or even prevent the server from restarting. To address this issue, you can forcibly terminate the unresponsive service using commands like kill or systemctl. Additionally, ensure that your services are properly configured to handle graceful shutdowns during reboots.
• 💥“Kernel Panic” error: A kernel panic is a critical error that can occur during the reboot process, indicating an unrecoverable issue with the Linux kernel. It often leads to a complete system freeze or a reboot loop. Kernel panics can be caused by various factors, including hardware failures, incompatible drivers, or system misconfigurations. Resolving a kernel panic requires in-depth troubleshooting, such as analyzing system logs, checking hardware compatibility, and ensuring the system is up to date with the latest patches and drivers. Seeking assistance from experienced system administrators or consulting online resources can be beneficial in resolving this error.

In Conclusion

In this article, I have explored various methods to reboot a Linux server, including using commands such as reboot and shutdown, as well as leveraging SysRq Magic Keys. While rebooting, it’s important to be aware of common errors like failed file system unmounting, non-responsive services, and kernel panics. To ensure a smooth reboot process, I recommend following best practices such as taking regular backups, keeping your system up to date, and checking service dependencies.

To further enhance your server administration skills, I recommend exploring related articles such as Server Monitoring and Performance Optimization, Troubleshooting Server Errors and Log Analysis, and Server Security Best Practices. These resources will expand your understanding of server management, troubleshooting techniques, and system optimization, empowering you to become a proficient Linux server administrator. 

Frequently Asked Questions