Make sure your NGINX is configured with the -with-debug configuration option.You are here: Home > Multi-Monitor Resources > Forum To enable writing the debugging log to a file: See Writing the Debugging Log to Memory and Debug Log for Selected IPs for details. To reduce the negative impact, you can configure the debugging log to be written into a memory buffer, or set the debugging log for particular IP addresses. Also note that the file can grow very large and quickly eat up disk space. Writing the debugging log to a file may slow down performance under high load. It is recommended enabling the debugging log on the ” main“ level of NGINX configuration to get the full picture of what’s going on. The debugging log may be written to a file, an allocated buffer in memory, stderr output, or to syslog. To enable it, make sure NGINX is compiled to support debugging (see Configuring NGINX Binary For Debugging) and then enable it in NGINX configuration file with the debug parameter of the error_log directive.

The debugging log records errors and any debugging-related information and is disabled by default. Įnabling Debug Logging in NGINX Configuration configure -with-debug -with-cc-opt='-O0 -g'. To enable debugging in NGINX Plus, you will need to switch from nginx to nginx-debug binary. Starting from Release 8, NGINX Plus ships the nginx-debug binary together with the standard binary. NGINX Plus already provides you with nginx-debug binary while NGINX Open Source requires recompilation.

NGINX debugging features include the debugging log and creation of a core dump file with its further backtrace.įirst, you will need to enable debugging in NGINX binary. It is generally used in developing or testing third-party or experimental modules. Introductionĭebugging helps to identify a bug in the program code if something goes wrong. Troubleshoot problems and track down bugs in an NGINX or NGINX Plus deployment, with the debugging binary, debug logging, and core dumps.

How to debug objectdock plus