yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #83849
[Bug 1744359] Re: Neutron haproxy logs are not being collected
** Changed in: tripleo
Status: Incomplete => Invalid
** Changed in: tripleo
Importance: High => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1744359
Title:
Neutron haproxy logs are not being collected
Status in devstack:
Invalid
Status in neutron:
Fix Released
Status in tripleo:
Invalid
Bug description:
In Neutron, we use haproxy to proxy metadata requests from instances to Nova Metadata service.
By default, haproxy logs to /dev/log but in Ubuntu, those requests get redirected by rsyslog to
/var/log/haproxy.log which is not being collected.
ubuntu@devstack:~$ cat /etc/rsyslog.d/49-haproxy.conf
# Create an additional socket in haproxy's chroot in order to allow logging via
# /dev/log to chroot'ed HAProxy processes
$AddUnixListenSocket /var/lib/haproxy/dev/log
# Send HAProxy messages to a dedicated logfile
if $programname startswith 'haproxy' then /var/log/haproxy.log
&~
Another possibility would be to change the haproxy.cfg file to include the log-tag option so that haproxy uses a different tag [0] and then it'd be dumped into syslog instead but this would break backwards compatibility.
[0] https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#3.1
-log-tag
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1744359/+subscriptions
References