I know that in FreeBSD, netstat -an doesn't show the same information as
Linux.  Try using sockstat, and see if that shows squid having an open port.
If you are familiar with OpenBSD, and know this is not the issue, I
apologize.

Start squid and tail the cache.log  You should see a line like:

2004/12/09 09:51:36| Accepting HTTP connections at 0.0.0.0, port 3128, FD
20.

Chris

-----Original Message-----
From: Jeff Schmidt (CACL Tech Asst) [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 7:31 AM
To: [EMAIL PROTECTED]
Subject: [squid-users] Squid not opening tcp port


Hello,
   At work we have a filter server running DansGuardian and Squid on top 
of OpenBSD. It was setup by my predecessor, and has worked so reliably 
that I haven't even looked at it hardly before. Well, last week we 
started having problem with the filtering. I ssh'ed into the filter 
server and started poking around. It seems that when the server boots 
up, and squid gets launched, it will not open any tcp port for incoming 
connections. It is *supposed* to be openning port 3128, the default 
port. However, after launching squid, and confirming that it is running 
by running "ps ax | grep squid", if I run "netstat -an" there is no 
entry for port 3128. In fact, it doesn't appear that squid has opened 
any other tcp port either.

When DansGuardian attempts to launch, it fails to connect to the proxy 
server, and exits.

Does anyone have any idea why squid would be unable to open the tcp 
port? Is there any way I can get debugging info from Squid to find out 
why it is unable to open tcp/3128?

Jeff Schmidt


Reply via email to