after reboot, 1 vs does't work and one only works for ~10 minutes after reboot

0

This is very strange, we have Kemp doing forwarding and ssl for 2 servers on one ip, doing Http-->https. I did a reboot for the first time in a month or so, and now, on boot, one of the servers will work fine for a few minutes, the other doesn't work at all, and then after a couple minutes the first one dies too.  the warning log shows nothing, and no changes have been made other than reboot. 

the one that's always dead says err_invalid response

in the warning log i see this 

Sending Redirect responses due to failed Real Servers
but when I look at real servers i see them both as up, and nothing has changed on either of them.

 

1 comment

Avatar
0
Tony Vaughan

Morning Aaron,


just to confirm the setup,

do you have one virtual service handling HTTP traffic, sending to two servers
and one virtual service handling HTTPS/SSL traffic, sending to two servers

or

one virtual service redirecting HTTP to HTTPS/SSL
and one virtual service handling HTTPS/SSL traffic, sending to two servers

by default the real servers will always be up,
i.e. after the LoadMasters have booted the initial health status of the real servers will be up, once a check is complete (default 9 seconds) then the status will stay up or switched to failed

in the logs you should normally see the reason the health check has failed
e.g. Removing RS <RS IP:Port> from VS <VS IP:Port> (<VS Name>) - Timeout waiting for data
do you see anything like this in the logs?