Hi Jonathan, Thank you for your reply, but I thought about that, but I can not find any evidence that that's the case. If I look at my last log, I restarted haproxy (after upgrading to the latest dev17) at 18:20LT. The first warning after that is the replication check failing at 19:37. Loglevel is set to notice, maybe that has something to do with it?
Dec 28 18:20:03 localhost haproxy[19206]: Proxy db02_replication started. Dec 28 19:37:13 localhost haproxy[19207]: Server db02_replication/db02 is DOWN, reason: Layer7 check passed, code: 200, info: "OK", check duration: 25ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Regards, Reinout Verkerk Directeur *Trilex Online Assessment* Burgemeester Roelenweg 33 8031 ES Zwolle T: 085 - 401 22 00 M: 06 - 553 76 034 www.trilex.nl On Fri, Dec 28, 2012 at 7:35 PM, Jonathan Matthews <[email protected]>wrote: > On 28 December 2012 17:26, Reinout Verkerk | Trilex > <[email protected]> wrote: > [snip] > > backend db01_replication > > mode tcp > > option httpchk > > server db01 server_ip:3306 check port 9201 inter 5000 fastinter > 2000 > > downinter 2000 rise 2 fall 3 > > > > Dec 28 18:20:32 localhost haproxy[29371]: Server db02_replication/db02 is > > DOWN, reason: Layer7 check passed, code: 200, info: "OK", check duration: > > 44ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, > 0 > > remaining in queue. > [snip] > > Just a guess, but are you /sure/ that that notification isn't the 1st > layer 7 pass /since/ the backend went down? I.e. it's the first of > your "rise 2", but the backend is still down as you've not yet reached > 2 passes? > > Perhaps have a check further up the logs for the actual "DOWN" event. > > As I say, just a guess. I don't have access to a working HAProxy to > check against at the moment ... > > Jonathan > -- > Jonathan Matthews // Oxford, London, UK > http://www.jpluscplusm.com/contact.html >
