Re: squid error

On Tue, 11 Jul 2000, Sergio Henrique Oliveira Pereira (EDB) wrote:

> Hi all,
> I'm using squid2.3ST2 with LDAP authentication and today some
> strange happened. In my cache.log the error message appear:
>
> ---cut----
> WARNING: Cannot run '/path/to/squid_ldap_auth' process
> commbind: Cannot bind socket to FD 2 to 127.0.0.1:0: (126) Cannot assign
> requested address
> ---cut----

Either you don't have a loopback interface, or you have the Linux
bug that comes up every so often.

==============================================================================

  11.37. 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

==============================================================================

  14.5. Linux

  14.5.1. Cannot bind socket FD 5 to 127.0.0.1:0: (49) Can't assign
  requested address

  Try a different version of Linux. We have received many reports of
  this ``bug'' from people running Linux 2.0.30. The bind(2) system
  call should NEVER give this error when binding to port 0.

==============================================================================

  14.2.4. FreeBSD 3.3: The lo0 (loop-back) device is not configured on
  startup

  Squid requires a the loopback interface to be up and configured. If
  it is not, you will get errors such as ``commBind''.

  From FreeBSD 3.3 Errata Notes
  <http://www.freebsd.org/releases/3.3R/errata.html>:

       Fix: Assuming that you experience this problem at all, edit
       /etc/rc.conf and search for where the network_interfaces
       variable is set. In its value, change the word auto to lo0
       since the auto keyword doesn't bring the loop-back device up
       properly, for reasons yet to be adequately determined.
       Since your other interface(s) will already be set in the
       network_interfaces variable after initial installation, it's
       reasonable to simply s/auto/lo0/ in rc.conf and move on.

  Thanks to Robert Lister <mailto:robl at lentil dot org>.
Received on Wed Jul 12 2000 - 00:50:45 MDT