Error log configuration in Nginx - Mini Project: Build & Apply

Error log configuration

📖 Scenario: You are managing a web server using nginx. To keep track of problems, you want to set up error logging properly.This helps you find and fix issues quickly, just like keeping a notebook for mistakes when learning something new.

🎯 Goal: Configure the nginx server to log errors to a specific file with a set log level.You will create the error log path, set the log level, and verify the configuration.

📋 What You'll Learn

Create an error_log directive with the exact file path /var/log/nginx/error.log

Set the error log level to warn

Use the error_log directive inside the http block

Print the final nginx.conf snippet showing the error log configuration

💡 Why This Matters

🌍 Real World

Web servers like <code>nginx</code> use error logs to record problems. Proper logging helps quickly find and fix issues, improving website reliability.

💼 Career

DevOps engineers and system administrators configure error logs to monitor server health and troubleshoot problems efficiently.

1

Create the http block skeleton

Write the http block in nginx.conf with opening and closing braces only.

Nginx

http {
    # Your code here
}

Hint

The http block groups web server settings. Start with http { and end with }.

2

Add the error_log directive with file path

Inside the http block, add the error_log directive with the exact file path /var/log/nginx/error.log.

Nginx

http {
    # Add error_log directive with file path here
}

Hint

The error_log directive sets where errors are saved. Use the exact path /var/log/nginx/error.log.

3

Set the error log level to warn

Modify the error_log directive inside the http block to include the log level warn after the file path.

Nginx

http {
    error_log /var/log/nginx/error.log warn;
    # Your code here
}

Hint

Add warn after the file path to set the log level to warnings and above.

4

Print the final nginx.conf snippet

Print the entire http block configuration with the error_log directive and warn level exactly as shown.

Nginx

# Print the nginx.conf snippet below
# Your code here

Hint

Use a print statement to show the final configuration exactly.

Practice

1. What is the main purpose of the error_log directive in nginx?

easy

A. To specify the file where error messages are recorded

B. To set the maximum number of client connections

C. To configure the server's IP address

D. To define the root directory for website files

Solution

1. Step 1: Understand the role of error logs

   Error logs record problems and errors that happen in the server, helping to find and fix issues.

2. Step 2: Identify what error_log does

   The error_log directive tells nginx where to save these error messages, specifying the file path and log level.

3. Final Answer:

   To specify the file where error messages are recorded -> Option A

4. Quick Check:

   error_log = file for errors [OK]

Hint: Error logs = where nginx saves error messages [OK]

Common Mistakes:

• Confusing error_log with access_log
• Thinking error_log sets server IP
• Mixing error_log with client connection limits

2. Which of the following is the correct syntax to set the error log file to /var/log/nginx/error.log with log level warn?

easy

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

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

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

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

Solution

1. Step 1: Recall nginx error_log syntax

   The correct syntax is: error_log <file_path> <log_level>;

2. Step 2: Check each option

   error_log /var/log/nginx/error.log warn; matches the correct syntax with semicolon and no extra symbols. Options A and B have invalid syntax, and D misses the semicolon.

3. Final Answer:

   error_log /var/log/nginx/error.log warn; -> Option D

4. Quick Check:

   Correct syntax ends with semicolon [OK]

Hint: Syntax: error_log path level; ends with semicolon [OK]

Common Mistakes:

• Omitting the semicolon at the end
• Using '=' sign incorrectly
• Adding extra words like 'level'

3. Given this nginx configuration snippet:

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

What level of messages will be logged?

medium

A. Errors and more severe messages

B. Only critical errors

C. All messages including debug

D. Only warnings and errors

Solution

1. Step 1: Understand log levels hierarchy

   Log levels in nginx from least to most severe: debug, info, notice, warn, error, crit, alert, emerg.

2. Step 2: Interpret 'error' level

   Setting level to 'error' logs error and all more severe messages like critical, alert, emergency.

3. Final Answer:

   Errors and more severe messages -> Option A

4. Quick Check:

   error level logs error and above [OK]

Hint: Log level logs that level and higher severity [OK]

Common Mistakes:

• Thinking it logs only critical errors
• Assuming warnings are included at error level
• Confusing debug with error level

4. You set error_log /var/log/nginx/error.log warn; but no warnings appear in the log file. What is the most likely cause?

medium

A. Error logs only record errors, not warnings

B. The log level 'warn' does not exist in nginx

C. The log file path is incorrect or not writable

D. You must restart nginx to enable error logging

Solution

1. Step 1: Check log file path and permissions

   If the path is wrong or nginx cannot write to the file, logs won't appear.

2. Step 2: Validate log level and service status

   'warn' is a valid level, and nginx logs warnings. Restarting is usually needed only after config changes, but logging works immediately if path is correct.

3. Final Answer:

   The log file path is incorrect or not writable -> Option C

4. Quick Check:

   Writable log file needed for logs [OK]

Hint: Check file path and permissions first if logs missing [OK]

Common Mistakes:

• Assuming 'warn' is invalid log level
• Forgetting to check file permissions
• Thinking restart always needed for logging

5. You want to log all error messages including debug info to /var/log/nginx/full_error.log but keep normal error logs at /var/log/nginx/error.log with level error. Which configuration achieves this?

hard

A. error_log /var/log/nginx/error.log error debug;\nerror_log /var/log/nginx/full_error.log debug;

B. error_log /var/log/nginx/error.log error;\nerror_log /var/log/nginx/full_error.log debug;

C. error_log /var/log/nginx/error.log error;\nerror_log /var/log/nginx/full_error.log error;

D. error_log /var/log/nginx/error.log;\nerror_log /var/log/nginx/full_error.log debug;

Solution

1. Step 1: Understand multiple error_log directives

   nginx allows multiple error_log directives to log to different files with different levels.

2. Step 2: Check each option for correct syntax and intent

   error_log /var/log/nginx/error.log error;\nerror_log /var/log/nginx/full_error.log debug; correctly sets error level for normal log and debug level for full log. error_log /var/log/nginx/error.log error debug;\nerror_log /var/log/nginx/full_error.log debug; has invalid combined levels. error_log /var/log/nginx/error.log error;\nerror_log /var/log/nginx/full_error.log error; logs both at error level. error_log /var/log/nginx/error.log;\nerror_log /var/log/nginx/full_error.log debug; misses level for first log.

3. Final Answer:

   error_log /var/log/nginx/error.log error;\nerror_log /var/log/nginx/full_error.log debug; -> Option B

4. Quick Check:

   Separate directives for different levels [OK]

Hint: Use two error_log lines with different levels [OK]

Common Mistakes:

• Combining log levels in one directive incorrectly
• Omitting log level in error_log
• Using one file for both levels