Why logging tracks server behavior in Nginx - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable access logging in nginx.

Nginx

access_log [1];

Drag options to blanks, or click blank then click option'

A/var/log/nginx/access.log

B/var/log/nginx/error.log

C/etc/nginx/nginx.conf

D/usr/share/nginx/html

Attempts:

3 left

💡 Hint

Common Mistakes

Using the error log path instead of access log path

Using configuration file path instead of log file path

The access_log directive specifies the file where nginx writes access logs. The default and common path is /var/log/nginx/access.log.

2fill in blank

medium

Complete the code to set the log format to 'combined' in nginx.

Nginx

log_format main [1];

Drag options to blanks, or click blank then click option'

A"combined log"

Bcombined

C"combined"

D"default"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or misspelled format names

Omitting quotes around the format string

The log_format directive defines a log format. The 'combined' format is a standard format that includes common fields for access logs.

3fill in blank

hard

Fix the error in the nginx configuration to log errors to the correct file.

Nginx

error_log [1] warn;

Drag options to blanks, or click blank then click option'

A/var/log/nginx/error.log

B/var/log/nginx/access.log

C/etc/nginx/error.log

D/usr/share/nginx/error.log

Attempts:

3 left

💡 Hint

Common Mistakes

Using access log path for error logs

Using incorrect directory paths

The error_log directive specifies where nginx writes error logs. The standard path is /var/log/nginx/error.log.

4fill in blank

hard

Fill both blanks to configure nginx to log access using the 'main' format to the correct file.

Nginx

access_log [1] [2];

Drag options to blanks, or click blank then click option'

A/var/log/nginx/access.log

Bmain

Cerror

D/var/log/nginx/error.log

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping file path and format

Using error log path for access logs

The access_log directive takes the log file path and the log format name. Here, the file is /var/log/nginx/access.log and the format is main.

5fill in blank

hard

Fill all three blanks to create a custom log format named 'detailed' that logs client IP, request method, and status code.

Nginx

log_format detailed '[1] [2] [3]';

Drag options to blanks, or click blank then click option'

A$remote_addr

B$request_method

C$status

D$host

Attempts:

3 left

💡 Hint

Common Mistakes

Using $host instead of $remote_addr for IP

Mixing variable order

The custom log format uses variables: $remote_addr for client IP, $request_method for HTTP method, and $status for response status code.

Practice

1. Why does nginx keep logs of server activity?

easy

A. To slow down the server performance

B. To record what the server does and any problems it encounters

C. To delete old files automatically

D. To increase the server's memory usage

Solution

1. Step 1: Understand the purpose of logging

   Logging is used to keep a record of server actions and errors for monitoring and troubleshooting.

2. Step 2: Identify the correct reason for nginx logging

   nginx logs server activity to help administrators track behavior and fix issues.

3. Final Answer:

   To record what the server does and any problems it encounters -> Option B

4. Quick Check:

   Logging = record server actions and errors [OK]

Hint: Logging tracks server actions and errors for monitoring [OK]

Common Mistakes:

• Thinking logging slows server down
• Confusing logging with file deletion
• Assuming logging increases memory use

2. Which of the following is the correct nginx directive to enable access logging?

easy

A. access_log /var/log/nginx/access.log;

B. log_access /var/log/nginx/access.log;

C. enable_access_log /var/log/nginx/access.log;

D. accesslog /var/log/nginx/access.log;

Solution

1. Step 1: Recall nginx logging syntax

   The correct directive to enable access logging is access_log followed by the log file path.

2. Step 2: Compare options to correct syntax

   Only access_log /var/log/nginx/access.log; uses the exact directive access_log with proper syntax.

3. Final Answer:

   access_log /var/log/nginx/access.log; -> Option A

4. Quick Check:

   Correct directive = access_log [OK]

Hint: Remember exact directive name: access_log [OK]

Common Mistakes:

• Adding underscores incorrectly
• Using wrong directive names
• Missing semicolon at end

3. Given this nginx log entry: 127.0.0.1 - - [10/Oct/2023:13:55:36 +0000] "GET /index.html HTTP/1.1" 200 1024 "-" "Mozilla/5.0", what does the status code 200 indicate?

medium

A. The requested page was not found

B. The server encountered an internal error

C. The request was successful

D. The client is unauthorized

Solution

1. Step 1: Understand HTTP status codes in logs

   Status code 200 means the server successfully processed the request.

2. Step 2: Match code to meaning

   200 means success; 404 means not found; 500 means server error; 401 means unauthorized.

3. Final Answer:

   The request was successful -> Option C

4. Quick Check:

   200 = success status code [OK]

Hint: 200 means success in HTTP status codes [OK]

Common Mistakes:

• Confusing 200 with error codes
• Mixing client and server error codes
• Ignoring status code meaning

4. You notice nginx error logs are empty even though the server has issues. Which configuration mistake could cause this?

medium

A. Missing error_log directive or wrong file path

B. Using access_log instead of error_log

C. Setting error_log level to crit instead of error

D. All of the above

Solution

1. Step 1: Check error log directive presence and path

   If error_log is missing or points to wrong file, errors won't be recorded.

2. Step 2: Verify correct directive and log level

   Using access_log won't capture errors. Also, setting log level too high (like crit) may miss error messages.

3. Final Answer:

   All of the above -> Option D

4. Quick Check:

   Error logs need correct directive, path, and level [OK]

Hint: Check error_log directive, path, and level carefully [OK]

Common Mistakes:

• Confusing access_log with error_log
• Ignoring log file path correctness
• Setting log level too high

5. How can proper nginx logging help improve server security?

hard

A. By tracking suspicious requests and detecting attacks early

B. By automatically blocking all IP addresses

C. By deleting old log files to save space

D. By increasing server CPU usage

Solution

1. Step 1: Understand logging role in security

   Logs record all requests, including suspicious ones, helping identify attacks or unauthorized access.

2. Step 2: Identify how logs improve security

   By analyzing logs, admins can detect patterns of attacks and respond quickly to protect the server.

3. Final Answer:

   By tracking suspicious requests and detecting attacks early -> Option A

4. Quick Check:

   Logging helps detect attacks early [OK]

Hint: Logs reveal suspicious activity for quick security response [OK]

Common Mistakes:

• Thinking logs block IPs automatically
• Confusing logging with file cleanup
• Assuming logs increase CPU load