Comment 1 for bug 1549753

Contrary to what's stated in the Bug Description, the problem is not related to the log socket not being available when the haproxy process starts.

The problem is related to net.unix.max_dgram_qlen being too small (10) by default. By increasing net.unix.max_dgram_qlen to 100 (for example) the problem goes away.

See https://bugzilla.redhat.com/show_bug.cgi?id=1257690 for example.

I am going to change the Importance from High to Medium, as the consequence of this issue is just the loss a few log entries at HAProxy startup time.