Re: Squid2.x on freebsd failes: commBind: Cannot bind socket

First, use netstat to find out if there's already something running on
that port. Second, if the port number <1024, you have to be root to bind
to it.

D

Colin Yuile wrote:
>
> Hi, I have been trying to get squid 2.2 running on a FreeBSD 3.3 machine.
>
> Whenever I try to connect to the proxy I get the following message and squid
> seems to restart (lots of disk noises). I have tried 2.2 and 2.1 with the same
> result. The permissions for dnsserver are ok and the port is not in use (I have
> checked with netstat and have tried different ports).
>
> Any suggestions would be greatly appreciated.
>
> --------------------------Fragment of Cache.log-----------
> 1999/10/19 20:18:19| Starting Squid Cache version 2.2.STABLE4 for
> i386--freebsd3.3...
> 1999/10/19 20:18:19| Process ID 8663
> 1999/10/19 20:18:19| With 2088 file descriptors available
> 1999/10/19 20:18:19| Performing DNS Tests...
> 1999/10/19 20:18:19| Successful DNS name lookup tests...
> 1999/10/19 20:18:19| helperOpenServers: Starting 10 'dnsserver' processes
> 1999/10/19 20:18:19| commBind: Cannot bind socket FD 5 to 127.0.0.1:0: (49)
> Can't assign requested address
> 1999/10/19 20:18:19| commBind: Cannot bind socket FD 5 to 127.0.0.1:0: (49)
> Can't assign requested address
> 1999/10/19 20:18:19| ipcCreate: Failed to create child FD.
> 1999/10/19 20:18:19| WARNING: Cannot run '/usr/local/libexec/dnsserver' process.
> --------------------------
>
> Colin Yuile (colin@ips.gov.au)
>
> IT Manager, IPS Radio and Space Services
> Department of Industry Science and Resources
>
> Ph +61 2 9213 8039
> Fax +61 2 9213 8061
Received on Tue Oct 19 1999 - 22:41:08 MDT