How to Restart Ubuntu via Command Line on Ubuntu 26.04

Knowing how to restart a server via the command line is an essential skill for any Ubuntu 26.04 administrator. Whether you manage a local workstation, a headless server, or a cloud instance, triggering a clean restart server ubuntu 26.04 without a graphical interface is a routine operational task. This guide covers the primary restart methods available on Ubuntu 26.04, explains when to use each one, and shows you how to verify that the system came back up correctly.

Software Requirements

Restart Ubuntu 26.04 with systemctl reboot

The preferred method to restart server ubuntu 26.04 is through systemctl, the command-line interface for systemd. This approach signals systemd to perform an orderly shutdown of all running services before the kernel reboots, minimising the risk of data corruption.

1. Issue the reboot command: Run the following as a privileged user:

   $ sudo systemctl reboot

   systemd immediately begins stopping all active units in the correct dependency order. The terminal session will drop as the SSH connection closes or the console resets.

Because systemd manages service startup and shutdown on Ubuntu 26.04, systemctl reboot guarantees that services such as databases, web servers, and the SSH server are stopped cleanly before the system restarts. This is especially important on production machines where abrupt termination could leave lock files or partially written logs behind.

Restart Ubuntu 26.04 with shutdown -r

The shutdown command provides additional control over the timing of a restart and lets you send a broadcast message to all logged-in users before the system goes down. This makes it the better choice when other users may be active on the server.

1. Restart immediately: Use now as the time argument:

   $ sudo shutdown -r now

   This is functionally equivalent to systemctl reboot.

2. Restart with a delay and a message: Replace now with a minute offset and append a quoted message:

   $ sudo shutdown -r +10 "Scheduled maintenance reboot in 10 minutes. Please save your work."

   The message is broadcast via wall to every logged-in user’s terminal. After the delay expires, the system restarts automatically.

3. Cancel a pending shutdown: If you need to abort a scheduled restart before it fires, run:

   $ sudo shutdown -c

   A cancellation notice is sent to all users and the restart is aborted.

Using the reboot Command Directly

Ubuntu 26.04 also provides the standalone reboot command as a convenience wrapper. On modern systemd-based systems, calling reboot directly invokes systemctl reboot internally, so the behaviour is identical.

1. Run reboot:

   $ sudo reboot

   The system begins an orderly shutdown and then restarts. This is the shortest command to type and is safe to use interchangeably with systemctl reboot.

Scheduling a Delayed Restart on Ubuntu 26.04

For environments where you need to plan a restart server ubuntu 26.04 outside of business hours, combining shutdown with an absolute time is more reliable than a relative offset, because a relative offset is computed from the moment the command runs.

1. Schedule a restart at a specific time: Specify the time in 24-hour HH:MM format:

   $ sudo shutdown -r 02:00 "Nightly maintenance restart. System will be back in a few minutes."

   The server will restart at 02:00 local time. All logged-in users receive the wall message immediately.

2. Confirm the scheduled restart: Run the following to see whether a shutdown is pending:

   $ systemctl list-jobs | grep shutdown

   If a shutdown job is queued, it appears in the output. An empty result means no restart is scheduled.

Additionally, if you need to trigger a restart after a configuration change such as modifying a static IP or needing to apply Netplan settings, a scheduled restart gives you a window to notify users and complete any outstanding tasks first. For network-related changes specifically, you may not need a full reboot; consult the guide on how to static ip server configure for alternatives.

Similarly, if you run containers, you may prefer to stop them gracefully before the system restarts. See the guide on how to restart Docker services for details.

Verifying the Restart on Ubuntu 26.04

After the system comes back online, confirming that the restart completed successfully is good practice. The two most useful checks are uptime and the system journal.

1. Check uptime: Run:

   $ uptime

   The output shows how long the system has been running since the last boot. A short uptime (seconds or a few minutes) confirms the restart just occurred.

   Example output:

    10:45:03 up 2 min,  1 user,  load average: 0.35, 0.18, 0.07

2. Check boot history with journalctl:

   $ journalctl --list-boots

   Output:

   0 fb0a530471054bde94d68cd33c218bc3 Mon 2026-03-02 23:16:10 CET Mon 2026-03-02 23:20:00 CET

   Each line represents one boot session. The entry marked 0 is the current boot, and the timestamps confirm when the system last started and how long it has been running.

3. Review the journal for boot errors: Use journalctl to inspect the current boot log for any warnings or failures:

   $ journalctl -b -p warning

   The -b flag limits output to the current boot session and -p warning filters to warning-level messages and above. Address any unexpected errors before returning the server to normal operation.

For more detail on the entire restart process, including how to control automatic startup of services after a reboot, see the official systemctl documentation.

Conclusion

Ubuntu 26.04 provides three clean, systemd-backed ways to restart server ubuntu 26.04 from the command line: systemctl reboot, shutdown -r, and the reboot shortcut. For an immediate restart, sudo systemctl reboot is the most explicit and recommended option. When you need to notify users or schedule a restart at a specific time, shutdown -r with a time argument and a message gives you that control. After the system returns online, confirming the uptime and reviewing the journal ensures the restart completed without issues.

For related operations, you can also consult the guide on how to restart Ubuntu 26.04 using other methods, including graphical tools and remote management interfaces.

Frequently Asked Questions

1. What is the difference between reboot, shutdown -r now, and systemctl reboot on Ubuntu 26.04? On Ubuntu 26.04, all three commands result in the same outcome: a clean, orderly system restart managed by systemd. reboot is simply a convenience wrapper that internally calls systemctl reboot. shutdown -r now routes through the shutdown utility but also delegates to systemd on modern systems. The practical difference is that shutdown -r additionally accepts a time argument and a broadcast message, making it more flexible for multi-user environments.
2. Will a command-line restart close all running services safely? Yes. Because Ubuntu 26.04 uses systemd as its init system, all three restart commands trigger an orderly teardown of running units before the kernel reboots. Services are stopped in reverse dependency order, which means databases, web servers, and other daemons are given the opportunity to flush buffers and release locks cleanly.
3. How can I restart a remote Ubuntu 26.04 server without losing my SSH session permanently? You cannot keep an SSH session alive across a reboot, as the connection drops when the SSH daemon stops. However, you can use tools like tmux or screen to preserve terminal sessions that resume automatically after reconnection. Alternatively, schedule the restart with shutdown -r +N so you have time to disconnect gracefully and then reconnect once the server is back online. After reconnecting, run uptime or who -b to confirm the restart completed.
4. Is there a way to restart only specific services instead of the whole system? Yes. If your goal is to apply a configuration change without a full reboot, you can restart individual systemd services with sudo systemctl restart service-name. For example, to restart the networking stack after a configuration change, you may only need to apply Netplan settings rather than rebooting the entire server.