Configuration reload vs restart in Nginx - CLI Comparison

Introduction

When you change the settings of a web server like nginx, you need to apply those changes. You can either reload the configuration without stopping the server or restart the server completely. Each method affects how your website stays available during the update.

When you update nginx settings like adding a new site or changing ports and want to apply changes without downtime.

When you fix a configuration error and want to test the new settings safely.

When you want to refresh nginx after changing SSL certificates without disconnecting users.

When you want to fully restart nginx to clear all running processes and start fresh.

When you suspect nginx is stuck or not responding and need a full restart to fix it.

Commands

This command tests the nginx configuration files for syntax errors before applying changes. It helps avoid applying broken settings.

Terminal

sudo nginx -t

Expected Output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

This command reloads the nginx configuration without stopping the server. It applies changes smoothly without disconnecting users.

Terminal

sudo systemctl reload nginx

Expected Output

No output (command runs silently)

This command stops and then starts nginx again. It fully restarts the server, which causes a brief downtime.

Terminal

sudo systemctl restart nginx

Expected Output

No output (command runs silently)

This command checks if nginx is running properly after reload or restart.

Terminal

sudo systemctl status nginx

Expected Output

● nginx.service - A high performance web server and a reverse proxy server

   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)

   Active: active (running) since Fri 2024-06-07 10:00:00 UTC; 5s ago

     Docs: man:nginx(8)

 Main PID: 1234 (nginx)

    Tasks: 3 (limit: 4915)

   Memory: 5.0M

   CGroup: /system.slice/nginx.service

           ├─1234 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;

           ├─1235 nginx: worker process

           └─1236 nginx: worker process

Key Concept

Reloading nginx applies configuration changes without stopping the server, while restarting stops and starts the server causing brief downtime.

Common Mistakes

Restarting nginx when only configuration changes need to be applied

Restart causes unnecessary downtime and disconnects users.

Use 'sudo systemctl reload nginx' to apply changes smoothly without downtime.

Reloading nginx without testing configuration first

If the configuration has errors, reload will fail and nginx may stop serving requests.

Always run 'sudo nginx -t' to test configuration before reload.

Ignoring nginx status after reload or restart

You might miss errors or nginx not running properly after changes.

Check status with 'sudo systemctl status nginx' to confirm nginx is active.

Summary

Use 'sudo nginx -t' to test nginx configuration syntax before applying changes.

Use 'sudo systemctl reload nginx' to apply configuration changes without downtime.

Use 'sudo systemctl restart nginx' only when a full server restart is needed.

Check nginx status with 'sudo systemctl status nginx' after reload or restart.