Re: Format of messages posted to error_log?

[Oleg A. Mamontov]

On Tue, Apr 12, 2022 at 10:30:29PM +0300, Sergey A. Osokin wrote:

On Tue, Apr 12, 2022 at 05:04:19PM +, Scott Snow wrote:

Sergey -
Thanks for the quick reply.

Note I am not asking after format of message content akin to what's
available for access_log, just the interpretation of the numerical parts
of the apparent pattern in the error_log messages posted:
"[]  # : "

Perhaps you mean even the "[] #" isn't fixed
or necessarily present; in that case, is there something distinguishing
error_log entries that do not follow this pattern?


Well, those two numbers are processId#connectionId, please visit the
following link to get more details:


Please let me correct a little: "processId#threadId: *connectionId"


https://nginx.org/en/docs/dev/development_guide.html#logging

--
Sergey A. Osokin
___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org


--
Cheers,
Oleg A. Mamontov
___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org

Re: Format of messages posted to error_log?

[Sergey A. Osokin]

On Tue, Apr 12, 2022 at 05:04:19PM +, Scott Snow wrote:
> Sergey -
> Thanks for the quick reply.
> 
> Note I am not asking after format of message content akin to what's
> available for access_log, just the interpretation of the numerical parts
> of the apparent pattern in the error_log messages posted:
> "[]  # : "
> 
> Perhaps you mean even the "[] #" isn't fixed
> or necessarily present; in that case, is there something distinguishing
> error_log entries that do not follow this pattern?

Well, those two numbers are processId#connectionId, please visit the
following link to get more details:
https://nginx.org/en/docs/dev/development_guide.html#logging

--
Sergey A. Osokin
___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org

RE: Format of messages posted to error_log?

[Scott Snow]

Sergey -
Thanks for the quick reply.

Note I am not asking after format of message content akin to what's available 
for access_log,
just the interpretation of the numerical parts of the apparent pattern in the 
error_log messages posted:
"[]  # : "

Perhaps you mean even the "[] #" isn't fixed or 
necessarily present; in that case, is there something distinguishing error_log 
entries that do not follow this pattern?

___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org

Re: Format of messages posted to error_log?

[Sergey A. Osokin]

Hi Scott,

hope you're doing well.

The error_log directive is documented well [1].
There's no format of error messages.

While I'm here I'd recommend to keep 72 characters per line, that helps
a lot to read emails, thank you.

References:
[1] https://nginx.org/en/docs/ngx_core_module.html#error_log

--
Sergey A. Osokin

In-Reply-To: 


On Tue, Apr 12, 2022 at 03:29:57PM +, Scott Snow wrote:
> 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 
> Controller
>  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-le...@nginx.org