On 12/11/2014 04:20 PM, [email protected] wrote:
Hi David,
Le 11/12/2014 15:26, David Adams a écrit :
We are running 1.5.9 on Centos 6.5. It crashes 10 seconds (give or take a few
seconds) after 1am, 5am, 9am, 1pm, 5pm and 9pm, like clockwork; let's call that
CRASHTIME. Previously we'd been using 1.5.3 on the same hardware for some
months without crashes. Once the crashes started we moved to 1.5.9 but they
continue. If we manually restart it a minute or two before CRASHTIME it stills
crashes when CRASHTIME arrives a minute or two later.
We've looked at all cron jobs that run on the server for anything that could be
causing the problem but found nothing. We've even dumped a process list every
1 second in the minutes before and after CRASHTIME and there is nothing
untoward. Traffic levels don't change and besides, that it happens every 4
hours at exactly the same time suggests it's not traffic related. Presumably
that also rules out any kind of malformed request or similar causing it.
When it crashes the haproxy process just disappears. Nothing in the haproxy
log, or system log. I do realise that it's probably something else on the
server that is causing it, but I guess that haproxy shouldn't die regardless.
1.5.9 was compiled from source.
We're using OpenVZ, which we've been using reliably for years:
vzctl-core-4.6.1-1.x86_64
vzkernel-2.6.32-042stab083.2.x86_64
OpenVZ is not anywhere close to any limits and shows no failures.
Happy to provide any further information to help diagnose the problem.
1am, 5am, 9am,
1pm, 5pm, 9pm
1.5.9
=> coincidence ? This really make me think of a script.
You have the time to downgrade on 1.5.8 to see if it crashs at 8pm!
I'm pretty sure there is bit of wizardry in HAProxy.
R,
Emeric
