Error log configuration in Nginx - Step-by-Step Execution

Process Flow - Error log configuration

Start nginx

↓

Check error_log directive

↓

Open error log file

↓

Set log level

↓

Write errors to log

↓

Continue serving requests

↓

On error, append entry to log file

Nginx reads the error_log directive, opens the specified file, sets the log level, and writes error messages there during runtime.

Execution Sample

Nginx

error_log /var/log/nginx/error.log warn;

server {
    listen 80;
    server_name example.com;
}

Configures nginx to log warnings and above to /var/log/nginx/error.log

Process Table

Step	Action	Directive Evaluated	Log File	Log Level	Result
1	Start nginx	N/A	N/A	N/A	Nginx process starts
2	Read config	error_log /var/log/nginx/error.log warn;	/var/log/nginx/error.log	warn	Log file and level set
3	Open log file	error_log directive	/var/log/nginx/error.log	warn	File opened for appending
4	Serve requests	N/A	/var/log/nginx/error.log	warn	Normal operation
5	Error occurs	N/A	/var/log/nginx/error.log	warn	Error message written to log
6	Stop nginx	N/A	/var/log/nginx/error.log	warn	Log file closed
7	Exit	N/A	N/A	N/A	Nginx stopped, logging ended

💡 Nginx stops or reloads, closing log file and ending logging

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
log_file	undefined	/var/log/nginx/error.log	/var/log/nginx/error.log (opened)	/var/log/nginx/error.log (written)	closed
log_level	undefined	warn	warn	warn	warn

Key Moments - 3 Insights

Why does nginx need the error_log directive before starting to log errors?

Because as shown in execution_table step 2, nginx reads the error_log directive to know which file to open and what level of errors to log before it can write any error messages.

What happens if the log file path is incorrect or not writable?

Nginx will fail to open the log file at step 3, which can cause errors or prevent logging. This is why the file path must be valid and writable.

Does nginx log all errors regardless of the log level set?

No, only errors at or above the configured log level (e.g., warn) are logged, as shown in step 5 where only warnings and more severe messages are written.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what does nginx set as the log level?

A error

B warn

C info

D debug

💡 Hint

Check the 'Log Level' column at step 2 in the execution_table.

At which step does nginx open the error log file for writing?

A Step 1

B Step 2

C Step 3

D Step 5

💡 Hint

Look for the step where the 'Result' says 'File opened for appending' in the execution_table.

If the log level is changed to 'error', how would the logging behavior change?

A Fewer messages would be logged

B More messages would be logged

C No messages would be logged

D All messages including debug would be logged

💡 Hint

Refer to the key_moments explanation about log level filtering.

Concept Snapshot

error_log <file_path> <level>;
- Sets where nginx writes error messages
- Levels: debug, info, notice, warn, error, crit, alert, emerg
- Only messages at or above level are logged
- Must be set before nginx starts logging
- Example: error_log /var/log/nginx/error.log warn;

Full Transcript

This visual execution shows how nginx configures error logging. When nginx starts, it reads the error_log directive to find the log file path and log level. It opens the file for appending error messages. During operation, errors at or above the set level are written to this file. If the file path is invalid, logging fails. The log level controls which errors are recorded, filtering out less severe messages. When nginx stops, it closes the log file and ends logging.