RE: logger #n in ALERT messages?
From: PiBa-NL [mailto:piba.nl@gmail.com] Sent: Friday, March 9, 2018 3:08 PM To: Glen Gunselman <gguns...@emporia.edu>; Haproxy <haproxy@formilux.org> Subject: Re: logger #n in ALERT messages? Hi Glen, Op 9-3-2018 om 17:43 schreef Glen Gunselman: (Note: this is my first attempt to setup haproxy, I'm using Oracle Linux 6.9 and HA-Proxy version 1.5.18 2016/05/10) How do I relate "logger #n" in ALERT messages to the configuration statements? Related details: >From starting haproxy using: sudo haproxy -d -f /etc/haproxy/haproxy.cfg | grep logger I get ALERTs of the following format: [ALERT] 067/101928 (39878) : sendto logger #2 failed: Resource temporarily unavailable (errno=11) [ALERT] 067/101928 (39878) : sendto logger #1 failed: No such file or directory (errno=2) [ALERT] 067/101928 (39878) : sendto logger #2 failed: No such file or directory (errno=2) [ALERT] 067/101928 (39878) : sendto logger #1 failed: No such file or directory (errno=2) ... >From top of /etc/haproxy/haproxy.cfg global log /dev/loglocal0 log /dev/loglocal1 notice chroot /var/lib/haproxy You do have both log sockets?: /dev/log and /var/lib/haproxy/dev/log [Glen Gunselman] NO, only /dev/log user haproxy group haproxy daemon maxconn 1 stats socket /var/run/haproxy/haproxy.sock mode 0600 level admin # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private tune.ssl.default-dh-param 2048 ssl-default-bind-ciphers kEECDH+aRSA+AES:kRSA+AES:+AES256:!kEDH:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl-default-bind-options no-sslv3 defaults log global modehttp option httplog option dontlognull option forwardfor timeout connect 5000 timeout client 300s timeout server 300s listen stats :1936 modehttp log global maxconn 10 timeout client 100s timeout server 100s timeout connect 100s timeout queue 100s stats enable stats hide-version stats refresh 30s stats show-node stats auth : stats uri /haproxy?stats (Note: I did not include the frontend, acl, use_backend and backend sections. There are no log statements in these sections.) I did add the following to /etc/rsyslog.conf and messages are being logged to those files. local0.* /var/log/haproxy.log local1.* /var/log/haproxy-status.log Thanks for any clues, Glen Regards, PiBa-NL (Pieter)
Re: logger #n in ALERT messages?
Hi Glen, Op 9-3-2018 om 17:43 schreef Glen Gunselman: (Note: this is my first attempt to setup haproxy, I'm using Oracle Linux 6.9 and HA-Proxy version 1.5.18 2016/05/10) How do I relate "logger #n" in ALERT messages to the configuration statements? Related details: From starting haproxy using: sudohaproxy -d -f /etc/haproxy/haproxy.cfg | grep logger I get ALERTs of the following format: [ALERT] 067/101928 (39878) : sendto logger #2 failed: Resource temporarily unavailable (errno=11) [ALERT] 067/101928 (39878) : sendto logger #1 failed: No such file or directory (errno=2) [ALERT] 067/101928 (39878) : sendto logger #2 failed: No such file or directory (errno=2) [ALERT] 067/101928 (39878) : sendto logger #1 failed: No such file or directory (errno=2) … From top of /etc/haproxy/haproxy.cfg global log /dev/loglocal0 log /dev/loglocal1 notice chroot /var/lib/haproxy You do have both log sockets?: /dev/log and /var/lib/haproxy/dev/log user haproxy group haproxy daemon maxconn 1 stats socket /var/run/haproxy/haproxy.sock mode 0600 level admin # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private tune.ssl.default-dh-param 2048 ssl-default-bind-ciphers kEECDH+aRSA+AES:kRSA+AES:+AES256:!kEDH:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl-default-bind-options no-sslv3 defaults logglobal modehttp optionhttplog optiondontlognull optionforwardfor timeout connect 5000 timeout client 300s timeout server 300s listenstats:1936 modehttp logglobal maxconn 10 timeout client100s timeout server100s timeout connect 100s timeout queue100s stats enable stats hide-version stats refresh 30s stats show-node stats auth : stats uri/haproxy?stats (Note: I did not include the frontend, acl, use_backend and backend sections.There are no log statements in these sections.) I did add the following to /etc/rsyslog.conf and messages are being logged to those files. local0.*/var/log/haproxy.log local1.*/var/log/haproxy-status.log Thanks for any clues, Glen Regards, PiBa-NL (Pieter)
logger #n in ALERT messages?
(Note: this is my first attempt to setup haproxy, I'm using Oracle Linux 6.9 and HA-Proxy version 1.5.18 2016/05/10) How do I relate "logger #n" in ALERT messages to the configuration statements? Related details: >From starting haproxy using: sudo haproxy -d -f /etc/haproxy/haproxy.cfg | grep logger I get ALERTs of the following format: [ALERT] 067/101928 (39878) : sendto logger #2 failed: Resource temporarily unavailable (errno=11) [ALERT] 067/101928 (39878) : sendto logger #1 failed: No such file or directory (errno=2) [ALERT] 067/101928 (39878) : sendto logger #2 failed: No such file or directory (errno=2) [ALERT] 067/101928 (39878) : sendto logger #1 failed: No such file or directory (errno=2) ... >From top of /etc/haproxy/haproxy.cfg global log /dev/loglocal0 log /dev/loglocal1 notice chroot /var/lib/haproxy user haproxy group haproxy daemon maxconn 1 stats socket /var/run/haproxy/haproxy.sock mode 0600 level admin # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private tune.ssl.default-dh-param 2048 ssl-default-bind-ciphers kEECDH+aRSA+AES:kRSA+AES:+AES256:!kEDH:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl-default-bind-options no-sslv3 defaults log global modehttp option httplog option dontlognull option forwardfor timeout connect 5000 timeout client 300s timeout server 300s listen stats :1936 modehttp log global maxconn 10 timeout client 100s timeout server 100s timeout connect 100s timeout queue 100s stats enable stats hide-version stats refresh 30s stats show-node stats auth : stats uri /haproxy?stats (Note: I did not include the frontend, acl, use_backend and backend sections. There are no log statements in these sections.) I did add the following to /etc/rsyslog.conf and messages are being logged to those files. local0.* /var/log/haproxy.log local1.* /var/log/haproxy-status.log Thanks for any clues, Glen