Human,
I believe pound.pid only contains the process id (for start/stop scripts)
necessary to know which process is pound, but pound.socket (or pound.socket) is
an actual listening control socket. On my machines, I have both pound.pid and
pound.sock:
balancer1:~# ls -l /var/run/pound*
-rw------- 1 root root 5 2007-11-03 06:31 /var/run/pound.pid
srwx------ 1 root root 0 2007-11-03 06:31 /var/run/pound.socket
total 0
balancer1:~# poundctl -c /var/run/pound.socket
0. http Listener 0.0.0.0:80 a
0. Service active (1)
0. Backend (UNKNOWN):0 active (1 0.000 sec) alive
1. Service active (1)
0. Backend (UNKNOWN):0 active (1 0.000 sec) alive
2. Service active (15)
0. Backend 10.0.0.101:81 active (5 0.000 sec) alive
1. Backend 10.0.0.102:81 active (5 0.000 sec) alive
2. Backend 10.0.0.103:81 active (5 0.000 sec) alive
1. HTTPS Listener 0.0.0.0:443 a
0. Service active (15)
0. Backend 10.0.0.101:442 active (5 0.000 sec) alive
1. Backend 10.0.0.102:442 active (5 0.000 sec) alive
2. Backend 10.0.0.103:442 active (5 0.000 sec) alive
2. HTTPS Listener 0.0.0.0:444 a
0. Service active (15)
0. Backend 10.0.0.101:442 active (5 0.000 sec) alive
1. Backend 10.0.0.102:442 active (5 0.000 sec) alive
2. Backend 10.0.0.103:442 active (5 0.000 sec) alive
3. HTTPS Listener 0.0.0.0:445 a
0. Service active (15)
0. Backend 10.0.0.101:442 active (5 0.000 sec) alive
1. Backend 10.0.0.102:442 active (5 0.000 sec) alive
2. Backend 10.0.0.103:442 active (5 0.000 sec) alive
4. HTTPS Listener 0.0.0.0:446 a
0. Service active (15)
0. Backend 10.0.0.101:442 active (5 0.000 sec) alive
1. Backend 10.0.0.102:442 active (5 0.000 sec) alive
2. Backend 10.0.0.103:442 active (5 0.000 sec) alive
-1. Global services
-Miles
Human Servers wrote:
Thanks Mike!
Yes I can see 192.168.0.160:8080 directly without Pound running - and when
Pound is forced to start too. Without Pound running 192.168.0.161 doesn't
resolve, but with Pound running I get the 'Service not available...'
message whereas it should direct to 192.168.0.160:8080.
My pound.conf file (on Linux, I think this is same as pound.cfg) has no
pound.sock reference but has what I assume is the equivalent on FreeBSD;
/var/run/pound.pid.
I think I set the logging to go to httpd-error.log a while ago. But now I'm
just getting errors in /var/log/messages.log. Any logged errors are helpful
right now! =)
As I've written before, Pound should be setup to start at boot, but I have
to force start it now, and even then it doesn't direct from
192.168.0.161:80 to 192.168.0.160:8080. Poundctl shows NO services running
- just gives me instructions to use the command to enable/disable services.
I imagine there is something missing that stops Pound being started at
boot, and this is also stopping the services from running once I have
forced Pound to start.
It's hard to find stuff online re Pound + FreeBSD. I'm sorry to bother
everyone here. I've looked everywhere!
Please keep the ideas coming - I really do need to resolve this today.
Thanks!!!
-----------------------------------------------------------------------------------------------------------------------
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.
