On Thu, Dec 11, 2014 at 10:40 AM, David Adams <[email protected]> wrote: > Yes, I am quite sure it's something external to the haproxy process which is > somehow interfering with it, but I can't figure out what. As I mentioned, > looking at a list of processes before and after haproxy stops doesn't reveal > any changes in what was running, i.e. it's not like some script runs just > before haproxy dies.
You may want to bypass the init script and run haproxy in a screen and wait for the crash and see what is returned there to stderr/stdout. You might get a kill signal number from that or another useful message.
