comparison src/core/ngx_syslog.c @ 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
comparison
equal deleted inserted replaced
9225:1c9264603adc 9226:c769217b4a5c
362 ngx_nonblocking_n " failed"); 362 ngx_nonblocking_n " failed");
363 goto failed; 363 goto failed;
364 } 364 }
365 365
366 if (connect(fd, peer->server.sockaddr, peer->server.socklen) == -1) { 366 if (connect(fd, peer->server.sockaddr, peer->server.socklen) == -1) {
367 ngx_log_error(NGX_LOG_ALERT, &peer->log, ngx_socket_errno, 367 ngx_log_error(NGX_LOG_CRIT, &peer->log, ngx_socket_errno,
368 "connect() failed"); 368 "connect() failed");
369 goto failed; 369 goto failed;
370 } 370 }
371 371
372 peer->conn.fd = fd; 372 peer->conn.fd = fd;