Hi Mark, Hi All, On Tue, Sep 02, 2014 at 02:59:32PM +0100, Mark Brooks wrote: > Hello All, > > Im testing starting the backend servers as disabled in the config > according to the manual - > "disabled > The "disabled" keyword starts the server in the "disabled" state. That means > that it is marked down in maintenance mode, and no connection other than the > ones allowed by persist mode will reach it. It is very well suited to setup > new servers, because normal traffic will never reach them, while it is still > possible to test the service by making use of the force-persist mechanism." > > my config line looks like > server RIP_Name 192.168.66.50 weight 100 cookie RIP_Name > agent-check agent-port 12345 check port 80 inter 2000 rise 2 fall 3 > minconn 0 maxconn 0 on-marked-down shutdown-sessions disabled > > The server comes up in maintenance mode as you would expect, but then > using the unix socket commands I am unable to get the server into the > up state. > > I have tried > > 'set server VIP_Name/RIP_Name state ready' > > and > > 'enable server VIP_Name/RIP_Name' > > and the stats page reports the server as 'DOWN(agent)' > > If I remove the feedback agent configuration so my server line looks > like the following - > > server RIP_Name 192.168.66.50 weight 100 cookie RIP_Name check port > 80 inter 2000 rise 2 fall 3 minconn 0 maxconn 0 on-marked-down > shutdown-sessions disabled > > its possible to get the service to come up using the aforementioned > socket commands.
For the record the following patch, which I posted a few moments ago, it intended to address this problem. [PATCH 1/2] BUG/MEDIUM: Do not set agent health to zero if server is disabled in config
