Re: [lvs-users] ldirectord: failed check doesn't remove a machine from the pool

Hi Graeme, I found that it was not because OK is an HTTP keyword that the check was not working, but because OK is a substring of BR*OK*EN. Daniel Daniel Lemay wrote: > Hi Graeme, > > You were correct. It is now working. > > Thank you > > Daniel > > Graeme Fowler wrote: >> On Mon, 2009-05-25 at

Re: [lvs-users] ldirectord: failed check doesn't remove a machine from the pool

Hi Graeme, You were correct. It is now working. Thank you Daniel Graeme Fowler wrote: > On Mon, 2009-05-25 at 16:19 +, Daniel Lemay wrote: > >> T 192.168.58.56:7778 -> 192.168.58.2:60760 [AP] >> HTTP/1.1 200 OK..Date: Mon, 25 May 2009 16:06:14 GMT..Server: >> > > Spot the OK abov

Re: [lvs-users] ldirectord: failed check doesn't remove a machine from the pool

On Mon, 2009-05-25 at 16:19 +, Daniel Lemay wrote: > T 192.168.58.56:7778 -> 192.168.58.2:60760 [AP] > HTTP/1.1 200 OK..Date: Mon, 25 May 2009 16:06:14 GMT..Server: Spot the OK above? ldirectord is matching on that. If you make your string something which isn't defined as a response code i

[lvs-users] ldirectord: failed check doesn't remove a machine from the pool

Hi, Here is a part of my config: virtual=x.x.x.x: real=192.168.58.55: masq real=192.168.58.56: masq scheduler=rr protocol=tcp service=http checkport=7778 request="/cmctest.html" receive="OK" checktype=negotiate #virtualhost="xx:7778" Here i