I tried this. I ran it like this:
/usr/local/sbin/haproxy -db -f /etc/haproxy/haproxy.cfg
which obviously didn't return as the process ran. Then at the crashtime (a few
seconds past 17:00), that process terminated and the terminal just showed:
aborted
I then restarted the process in the normal way.
On Thursday, 11 December 2014, 15:45, Tait Clarridge <[email protected]>
wrote:
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.
