[squid-users] Socket failure errors 2.5stable2

Hi There,

Have been looking through the depths of the archives and have not been able
to find much about this error:

ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://www.google.com/dirhp?
The following error was encountered:
Socket Failure
The system returned:
    (22) Invalid argument
Squid is unable to create a TCP socket, presumably due to excessive load.
Please retry your request.
Your cache administrator is squidboy@admin.com

Generated Wed, 07 May 2003 00:55:10 GMT by prx3.internnal.net
(squid/2.5.STABLE2)

The machine is dedicated to squid, and hardware spec is as follows: E250
2X400 processors, 1GB RAM, network interface is running @ 100 FDX.

At the same time we are seeing a lot of the following in the cache.log:

2003/05/07 14:13:52| commBind: Cannot bind socket FD 77 to *:0: (22)
Invalid argument
2003/05/07 14:13:58| commBind: Cannot bind socket FD 123 to *:0: (22)
Invalid argument
2003/05/07 14:14:07| commBind: Cannot bind socket FD 167 to *:0: (22)
Invalid argument
2003/05/07 14:14:07| commBind: Cannot bind socket FD 157 to *:0: (22)
Invalid argument
2003/05/07 14:14:07| commBind: Cannot bind socket FD 164 to *:0: (22)
Invalid argument
2003/05/07 14:14:07| commBind: Cannot bind socket FD 165 to *:0: (22)
Invalid argument
2003/05/07 14:14:07| commBind: Cannot bind socket FD 142 to *:0: (22)
Invalid argument
2003/05/07 14:14:09| commBind: Cannot bind socket FD 164 to *:0: (22)
Invalid argument
2003/05/07 14:14:09| commBind: Cannot bind socket FD 160 to *:0: (22)
Invalid argument

(22) Invalid argument seems to match the cache.log entry, could this be
related.

Could this be a configuratiuon related issue?

This machine was running 2.4stable7 with no problems, things have been a
little unstable since we upgraded to 2.5stable2.

Any help will be apprecaited....

Regards,
Richard Fuser
Firewall Administrator
Received on Wed May 07 2003 - 00:51:38 MDT