Re: cannot assign socket

From: Duane Wessels <[email protected]>
Date: Mon, 23 Aug 1999 17:16:41 -0600

On Mon, 23 Aug 1999, Paolo Cova wrote:

> I am running Squid Cache version 2.2.STABLE4 on a linux debian system
> with kernel 2.2.8. Squid dies with this message in the log:
>
> 1999/08/23 20:25:37| WARNING: All dnsserver processes are busy.
> 1999/08/23 20:25:37| WARNING: 1 pending requests queued
> FATAL: Too many queued dnsserver requests
> Squid Cache (Version 2.2.STABLE4): Terminated abnormally.
>
> What seems to be causing the problem is dnsserver, and below are the
> repeated error messages in the log. I have looked for a solution on the
> faq and the searchable archives, and read of similar problems from other
> people, but found no solution so far.
> Is squid trying to bind on the same port (0) of my X server or what?
> This problem is independent of what port I assign squid in squid.conf
> and of any tcp and udp incoming and outgoing addresses.
>
> 1999/08/23 20:25:37| helperOpenServers: Starting 5 'dnsserver' processes
>
> 1999/08/23 20:25:37| commBind: Cannot bind socket FD 1 to 127.0.0.1:0:
> (99) Cannot assign requested address
> 1999/08/23 20:25:37| commBind: Cannot bind socket FD 1 to 127.0.0.1:0:
> (99) Cannot assign requested address
> 1999/08/23 20:25:37| ipcCreate: Failed to create child FD.
> 1999/08/23 20:25:37| WARNING: Cannot run
> '/usr/local/squid/bin/dnsserver' process.
>
> Any insight?

Does your linux system have a loopback interface configured?

Can you ping 127.0.0.1?

Duane W.
Received on Mon Aug 23 1999 - 16:51:41 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:48:05 MST