Red Hat Bugzilla – Bug 1257690
haproxy should use UDP logging
Last modified: 2016-04-07 17:39:20 EDT
It is higly recommended to use UDP logging for haproxy. Currently, rhel-osp-director will configure haproxy to log to the /dev/log UNIX socket. Since max_dgram_qlen it most likely quite small, you will likely get warnings at startup:
[ALERT] 238/115010 (13878) : sendto logger #1 failed: Resource temporarily unavailable (errno=11)
There are two solutions:
1. Use UDP logging by changing the log line to this:
log 127.0.0.1 local0
2. Increase the max_dgram_qlen via sysctl.
# probably 10
Those 3 reviews address the issue mentioned in the ticket. Both solution 1 and 2.
However, tripleo-heat-templates does not configure rsyslog daemons on the machines, hence 127.0.0.1:514 in UDP is not available out of the box.
I think this request should be made as a RFE. (ie. make t-h-t configure rsyslog deamons on the hosts)
TripleO-Heat-Templates review (Solution 1): https://review.openstack.org/#/c/222602/
TripleO-Heat-Templates review (Solution 2): https://review.openstack.org/#/c/222612/
Puppet-TripleO review : https://review.openstack.org/#/c/222595/
Upstream review merged
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.