Thank you Dave. I was modifying /usr/local/etc/pound.cfg as specified in the manpage, but it was using /etc/pound.cfg which had been installed by default.
I have managed to get it working now. Ravi Iyer FX Concepts, LLC -----Original Message----- From: Dave Steinberg [mailto:[email protected]] Sent: Tuesday, April 20, 2010 12:23 PM To: [email protected] Subject: Re: [Pound Mailing List] Error with simple config On 4/20/2010 11:58 AM, Ravi Iyer wrote: > > I am migrating an existing setup. > > The old one was -- v 1.8 2004/11/04 13:37:07 > I am installing Version 2.4.4 on RHEL5 4.1.2-48 > > Here is my config file: > > #/usr/local/etc/pound.cfg > User "nobody" > Group "nobody" > RootJail "/usr/share/pound" > LogLevel 5 > ListenHTTP > Address 192.168.10.240 > Port 80 > Service > BackEnd > Address 10.10.2.120 > Port 8080 > End > End > End > > With > $ lynx http://192.168.10.240/ > I get -- Alert!: HTTP/1.0 503 Service Unavailable > > But I am able to connect with > $ lynx http://10.10.2.120:8080/ > > In /var/adm/messages, I see > Apr 20 11:51:18 pound pound: (42064940) connect_nb: error after getsockopt: > Connection refused > Apr 20 11:51:18 pound pound: (42064940) backend 127.0.0.1:8000 connect: > Connection refused > Apr 20 11:51:18 pound pound: (42064940) connect_nb: error after getsockopt: > Connection refused > Apr 20 11:51:18 pound pound: (42064940) backend 127.0.0.1:8001 connect: > Connection refused > Apr 20 11:51:18 pound pound: (42064940) e503 no back-end "GET / HTTP/1.0" > from 192.168.10.240 Is that your entire config? Are you sure pound is actually using that config, and not some other default one? The log lines seem to indicate its connecting to localhost, where you told it to connect to 10.10.2.120. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
