On Wed, Feb 3, 2016 at 3:05 AM Vincent Bernat <[email protected]> wrote:
> ❦ 3 février 2016 00:11 GMT, David Birdsong <[email protected]> : > > > I'm not using consul but am using haproxy in a docker container > > and reloading when backend hosts change registrations. I haven't > > seen this issue. I run using haproxy-systemd-wrapper and HUP that > > process to reload. > > > > does that mean the wrapper ensures that an old process exits and > > forces if it doesn't eventually? > > No, the wrapper is only here to make HAProxy appears more like a > traditional daemon on the signal handling front. The old processes are > expected to stay to handle existing connections. Once you locate an old > process, check why it is here with lsof: lsof -n -p <PID>. You should > see that the process is not listening anymore and is only handling old > connections. If you kill the process, the connections will just break. > right, thanks, but again, I'm familiar w/ haproxy and graceful reloads. I've used lsof -Pnp <pid>, and I find that sometimes an old haproxy process is still listening for new connections. This is the problem I'm trying to ask if anyone else is also seeing. > -- > Follow each decision as closely as possible with its associated action. > - The Elements of Programming Style (Kernighan & Plauger) > >
