Hi, I think one problem is that you really seem confused and your audience is also confused.
> Hi everyone, > > Sorry for the drama - but I have to know ASAP whether the FreeBSD install > of Pound uses a pound.socket or pound.sock file or neither. > > If you've followed my issue so far: > > 1. Months ago I posted for a solution here but no one replied. > 2. Now I URGENTLY need to get Pound going to launch a web app on another > server. (SAAS = $, livelihood..., my families future.) > 3. The problem was caused by me temporarily disabling Pound to get SSH > going. I have absolutely no idea what relation those two have. So whatever you did to 'get SSH going' may have broken your pound but I really can't think why. > 4. I now have to force Pound to start after boot. > 5. Once started the listening address: 192.168.0.161:80 returns a 'Service > not available message'. > 6. I can view the backend 192.168.0.160:8080 with/without Pound running. What and from where can you 'view'? That's an important question. > 7. I'm using FreeBSD. I have a pound.pid file but no pound.sock/(et). I > doubt I deleted/moved this file. > 8. If pound.sock(et) isn't need on FreeBSD, I suspect I just need to be > shown how to run the poundctl command to re-enable the listerner. First, forget about the socket and about poundctl. The socket is a socket and not a normal file and has no file content. It's being created once pound starts up by pound itself. If you remove the corresponding config line pound will still start and work but you just can't use poundctrl (which is not needed for basic functioning of pound!). So, I suggest you try to do things step by step. Maybe like this. 1) Log in to your pound server (I think it is 192.168.0.161, right?). Now test the connection to your backend with telnet 192.168.0.160 8080 If that works, try a 'GET /' and you should see some html garbage and telnet should exit. If that works your backend is fine. 2) Start pound. Check that it is up and running with ps, then check that it is listening on the correct host:port. On Linux this could be easily done with netstat -lpn | grep pound The netstat command may need different args on FreeBSD but the manpage should tell. Then you see get something like this: tcp 0 0 192.168.0.161:80 0.0.0.0:* LISTEN 7808/pound It clearly shows that process pound is listening on 192.168.0.161:80. If it doesn't show up you may check with 'netstat -l' whether another process already listens on 192.168.0.161:80. 3) If 1 and 2 are fine, it should only be a problem with your pound config. Check that you get logs from pound when accessing 192.168.0.161:80 and try to find out why it fails if it still does. One more suggestion: Many people told you what to check but you didn't reply in detail. Maybe you first confirm 1 and 2 now and me or others may help to get it going. Simon -- To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions.
