Comment 17 for bug 1648396

Revision history for this message
Frode Nordahl (fnordahl) wrote :

There is a few issues with haproxy logging adding to the complexity of finding the root cause of this bug.

1) The rsyslog daemon is not restarted after configuration is injected in /etc/rsyslog.d by the the haproxy package. This leads to /var/lib/haproxy/dev/log socket not being created.

2) The charm-helpers haproxy.cfg template configures haproxy to log to 127.0.0.1 UDP/514, but rsyslog is by default not configured to receive on UDP/514