I confirm that adding "no option start-on-reload" resolves the reload issue.
I'll report to dataplane documentation. вт, 4 февр. 2020 г. в 16:01, William Lallemand <[email protected]>: > On Tue, Feb 04, 2020 at 12:48:18AM +0500, Илья Шипицин wrote: > > > > вс, 2 февр. 2020 г. в 22:58, Tim Düsterhus <[email protected]>: > > > > > > > > [...] > > > > > > Feb 02 20:50:07 xxx systemd[1]: haproxy.service failed. > > > > > > > > > > ... leading to the unit being stopped. > > > > > > > > > > So you would have to find out with the dataplane API dies. My > educated > > > > > guess would be that it fails because the port is already being in > use > > > by > > > > > the old dataplane API process. > > > > > > > > > > > From what I understand of the dataplaneapi, it is reloaded upon a USR1 > > > signal, > > > signal which is sent by the master process upon a reload. > > > > > > So you probably just need to add "no option start-on-reload" in your > > > program > > > section to prevent HAProxy to launch the dataplane-api again. > > > > > > > > > thank you, I'll try > > > > maybe it should be added to docs. > > > > Could you open an issue on the dataplaneapi bugtracker? Because I'm not > sure > this is the right behavior. > > The doc speaks about "no option start-on-reload" but only if used by > docker. > > > https://www.haproxy.com/documentation/hapee/1-9r1/configuration/dataplaneapi/ > > -- > William Lallemand >
