Hey all,

I'm having some trouble with Pound.  I have a set of application servers
behind Pound that aren't terribly stable.  However, pound doesn't seem to
kick bad backends out of rotation like it should.  I get log message like
so:

Mar 21 20:33:02 poundcat pound: (b58ffb40) e500 response error read from
xxx.xxx.xxx.203:8080/GET /DmpMediaProvider/displaySlide?id=2809 HTTP/1.1:
Connection timed out (15.017 secs)

This happens over and over again, yet my poundctl output claims it's still
alive.

2. Backend xxx.xxx.xxx.203:8080 active (5 0.000 sec) alive

Any ideas why this is happening?  Earlier this week I had 3/4 of the
backend servers go down and pound was still happily forwarding requests to
the dead servers.  At this point I'm considering writing a script to watch
for those log messages and use poundctl to kick the dead backends out.

I'm running pound 2.5 installed from apt-get on ubuntu server 12.04 LTS.

Thanks,
Landy

Reply via email to