On Wed, 2010-06-30 at 16:26 -0700, Adam Olsen wrote: > Recently, we've started getting the following errors in the pound log: > > Jun 30 17:09:10 socproxy pound: (7f6549145950) connect_nb: poll timed out > > After a number of these, the log eventually floods with the following errors: > > Jun 30 17:09:10 socproxy pound: (7f654ccaf950) e503 no back-end "GET > /cgi-bin/javascript/tags.js HTTP/1.1" from 124.138.56.2 > > ... for every request. The site is basically down at this point. > Every request fails with e503. Restarting pound fixes the problem. > > What could be causing this? Here is what our pound.cfg looks like:
Could it be that you run out of sockets? With a slow network you could have an awful lot of sockets waiting for a connection. -- Robert Segall Apsis GmbH Postfach, Uetikon am See, CH-8707 Tel: +41-32-512 30 19 -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
