Linux Reboot Command Explained (With Examples)

A: There are several methods to reboot a Linux server from the terminal:

# Method 1: Using reboot command
sudo reboot

# Method 2: Using shutdown command
sudo shutdown -r now

# Method 3: Using systemctl (modern systems)
sudo systemctl reboot

Each method has its use case:

• reboot is quick and straightforward
• shutdown -r offers more control over timing and user notifications
• systemctl reboot is preferred on modern systemd-based distributions

A: While both commands achieve the same end result, they have different features:

• reboot is simpler and designed for immediate restarts
• shutdown -r offers more flexibility:
• Can schedule reboots (e.g., shutdown -r +5 for 5 minutes later)
• Provides better user notification options
• Allows cancellation of scheduled reboots
• More detailed logging of the reboot process

A: Follow these steps for a safe production server reboot:

1. Notify users and stakeholders

   wall "Server maintenance scheduled in 10 minutes"

1. Check system status

   systemctl status
   uptime
   df -h

1. Schedule the reboot with notification

   sudo shutdown -r +10 "Server maintenance"

1. Monitor the reboot process

   journalctl -f

1. Verify services after reboot

   systemctl status

   # View logs from logger command
   journalctl -t logger
   
   # Or check system logs for reboot entries
   grep reboot /var/log/syslog

A: If a normal reboot fails, follow this troubleshooting sequence:

1. First, try alternative reboot methods:

   sudo shutdown -r now
   sudo systemctl reboot

1. Check for hung processes:

   ps aux | grep -i "D"

1. Check system logs:

   journalctl -xe
   # Check reboot-related logs
   journalctl -t logger
   grep reboot /var/log/syslog

1. As a last resort, use force reboot:

   sudo reboot -f

1. If all else fails, use the magic SysRq key:

   echo 1 > /proc/sys/kernel/sysrq
   echo b > /proc/sysrq-trigger

A: You can automate server reboots using several methods:

1. Using cron for scheduled reboots

   # Add to crontab
   0 3 * * 0 root /sbin/shutdown -r +5 "Weekly maintenance"

1. Using systemd timer

   # Create a timer unit
   [Unit]
   Description=Weekly Reboot
   
   [Timer]
   OnCalendar=Sun 03:00
   Persistent=true
   
   [Install]
   WantedBy=timers.target

1. Using a shell script

   #!/bin/bash
   logger "Starting scheduled maintenance"
   wall "System maintenance in 5 minutes"
   sleep 300
   sudo reboot

Remember to:

• Always notify users before automated reboots
• Choose maintenance windows during low-traffic periods
• Monitor the reboot process
• Have a rollback plan if issues occur
• Check logs after automated reboots:

  # View maintenance logs
  journalctl -t logger
  # Check system logs for reboot entries
  grep reboot /var/log/syslog

A: Yes, you need sudo privileges to use the reboot command. This is because rebooting is a system-level operation that affects all users and processes on the machine. Standard users don't have the necessary permissions to initiate a system reboot for security reasons. To reboot your system, you'll need to use sudo:

A: Before rebooting:

• Save all work.
• Notify users.
• Unmount disks if needed.
• Use:

sudo shutdown -r +1

To give time for a clean restart.

A: Try shutdown -r now or systemctl reboot. If that fails, check for file system errors, hung processes, or permission issues. As a last resort, a forced reboot (reboot -f) can be used, though it may cause data loss.