Why logging tracks server behavior in Nginx - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Nginx use access logs?

What is the main purpose of the access.log file in Nginx?

A To store the server's configuration files

B To save the server's error messages only

C To record every request made to the server for monitoring and troubleshooting

D To cache website content for faster delivery

💡 Hint

Think about what information helps you understand who visited your website and when.

The access.log records all requests to the server, helping track usage and diagnose issues.

💻 Command Output

intermediate

Output of Nginx error log on startup failure

What output will you see in the Nginx error log if the server fails to start due to a syntax error in the configuration?

Nginx

nginx -t

A "nginx: [emerg] unknown directive \"bad_directive\" in /etc/nginx/nginx.conf:10"

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

C "nginx: [warn] deprecated directive used in /etc/nginx/nginx.conf"

D "nginx: [error] failed to bind to port 80"

💡 Hint

Look for messages indicating a syntax problem in the config file.

A syntax error causes an emergency level log entry showing the unknown directive and file location.

❓ Configuration

advanced

Configuring Nginx to log client IP and request time

Which Nginx log_format configuration correctly logs the client IP and request processing time?

A log_format custom '$remote_addr - $request_time "$request"';

B log_format custom '$remote_user - $request_time "$request"';

C log_format custom '$remote_addr - $request_length "$request"';

D log_format custom '$remote_addr - $upstream_response_time "$request"';

💡 Hint

Remember, $remote_addr is client IP and $request_time is request duration.

The log_format directive uses variables like $remote_addr for client IP and $request_time for request time.

❓ Troubleshoot

advanced

Diagnosing missing logs in Nginx

You notice that Nginx is not writing any entries to the access.log. What is the most likely cause?

A The <code>error_log</code> level is set to <code>info</code>

B The <code>access_log</code> directive is missing or commented out in the server block

C The Nginx service is running with root privileges

D The server is running out of disk space

💡 Hint

Check if logging is enabled in the configuration.

If access_log is missing or disabled, no access logs will be written.

✅ Best Practice

expert

Best practice for rotating Nginx logs

What is the recommended way to rotate Nginx logs without stopping the server?

A Disable logging during peak hours to avoid large log files

B Manually delete the log files and restart Nginx

C Configure Nginx to write logs to a database instead of files

D Use the <code>logrotate</code> tool with a postrotate script that sends <code>nginx -s reopen</code>

💡 Hint

Think about how to safely tell Nginx to start writing to new log files.

Using logrotate with a postrotate script that signals Nginx to reopen logs avoids downtime and data loss.