Debug mode in Nginx - Step-by-Step Execution

Process Flow - Debug mode

Enable debug in nginx.conf

↓

Reload nginx service

↓

Send request to nginx

↓

nginx logs detailed debug info

↓

Analyze logs for troubleshooting

↓

Disable debug after fixing

↓

Reload nginx service again

This flow shows how to turn on debug mode in nginx, reload it, check detailed logs, then turn debug off.

Execution Sample

Nginx

error_log /var/log/nginx/error.log debug;
# reload nginx
sudo nginx -s reload
# send request
curl http://localhost
# check logs
cat /var/log/nginx/error.log

Enable debug logging, reload nginx, send a request, then check detailed debug logs.

Process Table

Step	Action	Command/Config	Result/Output
1	Enable debug logging	error_log /var/log/nginx/error.log debug;	Config updated to log debug info
2	Reload nginx	sudo nginx -s reload	nginx reloads with new config, no errors
3	Send HTTP request	curl http://localhost	Response received from nginx server
4	Check logs	cat /var/log/nginx/error.log	Detailed debug info lines appear in log
5	Disable debug logging	error_log /var/log/nginx/error.log warn;	Config updated to normal logging
6	Reload nginx	sudo nginx -s reload	nginx reloads with debug off

💡 Debug mode disabled and nginx reloaded to normal logging

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	Final
error_log level	warn (default)	debug	debug	warn	warn
nginx status	running	running	running with debug	running with debug	running

Key Moments - 3 Insights

Why do we need to reload nginx after changing the error_log level?

Because nginx reads configuration only at startup or reload, so changes like debug mode take effect only after reload (see execution_table step 2).

Will debug logs appear if we don't set error_log level to debug?

No, debug logs only appear if error_log is set to debug level (see execution_table step 1 and 4).

Why disable debug mode after troubleshooting?

Debug mode creates very detailed logs that can fill disk space and slow nginx, so we disable it after use (see execution_table steps 5 and 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the error_log level after step 1?

A error

B warn

C debug

D info

💡 Hint

Check the 'error_log level' row in variable_tracker after Step 1

At which step does nginx reload with debug mode enabled?

A Step 1

B Step 2

C Step 5

D Step 6

💡 Hint

Look at the 'nginx status' variable in variable_tracker and execution_table step 2

If we skip disabling debug mode, what happens?

A nginx logs detailed debug info continuously

B nginx stops logging

C nginx crashes

D nginx ignores debug logs

💡 Hint

Refer to key_moments about why debug mode should be disabled after use

Concept Snapshot

Debug mode in nginx is enabled by setting error_log level to debug in nginx.conf.
Reload nginx to apply changes using 'sudo nginx -s reload'.
Send requests to generate detailed debug logs in error.log.
After troubleshooting, set error_log back to warn and reload nginx.
Debug logs help find issues but can slow server and fill disk space.

Full Transcript

To use debug mode in nginx, first edit the nginx configuration file to set the error_log directive with the debug level. This tells nginx to log detailed information. Then reload nginx so it reads the new config. When you send requests to nginx, it will log detailed debug info in the error log file. After you finish troubleshooting, change the error_log level back to warn to avoid excessive logging and reload nginx again. This process helps find problems by showing detailed internal steps in the logs.