/ Zope / Apsis / Pound Mailing List / Archive / 2009 / 2009-02 / connect_nb: error after getsockopt: Connection refused

[ << ] [ >> ]

[ Pound on pfSense? / "Eric B." ... ] [ Domain-agnostic HTTPS redirects / "(private) ... ]

connect_nb: error after getsockopt: Connection refused
Jon Garvin <jgarvin.lists(at)gmail.com>
2009-02-18 19:28:25 [ SNIP ]
I'm starting to see a lot of these errors in my messages log...

 connect_nb: error after getsockopt: Connection refused

Googling around is seems to be an issue with pound trying to connect to
a backend server that doesn't exist.  Is there any way to tell *which*
backend server?  We've got pound directing traffic for multiple sites,
on multipe domains, with multiple backends each, so it's going to be a
huge PITA to hunt down which, if any, aren't running, or if it's just a
typo in the pound.cfg (and if so, where).  Seems like a future version
of pound could just say something like...

 connect_nb: error after getsockopt: Connection refused on 127.0.0.1:3064

If, that is in fact, what this error means.

Baring waiting for a future version... anybody got any other suggestions?

-- 

http://www.5valleys.com/

http://www.workingwithrails.com/person/8078


MailBoxer