Welcome! Log In Create A New Profile

Advanced

Format of messages posted to error_log?

Scott Snow
April 12, 2022 11:34AM
Is there documentation for the format of error messages nginx posted to error_log?
Specifically, following the level in square brackets are two numbers separated by '#'; what do these represent?
For instance, the message on the page Advanced Configuration with Snippets | NGINX Ingress Controllerhttps://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-snippets/ begins with "[emerg] 31:31:"
Why I'm asking is for purposes of documentation; a system using nginx routes these messages to syslog; the design document for the module responsible for publishing the messages gives the format and examples. The example for nginx errors begins:
<131>Oct 24 18:17:47 imx7d-zoll-resus nginx: 2018/10/24 18:17:47 [error] 3105#0: *11 connect() failed (111: Connection refused) while connecting ...

We have a format and examples for each of syslog-ng, gunicorn access, gunicorn error, and nginx access.
_______________________________________________
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-leave@nginx.org
Subject Author Posted

Format of messages posted to error_log?

Scott Snow April 12, 2022 11:34AM

Re: Format of messages posted to error_log?

Sergey A. Osokin April 12, 2022 12:08PM

RE: Format of messages posted to error_log?

Scott Snow April 12, 2022 01:08PM

Re: Format of messages posted to error_log?

Sergey A. Osokin April 12, 2022 03:36PM

Re: Format of messages posted to error_log?

Oleg A. Mamontov April 13, 2022 02:38AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 66
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready