Re: [Zenloadbalancer-support] Monitoring IP/Port and Farm-Gaurdian backend

[José G. <jos...@gm...>]

Hi, Genoint.

FarmGuardian is not the problem. FarmGuardian executes a script changing
the parameter HOST for the backend's IP and the parameter PORT for the
backend's PORT.

There are some examples of scripts that you can use in Zen Load Balancer,
but that does not mean that is the script you need to check your backends.
Use it as base to develop your own script that can tell you when your app
is up and down.

Best regards.


2014-09-04 18:35 GMT+02:00 Genoint <ge...@ya...>:

> So I have raised this with our development team and they aren't happy. :)
>   There could be a situation when farm guardian doesn't get a good response
> as the application is down but the server is still listening on ip/port. Is
> there a way to get zen to mark a node down if farm guardian doesn't get an
> expected response but ip/port are still responding?
>
> On Sep 4, 2014, at 10:03 AM, José García <jos...@gm...>
> wrote:
>
> FarmGuardian has evolved from 3.02 to 3.05 in performance and low
> resources needed, but the double check is active in 3.05 too.
>
> Best regards.
>
>
> 2014-09-04 15:57 GMT+02:00 Genoint <ge...@ya...>:
>
>> And it is the same in 3.05?
>>
>> Thanks for all of the help.
>>
>> On Sep 4, 2014, at 9:52 AM, José García <jos...@gm...>
>> wrote:
>>
>> It uses both, IP/port and FarmGuardian check. Obviously if the IP and/or
>> port are down, FarmGuardian will mark it as down too...
>>
>> Best regards.
>>
>>
>> 2014-09-04 15:36 GMT+02:00 Genoint <ge...@ya...>:
>>
>>> Thanks for the info I will debug using your method. One more question;
>>> when I am using farm guardian in 3.02 does it still monitor the site with
>>> ip/port for up/down status or does it use farm guardian only?
>>>
>>> On Sep 4, 2014, at 9:31 AM, José García <jos...@gm...>
>>> wrote:
>>>
>>> Hi, John.
>>>
>>> I don't know if update to 3.05 is going to fix your issues. I only tell
>>> you that migrate is a good option because your version es very obsolete,
>>> and FarmGuardian now works better and needs less resources than the 3.02
>>> version.
>>>
>>> In the other hand, you need to know why the script tells you that your
>>> application is up when it's down. Launch the script by hand using the
>>> command line and debug it. Perhaps your applications are not responding the
>>> way you think they do, or when you access to the backend by IP and port the
>>> response is not the same as when you access by URI...
>>>
>>> Best regards...
>>>
>>>
>>> 2014-09-04 14:54 GMT+02:00 Genoint G <ge...@ya...>:
>>>
>>>> So 3.05 will fix the issues I am having in the scenario I described?  I
>>>> am just trying to use Farm Guardian to detect up/down state by searching
>>>> for specific text on site.  Am I to assume this doesn't work correctly in
>>>> 3.02 then?
>>>>
>>>> -John
>>>>
>>>>
>>>>   On Thursday, September 4, 2014 7:55 AM, José García <
>>>> jos...@gm...> wrote:
>>>>
>>>>
>>>> Hi, I recommend you to update to 3.05 version. There are lots of
>>>> improvements in HTTP profiles and FarmGuardian from 3.02 versions.
>>>>
>>>> You can not migrate from 3.02 to 3.05, so you will need to recongigure
>>>> your farms.
>>>>
>>>> Best regards...
>>>>
>>>>
>>>> 2014-09-02 22:07 GMT+02:00 Genoint G <ge...@ya...>:
>>>>
>>>> Hi,
>>>>
>>>> We are currently running ZEN LB 3.02 and we currently have a situation
>>>> where our development servers have two different applications running on
>>>> the same port on the same server.  The application is differentiated by
>>>> different URI paths and the ports are 7451 and 7452.  We cannot use simple
>>>> ip/port checks for monitoring the health of backend servers because if we
>>>> take down application 1, application 2 still uses the port and ZEN will
>>>> still think its up.  Therefore we have opted to use Farm Guardian for
>>>> health checks, but it doesn't seem to be working.
>>>>
>>>> Here is the Farm Guardian script:  it is checking for "Login" in the
>>>> path /cas/login
>>>>
>>>> check_http -w 9 -c 9 -H HOST -u /cas/login -s 'Login' -p PORT
>>>>
>>>> It is checking for "Login" in the path /cas/login, after adding this
>>>> both sites remain up.  However, if we take down this application Zen still
>>>> thinks this server is up, even though you cannot manually browse to the
>>>> path, its down.  It seems as though Zen is still using ip/port monitoring.
>>>> The only way we could get ZEN to see this as down is to shut down both
>>>> applications listening on the port.
>>>>
>>>> Farm Guardian log below:  backends are http, IP's changed for security
>>>> reasons.  In this situation we had shutdown the application running
>>>> /cas/login on both 7451 and 7452 ports, but Zen still marked it as up.  We
>>>> let it stay for 10 mins and there was no change.
>>>>
>>>> execution in Tue Sep 2 15:44:49 2014 ::
>>>>  server[0]: 192.168.x.11:7451
>>>> Backend status 0: active
>>>> command: /usr/local/zenloadbalancer/app/libexec/check_http -w 9 -c 9 -H
>>>> 192.168.x.11 -u /cas/login -s 'Login' -p 7451
>>>> No state changed for the backend.
>>>>  server[1]: 192.168.x.11:7452
>>>> Backend status 1: fgDOWN
>>>> command: /usr/local/zenloadbalancer/app/libexec/check_http -w 9 -c 9 -H
>>>> 192.168.x.11 -u /cas/login -s 'Login' -p 7452
>>>> No state changed for the backend.
>>>> The servers timeout is: 45
>>>>  checking:
>>>>  farmname: CASDEV2HTTP
>>>>  timeout: 45
>>>>  blacklist:
>>>>  timetocheck: 10
>>>>  portadmin: /tmp/CASDEV2HTTP_pound.socket
>>>>  server[0]: 192.168.x.11:7451
>>>>  server[1]: 192.168.x.11:7452
>>>>  check: check_http -w 9 -c 9 -H HOST -u /cas/login -s 'Login' -p PORT
>>>>
>>>> Thanks in advance for your help.
>>>> John G
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Zenloadbalancer-support mailing list
>>>> Zen...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>