Pete DeLaurentis wrote:[...]


Is your private key encrypted?

Kenneth Burgener wrote:[...][...][...]

Sorry, ignore my question.  I just saw your answer to this in another
thread.

Read documentation about pountctl.
Regards.
Lorenzo

2007/12/12, aT <pakistan(at)gmail.com>:[...]

Hello,

I've started the same thread a few month ago:

http://www.apsis.ch/pound/pound_list/archive/2007/2007-09/1189541362000#1189541362000

There is also a solution inside.

Robert

aT schrieb:[...]

What is being written into the messages log? /var/log/messages

Pound writes its error log into that file.

Do "tail -f /var/log/messages" and then in another shell, do the "pound
start", see what it reports.
[...]

> my pound.cfg:[...]

<snip>

Looks ok offhand.  Did you check syslog?
[...]

That syntax may be for an older version of pound.  At least its not for 
any version I've used.

Regards,[...]

Is there anything in /var/log/messages?
Check sockstat to see if anything was on port 80?

Victor Subervi wrote:[...]

Okay. I tail /var/log/messages and get this:
HTTP socket bind 1.2.3.4:80: Address already in use - aborted
This is strange. So I ps wax|grep pound and sure enough, it's up! It wasn't
before. I couldn't get it up before. Go figure! However, when I try and hit
a page, I get this error:
The service is not available. Please try again later.
Now, if it were being passed to :8080, Zope would throw a Zope error, which
isn't happening. I'm lost. Ideas?
TIA,
Victor

On Dec 19, 2007 11:46 AM, Dave Steinberg <dave(at)redterror.net> wrote:
[...]

It appears my response never got sent. Strangely, tail /var/log/messages
showed pound was up! It wasn't before. Couldn't get it to work. But it's up
:-} Nonetheless, when I try and hit the site, which I know is pointed to the
server, I get this error:

The service is not available. Please try again later.

Now, sockstat shows (among other things) this:

root     pound      99968 4  tcp4   1.2.3.4:80    *:*

tail /var/log/messages shows this:

Dec 19 22:44:01 WE62 pound: no back-end "GET /favicon.ico HTTP/1.1" from
190.166.0.59
Dec 19 22:44:08 WE62 pound: no back-end "GET /favicon.ico HTTP/1.1" from
190.166.0.59
Dec 19 22:46:11 WE62 pound: no back-end "GET /robots.txt HTTP/1.1" from
66.249.67.186
Dec 19 23:00:36 WE62 pure-ftpd: (?(at)66.45.243.162) [ERROR] Unable to set up
secure anonymous FTP
Dec 20 00:25:11 WE62 su: admin to root on /dev/ttyp1
Dec 20 00:25:17 WE62 pound: HTTP socket bind 1.2.3.4:80: Address already in
use - aborted
Dec 20 00:27:55 WE62 pound: HTTP socket bind 1.2.3.4:80: Address already in
use - aborted
Dec 20 00:28:25 WE62 pound: no back-end "GET / HTTP/1.1" from 190.166.0.59
Dec 20 00:57:59 WE62 pound: no back-end "GET / HTTP/1.1" from 190.166.0.59
Dec 20 00:59:31 WE62 pound: no back-end "GET / HTTP/1.1" from 190.166.0.59

I presume the 190.166.0.59 is the IP from where I am trying to pull up the
page.

What do?
TIA.
Victor

On Dec 19, 2007 12:17 PM, Michael Toth <pound.mtoth(at)queldor.net>
wrote:
[...]

This is excellent progress!

You know that the problem is not pound. Your back end server is not
responding to pound. Make sure that you have the correct port number. 

The 190.166.0.59 address is your local client (or upstream proxy).

The error "no back-end" means that pound could not establish a connection to
the back-end server.
[...]

Hi Victor,

Your /var/log/messages file should have something like this:

[pound]  HTTP socket bind 1.2.3.4:80: Address already in use - aborted

If so, then you have a web server running in tandem with your pound server.
That's no good. Shut that guy off and try pound again.

Pound will go up and sit idle with no connection escrowing even when none of
the BE servers are responding.

In this case, though, it looks like pound can't get the server socket on
port 80, so it can't handle your connection. Therefore, when you connect
your IE to your "pound server", you're actually hitting your HTTP server
that is also running on that box.

If you do a "netstat -n -a" do you see someone sitting on "*:80" when pound
is not running???
[...]

