I'm pretty sure that pound would restart its socket and all components,
whatever they may be, upon restarting the service
I never control pound with poundctl, just kill the PID and start pound
again.
I really think the nature of your issue, has to do with the jail. Can you
just remove pound from Jail for now?
If you get it to work with a wget from the pound server, then technically it
should work.
>From following the posts, I'm not sure your having a Pound issue at all,
could just be a Jail issue
If it were me, I would just fire up pound in some alternate test configs,
outside of Jail, and you could also strip the HeadRequire settings.
i.e.
---------------- my pound.conf --------------------------
User "xxx"
Group "xxx"
ListenHTTP
Address 192.168.0.161
Port 80
LogLevel 2
# Virtual Host xxxxx.com
#
Service
BackEnd
Address 192.168.0.160
Port 8080
End
End
End
--------------- end of pound.conf ------------------------
Also, just another follow-up question, are you sure that there's no other
services running on the pound box on port 80? Like a web server for instance
at 192.168.0.161:80 ?
Thank you
-Kiriki
-----Original Message-----
From: Human Servers [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2008 3:30 PM
To: [email protected]
Subject: Re: [Pound Mailing List] URGENT: pound.socket in FreeBSD???
Thanks Simon!
My original post was very clear as to my Pound problem:
http://www.apsis.ch/pound/pound_list/archive/2008/2008-06/1214199931000#1214
199931000
and ended with a series of questions that I hoped would solve this problem
in a simple 'step-by-step' process.
Replies - like yours, tend to jump in at point when information previously
noted by me has been missed or ignored.
However, I appreciate ALL help, and in an effort to resolve this issue, I
have followed every suggestion in this mailing list and replied in detail
to each one, while trying to answer my original questions and adapt these
as I've learned more about Pound.
Thus, replying to you in detail:
Thank you for clearing up the socket creation process. This has removed a
large blackhole in my knowledge, and I feel a lot closer to solving this
problem now.
As I've written before, I can directly view the web page at backend
192.168.0.160:8080.
But I still telnetted to this as per your advice, added GET /, and yes I
got HTML back, which I recognise as being part of the web app.
I performed sockstat (FreeBSD equiv of netstat) and confirmed that Pound is
running and listening to 192.168.0.161:80 - as it should be.
So 1 and 2 are fine.
If you had read a previous mail from me, you would know that I have already
posted logs, and I have already noted that I haven't changed the config
file at all from when Pound originally worked.
var/log/messages:
server pound: no service "GET / HTTP/1.1" from 192.168.0.254 (the router)
And to reply to your bracketed point - I have NEVER believed that poundctl
is necessary for the normal running of Pound.
But to repeat myself (clealy) once agani:
I suspect I just need to be shown how to run the poundctl command to
RE-ENABLE the service.
My original sin was to disable Pound (thinking it has inhibiting SSH - as
again I've written earlier), which I must have done via the poundctl
command, and being a noob at Pound, I'm struggling to re-enable it.
I'm sorry if I seem rude, but I have been very clear in my replies and
questions, and repeating what I wrote only a few emails back seems rather
inefficient.
The reason for the length of my original post, was that I wanted to avoid
being misunderstood and repeating myself as I have thus done since.
I'm happy and appreciative of any and all help I get and I regard Pound as
a great free product.
----------------------------------------------------------------------------
-------------------------------------------
Send big files for free. Simple steps. No registration.
Visit now http://www.nawelny.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.
