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
<jose.garcia.rob...@gmail.com> 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 <geno...@yahoo.com>:
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
>Zenloadbalancer-support@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
