On 8/27/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > I'm getting a lot of: > > Aug 27 20:42:21 slbd[684]: Poll failed to start TCP to 192.168.1.2:443 > Aug 27 20:42:21 slbd[684]: Poll failed TCP for 192.168.1.2:443 > Aug 27 20:42:21 slbd[684]: Poll failed to start TCP to 192.168.1.3:443 > Aug 27 20:42:21 slbd[684]: Poll failed to start TCP to 192.168.1.3:80 > Aug 27 20:42:21 slbd[684]: Poll failed TCP for 192.168.1.2:80 > Aug 27 20:42:21 slbd[684]: Poll failed to start TCP to 192.168.1.3:80 > Aug 27 20:42:26 slbd[684]: Switching to sitedown for VIP 12.34.56.78:443 > Aug 27 20:42:26 slbd[684]: Switching to sitedown for VIP 12.43.56.78:80 > > seemingly at random. These servers are up and running just fine so I'm not > sure what the problem might be (yes i can even hit them through the VIP over > the internet and load balances just fine). How do I go abou debugging this > to give you guys a better idea of what might be wrong? Slbd's logging is > kind of unhelpful as well. It logs every 5 seconds that the poll fails but > then doesn't log when its back up. It seems it would be better if it logged > when it went down and when it came back up.
This appears more of a "I cannot even open a socket error" other than "I cannot connect to the target". SLBD apparently needs some more work. We had to port a lot of changes from it being against a earlier version of pf. Scott
