Hi Pierre, On Wed, Apr 04, 2018 at 08:12:50AM +0000, Pierre Cheynier wrote: > Hi there, > > We had an issue recently, using 1.8.5. For some reason we ended up entering > in the "No enabled listener found" state (I guess the config file was > incomplete, being written at that time, something like that). > > Here are the logs: > > Apr 03 17:51:49 hostname systemd[1]: Reloaded HAProxy Load Balancer. > Apr 03 17:54:22 hostname haproxy[27090]: [WARNING] 092/175149 (27090) : > Reexecuting Master process > Apr 03 17:54:22 hostname haproxy[27090]: [ALERT] 092/175422 (27090) : > [/usr/sbin/haproxy.main()] No enabled listener found (check for 'b > Apr 03 17:54:22 hostname haproxy[27090]: [WARNING] 092/175422 (27090) : > Reexecuting Master process in waitpid mode > Apr 03 17:54:22 hostname haproxy[27090]: [WARNING] 092/175422 (27090) : > Reexecuting Master process > Apr 03 17:54:22 hostname systemd[1]: Reloaded HAProxy Load Balancer. > > Subsequent reloads were OK. > > The issue here is that it lets HAProxy in an inconsistent state: connections > are almost always in timeout, including the one on the Unix socket, the > healtcheck endpoint set using monitor-uri, etc., until a real stop/start is > done (meaning the parent/worker is restarted itself). > Doing reloads doesn't fix here.
At the moment I have really no idea about this, it should be handled like any config parsing error in theory, since after all, it's just that. The master-worker mechanism is a bit complex as it takes care of many things, and I'm not much at ease with it yet. William's coming back next week, let's check with him if he has an idea about what can happen. Cheers, Willy
