Debug mode in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Enable debug logging in nginx configuration

You want to enable debug logging in nginx to troubleshoot request handling. Which directive correctly enables debug logging in the main nginx configuration file?

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

B access_log /var/log/nginx/access.log debug;

C log_level debug;

D debug_log /var/log/nginx/debug.log;

💡 Hint

Debug logging in nginx is controlled by the error_log directive with a specific log level.

The error_log directive controls error and debug logging in nginx. Setting its level to debug enables detailed debug logs. The access_log directive does not accept a debug level. There is no log_level or debug_log directive in nginx.

💻 Command Output

intermediate

Check if debug mode is active in nginx

After enabling debug logging, you want to verify if nginx is running with debug mode active. Which command output confirms debug mode is enabled?

Nginx

nginx -V

A debug=true

B error_log set to debug

C debug_mode=on

D built with --with-debug

💡 Hint

Check the nginx build options to see if debug support is compiled in.

The nginx -V command shows build options. The presence of --with-debug means nginx was compiled with debug support. The other options are not part of the nginx -V output.

❓ Configuration

advanced

Configure debug logging only for a specific location

You want to enable debug logging only for requests to the /api location in nginx, without affecting other locations. Which configuration snippet achieves this?

A

location /api {
    error_log /var/log/nginx/api_error.log debug;
}

B

error_log /var/log/nginx/api_error.log debug;
location /api {}

C

location /api {
    access_log /var/log/nginx/api_access.log debug;
}

D

location /api {
    debug_log /var/log/nginx/api_debug.log;
}

💡 Hint

The error_log directive can be set inside a location block to control logging for that location.

Setting error_log with debug level inside the location /api block enables debug logging only for that location. The access_log directive does not support debug level. The other options either set logging globally or use invalid directives.

❓ Troubleshoot

advanced

Debug logs not appearing after enabling debug mode

You enabled debug logging in nginx with error_log /var/log/nginx/error.log debug; but no debug messages appear in the log. What is the most likely cause?

A The log file path is incorrect and nginx cannot write logs

B The error_log directive must be in the http block, not main

C nginx was not compiled with --with-debug option

D Debug logging requires restarting the server with --debug flag

💡 Hint

Check if your nginx binary supports debug mode by build options.

If nginx was not compiled with --with-debug, debug logging directives are ignored. The error_log directive can be in main or http blocks. Incorrect log path causes errors but usually logs warnings. There is no --debug flag for nginx start.

✅ Best Practice

expert

Best practice for enabling debug mode in production nginx

You need to enable debug logging temporarily on a production nginx server to troubleshoot an issue. What is the best practice to minimize impact?

A Enable debug logging globally and restart nginx to apply changes

B Enable debug logging only for the affected location and reload nginx configuration

C Enable debug logging and leave it on permanently for continuous monitoring

D Stop nginx, enable debug logging, then start nginx to avoid partial logs

💡 Hint

Limit debug logging scope and avoid full restarts in production.

Enabling debug logging only for the affected location reduces performance impact. Reloading configuration applies changes without downtime. Global debug logging or permanent debug mode can degrade performance. Stopping nginx is unnecessary and causes downtime.

Practice

1. What does enabling debug mode in nginx do?

easy

A. Shows detailed logs to help find problems

B. Stops nginx from running

C. Deletes all log files

D. Automatically fixes errors

Solution

1. Step 1: Understand debug mode purpose

   Debug mode is designed to provide detailed information about what nginx is doing internally.

2. Step 2: Identify effect of enabling debug mode

   It shows detailed logs that help find and fix problems in nginx configuration or operation.

3. Final Answer:

   Shows detailed logs to help find problems -> Option A

4. Quick Check:

   Debug mode = detailed logs [OK]

Hint: Debug mode means detailed logs for troubleshooting [OK]

Common Mistakes:

• Thinking debug mode stops nginx
• Believing debug mode deletes logs
• Assuming debug mode auto-fixes errors

2. Which is the correct syntax to enable debug mode in nginx's error log?

easy

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

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

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

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

Solution

1. Step 1: Recall error_log syntax

   The correct syntax is: error_log <file_path> <level>; where level can be debug, info, etc.

2. Step 2: Identify correct option

   error_log /var/log/nginx/error.log debug; uses correct order: file path first, then debug level.

3. Final Answer:

   error_log /var/log/nginx/error.log debug; -> Option C

4. Quick Check:

   error_log file_path debug; = error_log /var/log/nginx/error.log debug; [OK]

Hint: error_log path then level debug; is correct syntax [OK]

Common Mistakes:

• Swapping file path and level order
• Using info instead of debug for debug mode
• Setting level to off disables logging

3. Given this nginx config snippet:

error_log /var/log/nginx/error.log debug;
server {
  listen 80;
  server_name example.com;
}

What will happen when nginx receives a request?

medium

A. Detailed debug logs will be written to /var/log/nginx/error.log

B. No logs will be created

C. Only error messages will be logged

D. Nginx will refuse connections

Solution

1. Step 1: Analyze error_log level

   The error_log is set to debug level, which logs detailed info about requests.

2. Step 2: Understand effect on request handling

   When nginx receives a request, it logs detailed debug info to the specified file.

3. Final Answer:

   Detailed debug logs will be written to /var/log/nginx/error.log -> Option A

4. Quick Check:

   debug level logs detailed info [OK]

Hint: debug level logs detailed info on requests [OK]

Common Mistakes:

• Thinking debug disables logging
• Assuming only errors are logged
• Believing nginx refuses connections with debug

4. You set error_log /var/log/nginx/error.log debug; but see no debug logs. What is a likely cause?

medium

A. Debug mode disables logging

B. Nginx was not reloaded after config change

C. The log file path is missing

D. The debug level is misspelled

Solution

1. Step 1: Check if config changes are active

   After changing nginx config, you must reload nginx to apply changes.

2. Step 2: Identify why no debug logs appear

   If nginx is not reloaded, it uses old config without debug logging.

3. Final Answer:

   Nginx was not reloaded after config change -> Option B

4. Quick Check:

   Reload nginx after config change [OK]

Hint: Reload nginx after config changes to activate debug [OK]

Common Mistakes:

• Forgetting to reload nginx
• Thinking debug disables logs
• Misspelling debug level

5. You want to enable debug mode only temporarily to avoid large log files. Which is the best approach?

hard

A. Delete log files manually to reduce size

B. Permanently set debug mode in nginx.conf

C. Disable logging completely during debugging

D. Set error_log /var/log/nginx/error.log debug;, reload nginx, then revert after debugging

Solution

1. Step 1: Understand temporary debug enabling

   Temporarily enable debug by changing error_log level and reloading nginx.

2. Step 2: Revert changes after debugging

   To avoid large logs, revert error_log level back and reload nginx again.

3. Final Answer:

   Set error_log /var/log/nginx/error.log debug;, reload nginx, then revert after debugging -> Option D

4. Quick Check:

   Temporary debug = enable then revert [OK]

Hint: Enable debug, reload, then revert to avoid big logs [OK]

Common Mistakes:

• Leaving debug mode enabled permanently
• Deleting logs instead of controlling debug level
• Disabling logging disables debug info