Hi Lukas,
On 11/03/2017 02:53 PM, Lukas Tribus wrote:
# service haproxy reload
[ALERT] 306/110738 (29225) : sendmsg logger #1 failed: Resource temporarily
unavailable (errno=11)
Well the destination logging socket is unavailable. I don't think
there is a lot to do here
on the haproxy side, this mostly depends on the destination socket and
the kernel.
I would suggest you use a UDP destination instead. That should be
better suited to
handle logging at this rate.
This is a test system with not much load other than my little 'ab -c 10
...' is creating. We have unix logging everywhere locally, works even
under heavy load.
First i suspected change in config where i added 'log /dev/log local0',
but after commenting that, those messages are still appear. Once per
process after reload, every time when doing quick reloads e.g. for i in
{1..10}; do service haproxy reload; done But sometimes even when not
restarting quickly. I have cronjob that runs after every 3 minutes and
reloads haproxy, then this error appears sometimes, not each time.
another bug about processes never closing after reload
Unless you are hitting a bug already fixed (make sure you use a
current stable release), it's
likely that long running sessions keep haproxy running.
Use the hard-stop-after directive to limit the time haproxy spends in
this state:
https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#3.1-hard-stop-after
I would not comment hanging process bug more under this thread, because
it's off topic. Will create new thread for that. Planned anyway, but
wanted first create reproduction instructions. So far, it's quite random...
Regards,
Veiko
