Re: Stale UNIX sockets after reload

2016-05-10 Thread Willy Tarreau
On Tue, May 10, 2016 at 04:01:24PM +0200, Mehdi Ahmadi wrote: > In the case of `stop` - I image that the stale / former sockets can be > listed using: > `sudo lsof | grep SOMETHING` ? No since there's no more process. What you see is just a file system entry. If you try to connect to it using

Re: Stale UNIX sockets after reload

2016-05-10 Thread Mehdi Ahmadi
In the case of `stop` - I image that the stale / former sockets can be listed using: `sudo lsof | grep SOMETHING` ? I'm wondering if an additional shell level checks / cleanup can be done in such cases were related PID's would be killed? - or perhaps there's a core part to how socets are created

Re: Stale UNIX sockets after reload

2016-05-10 Thread Willy Tarreau
On Mon, May 09, 2016 at 04:12:32PM +0200, Pavlos Parissis wrote: > On 09/05/2016 02:26 , Christian Ruppert wrote: > > Hi, > > > > it seems that HAProxy does not remove the UNIX sockets after reloading > > (also restarting?) even though they have been removed from the > > configuration and

Re: Stale UNIX sockets after reload

2016-05-09 Thread Pavlos Parissis
On 09/05/2016 02:26 μμ, Christian Ruppert wrote: > Hi, > > it seems that HAProxy does not remove the UNIX sockets after reloading > (also restarting?) even though they have been removed from the > configuration and thus are stale afterwards. > At least 1.6.4 seems to be affected. Can anybody else

Stale UNIX sockets after reload

2016-05-09 Thread Christian Ruppert
Hi, it seems that HAProxy does not remove the UNIX sockets after reloading (also restarting?) even though they have been removed from the configuration and thus are stale afterwards. At least 1.6.4 seems to be affected. Can anybody else confirm that? It's a multi-process setup in this case