David: You could try running strace -faep HAPROXY_PID -o /tmp/haproxy.strace from 1 minute before the process is getting killed. Then examine the output file for clues. I might not have the options 100% correct.
-Jerry Jerry Champlin Absolute Performance Inc. Phone: 303-565-4401 -- Enabling businesses to deliver critical applications at lower cost and higher value to their customers. NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately. On Thu, Dec 11, 2014 at 8: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. > > > On Thursday, 11 December 2014, 15:22, "[email protected]" < > [email protected]> wrote: > > > Le 11/12/2014 16:20, [email protected] a écrit : > > 1am, 5am, 9am, > > 1pm, 5pm, 9pm > > 1.5.9 > > => coincidence ? This really make me think of a script. > > I mean "a script *issue*" ;-) > > > > -- > Cyril Bonté > > >
