Configuration testing (nginx -t) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the command nginx -t do?

It checks the syntax of the nginx configuration files without starting the server. It helps find errors before applying changes.

beginner

Why is it important to run nginx -t before restarting nginx?

Because it ensures the configuration files have no syntax errors, preventing nginx from failing to start or crashing.

beginner

What output indicates a successful configuration test with nginx -t?

You will see messages like:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
and
nginx: configuration file /etc/nginx/nginx.conf test is successful

intermediate

If nginx -t reports an error, what should you do?

Read the error message carefully to find the file and line number causing the problem, then fix the syntax error before testing again.

beginner

Can nginx -t apply configuration changes to the running server?

No, it only tests the configuration syntax. To apply changes, you must reload or restart nginx after a successful test.

What does the -t option do in the nginx command?

A Stops nginx service

B Starts nginx in test mode

C Tests the configuration syntax without starting nginx

D Displays nginx version

The -t option checks the configuration files for syntax errors without starting the server.

What should you do if nginx -t shows a syntax error?

A Ignore it and restart nginx

B Fix the error in the configuration file and test again

C Uninstall nginx

D Run <code>nginx -s reload</code> immediately

You must fix the syntax error before restarting or reloading nginx to avoid failures.

Which message indicates a successful nginx configuration test?

A nginx: configuration file test failed

B nginx: service stopped

C nginx: unknown command

D nginx: the configuration file syntax is ok

The message confirms the syntax is correct and the test succeeded.

Does nginx -t apply configuration changes to the running server?

A No, it only tests the configuration syntax

B Yes, it reloads nginx automatically

C Yes, it restarts nginx

D No, it stops nginx

Testing does not change the running server; you must reload or restart nginx separately.

Where does nginx -t look for configuration files by default?

A /etc/nginx/nginx.conf

B /usr/local/nginx/conf/nginx.conf

C /var/www/html/index.html

D /home/nginx/config.conf

By default, nginx tests the main configuration file located at /etc/nginx/nginx.conf.

Explain the purpose and typical usage of the nginx -t command.

Think about how you check a recipe before cooking.

Describe the steps you take if nginx -t reports a syntax error.

Like proofreading a letter before sending it.

Practice

1. What is the primary purpose of running nginx -t before restarting the nginx service?

easy

A. To check the nginx configuration syntax for errors without applying changes

B. To restart the nginx service immediately

C. To display the current nginx server status

D. To update nginx to the latest version

Solution

1. Step 1: Understand the command purpose

   The nginx -t command tests the configuration files for syntax errors without starting or restarting the server.

2. Step 2: Differentiate from other commands

   Restarting or checking status uses different commands like systemctl restart nginx or systemctl status nginx. Updating nginx is unrelated.

3. Final Answer:

   To check the nginx configuration syntax for errors without applying changes -> Option A

4. Quick Check:

   nginx -t = syntax check [OK]

Hint: Use nginx -t to verify config syntax before restart [OK]

Common Mistakes:

• Confusing nginx -t with restart command
• Thinking nginx -t applies changes
• Using nginx -t to check server status

2. Which of the following is the correct syntax to test nginx configuration files?

easy

A. nginx --test

B. nginx test-config

C. nginx -t

D. nginx --check

Solution

1. Step 1: Recall nginx test command syntax

   The correct command to test nginx configuration syntax is nginx -t.

2. Step 2: Verify other options

   Options like --test, test-config, or --check are invalid and will cause errors.

3. Final Answer:

   nginx -t -> Option C

4. Quick Check:

   Correct test syntax = nginx -t [OK]

Hint: Remember short flag -t for testing config syntax [OK]

Common Mistakes:

• Using long or incorrect flags like --test
• Typing commands that don't exist
• Confusing test with restart commands

3. You run sudo nginx -t and see the output:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

What does this output mean?

medium

A. The nginx configuration has syntax errors and cannot start

B. The nginx service has restarted successfully

C. The nginx configuration file is missing

D. The nginx configuration syntax is correct and ready to reload

Solution

1. Step 1: Interpret the output messages

   The output states the syntax is ok and the test is successful, meaning no errors were found in the config files.

2. Step 2: Understand what the test implies

   This means nginx can safely reload or restart using this configuration without syntax issues.

3. Final Answer:

   The nginx configuration syntax is correct and ready to reload -> Option D

4. Quick Check:

   Syntax ok + test successful = config valid [OK]

Hint: Look for 'syntax is ok' and 'test is successful' in output [OK]

Common Mistakes:

• Assuming test means service restarted
• Confusing syntax errors with warnings
• Ignoring the success message

4. You run sudo nginx -t and get this error:

nginx: [emerg] unknown directive "servere" in /etc/nginx/nginx.conf:12
nginx: configuration file /etc/nginx/nginx.conf test failed

What is the best way to fix this?

medium

A. Correct the typo "servere" to "server" in the config file

B. Ignore the error and restart nginx anyway

C. Delete the entire nginx.conf file

D. Run nginx -s reload without changes

Solution

1. Step 1: Identify the error cause

   The error shows an unknown directive "servere" at line 12, which is likely a typo for "server".

2. Step 2: Fix the configuration file

   Editing the config file to correct the typo will fix the syntax error and allow nginx to test successfully.

3. Final Answer:

   Correct the typo "servere" to "server" in the config file -> Option A

4. Quick Check:

   Fix typos in config to pass nginx -t test [OK]

Hint: Fix typos in config file before restarting nginx [OK]

Common Mistakes:

• Restarting nginx without fixing errors
• Deleting config files unnecessarily
• Ignoring error messages

5. You have multiple nginx config files included in /etc/nginx/nginx.conf. After editing one included file, which command sequence ensures safe application of changes?

hard

A. Run nginx -s stop then nginx -s start without testing

B. Run nginx -t to test, then sudo systemctl reload nginx if no errors

C. Delete the edited file and restart nginx

D. Directly run sudo systemctl restart nginx without testing

Solution

1. Step 1: Test all config files including included ones

   Running nginx -t checks syntax across main and included config files to catch errors before reload.

2. Step 2: Reload nginx safely if test passes

   If the test is successful, use sudo systemctl reload nginx to apply changes without downtime.

3. Final Answer:

   Run nginx -t to test, then sudo systemctl reload nginx if no errors -> Option B

4. Quick Check:

   Test config then reload nginx safely [OK]

Hint: Always test config before reload to avoid downtime [OK]

Common Mistakes:

• Restarting without testing config
• Stopping nginx instead of reloading
• Ignoring included config files