All this confused me, so I decided to add a line at the end of
/var/log/messages, then try to hit the page and the tail the log. Surprise!
No new lines! Yes, the port is correct (8080). The Zope instance is up and
running. But I still can't hit the page! My new server company tells me
they've routed the URL. What am I missing?
TIA,
Victor

On Dec 19, 2007 1:24 PM, Jacob Anderson <jwa(at)beyond-ordinary.com>
wrote:
[...]

But this is from sockstat:


root pound 99968 4 tcp4 1.2.3.4:80 *:*

root pound 99967 4 tcp4 1.2.3.4:80 *:*

Interestingly, running a tail on /var/log/messages gave me this (since my
manually inserted line):

Dec 20 02:14:33 WE62 pound: no back-end "GET / HTTP/1.1" from 190.166.0.59
Again. Whatever that "no back-end" means.

netstat -n -a shows tcp4 in listen mode, which is pound again.

The *only* thing listening to port 80 is pound. Also, port 8080 is up with a
Zope instance. I'm lost :(
TIA,
Victor


On Dec 19, 2007 1:55 PM, Jacob Anderson <jwa(at)beyond-ordinary.com>
wrote:
[...]

Does sockstat show port 8080 open?
Can you telnet to port 8080 and does that work?

Victor Subervi wrote:[...][...]
>>> -----Original Message-----
>>> From: Victor Subervi [mailto:victorsubervi(at)gmail.com]
>>> Sent: Wednesday, December 19, 2007 8:31 AM
>>> To: pound(at)apsis.ch
>>> Subject: Re: [Pound Mailing List] Can't Get Pound Up
>>>
>>> Okay. I tail /var/log/messages and get this:
>>> HTTP socket bind 1.2.3.4:80 <http://1.2.3.4/>: Address already in use -
>>>       [...]
>>> This is strange. So I ps wax|grep pound and sure enough, it's
>>> up! It wasn't before. I couldn't get it up before. Go figure!
>>> However, when I try and hit a page, I get this error:
>>> The service is not available. Please try again later.
>>> Now, if it were being passed to :8080, Zope would throw a
>>> Zope error, which isn't happening. I'm lost. Ideas?
>>> TIA,
>>> Victor
>>>
>>> On Dec 19, 2007 11:46 AM, Dave Steinberg
<dave(at)redterror.net> wrote:
>>>
>>>       
>>>>> my pound.cfg:
>>>>>
>>>>> ListenHTTP
>>>>>     Address 1.2.3.4
>>>>>     Port    80
>>>>>     Service
>>>>>         # HeadRequire "Host: .*www.example.com.*"
>>>>>         # Note: I tried the above line as well, no go
>>>>>         BackEnd
>>>>>             Address 1.2.3.4
>>>>>             Port    8080
>>>>>         End
>>>>>     End
>>>>> End
>>>>>           
>>>> <snip>
>>>>
>>>> Looks ok offhand.  Did you check syslog?
>>>>
>>>>         
>>>>> Now, the last time I did this, the syntax was like this:
>>>>>
>>>>> LogLevel     2
>>>>> ListenHTTP 1.2.3.4,80
>>>>> UrlGroup ".*"
>>>>> BackEnd 1.2.3.4,8080,1
>>>>> EndGroup
>>>>>           
>>>> That syntax may be for an older version of pound.  At least
its not
>>>> for any version I've used.
>>>>
>>>> Regards,
>>>> --
>>>> Dave Steinberg
>>>> http://www.geekisp.com/
>>>> http://www.steinbergcomputing.com/
>>>>
>>>> --
>>>> To unsubscribe send an email with subject unsubscribe to
>>>>         
>>> pound(at)apsis.ch.
>>>       
>>>> Please contact roseg(at)apsis.ch for questions.
>>>>
>>>>         
>>> --
>>> To unsubscribe send an email with subject unsubscribe to
>>> pound(at)apsis.ch.
>>> Please contact roseg(at)apsis.ch for questions.
>>>
>>>       [...][...]

Yes, sockstat shows 8080 is open and a Zope instance listening to it.
# telnet 202.157.176.193:8080
202.157.176.193:8080: hostname nor servname provided, or not known
The process was open for about a minute.
When I nslookup from the server the URL it shows it's pointed to the server.
When I try nslookup via another server it hangs. Please tell me what you get
from this:
nslookup larmiarmountain.com
TIA,
Victor

On Dec 19, 2007 3:15 PM, Michael Toth <pound.mtoth(at)queldor.net> wrote:
[...]