Problems with Squid 2.2S4 on Solaris x86/2.5

From: Reuben Farrelly <reuben.farrelly@dont-contact.us>
Date: Fri, 30 Jul 1999 02:51:41 +1000

Hi,

We are running a Squid 2.2 Stable4 proxy on a Solaris x86 machine and are
experiencing a small problem on it. No additional patches have been
installed on squid (no webdav), and squid was compiled with --async-io and
--enable-digests.

1999/07/30 01:38:35| commBind: Cannot bind socket FD 22 to
203.100.224.20:0: (22) Invalid argument

Yet in squid.conf:
  tcp_outgoing_address 203.100.224.20

And ifconfig -a ...

iprb0:2: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
         inet 203.100.224.20 netmask ffffff00 broadcast 203.100.224.255

netstat -naf inet | grep 203.100 yields:

203.100.224.20.56804 203.10.103.54.80 0 0 8760 0 SYN_SENT
203.100.224.20.56808 165.69.1.187.80 7781 0 8760 0 TIME_WAIT
203.100.224.20.56815 165.69.1.192.80 7717 0 8760 0 ESTABLISHED
...and some others as well.

This interface appears to be working properly, and only one copy of squid
is running. These messages are appearing at sporadic intervals in the
cache log, sometimes several in the course of 2 seconds, then nothing for a
few minutes.

When squid is running, it seems to preform pretty well, but I'd like to
find out what the error message means given nothing appears to be wrong,
and any ideas as to where to start looking for a fix. Or is it a harmless
message only worth ignoring?

Reuben
Received on Sat Jul 31 1999 - 05:05:12 MDT

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