changeset 9226:c769217b4a5c

Syslog: logging level of connect() errors. Connecting to syslog server might legitimately fail: for example, if syslogd is not running, and the connection is made over a unix socket. As such, the "alert" logging level is not appropriate. Changed logging level to "crit" instead, similarly to the logging level used for connect() errors in resolver.
author Maxim Dounin <mdounin@mdounin.ru>
date Fri, 01 Mar 2024 05:42:15 +0300
parents 1c9264603adc
children 37ef53ecd6b0
files src/core/ngx_syslog.c
diffstat 1 files changed, 1 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/src/core/ngx_syslog.c
+++ b/src/core/ngx_syslog.c
@@ -364,7 +364,7 @@ ngx_syslog_init_peer(ngx_syslog_peer_t *
     }
 
     if (connect(fd, peer->server.sockaddr, peer->server.socklen) == -1) {
-        ngx_log_error(NGX_LOG_ALERT, &peer->log, ngx_socket_errno,
+        ngx_log_error(NGX_LOG_CRIT, &peer->log, ngx_socket_errno,
                       "connect() failed");
         goto failed;
     }