Hello Veiko,
2017-11-03 12:21 GMT+01:00 Veiko Kukk <[email protected]>: > Hi, > > I noticed, while trying to reproduce conditions for another bug about > processes never closing after restart, that sometimes reload causes logging > errors displayed. > > Following config section might be relevant: > > global > log /dev/log local0 > nbproc 3 > > defaults > log /dev/log local0 > > frontend foo > log /dev/log local1 > > ... > > # 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. > 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 Regards, Lukas
