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

Thanks for all the responces. Duane hit the nail on the head. Running netstat
showed that there was no loopback interface configured. This should have been
configured by default. Examinig the rc script that configures the network
interfaces revealed that it was getting a list of all interfaces using ifconfig
-l, but failed to configure them. Adding lo0 explicitly solved the problem.

Again, many thanks for the help.

Colin

On 20-Oct-99 Duane Wessels wrote:
>
>
> On Wed, 20 Oct 1999, 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.
>> --------------------------
>
> 11.34 commBind: Cannot bind socket FD 5 to 127.0.0.1:0: (49) Can't assign
> requested address
>
> This likely means that your system does not have a loopback network
> device, or that device is not properly configured. All Unix systems
> should have a network device named lo0, and it should be configured
> with the address 127.0.0.1. If not, you may get the above error
> message. To check your system, run:
>
> % ifconfig lo0
>
> The result should look something like:
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet 127.0.0.1 netmask 0xff000000
>
Received on Wed Oct 20 1999 - 16:12:29 MDT