[squid-users] 2.4 stable7 upgrade to 2.5 stable2 problems

From: <[email protected]>
Date: Wed, 16 Apr 2003 10:22:01 +1000

Hi,

Yesterday we upgraded to 2.5stable2, we first upgraded all of our child
proxys and then last night we did the parents.

The children ran all day with no problems on 2.5 stable2 we then updated
the parent machines and all seemed ok

This morning the speed of browsing was very very slow and I noticed the
following in the cache.log

One parent showed these errors:

2003/04/16 08:21:21| commBind: Cannot bind socket FD 902 to xxx.x.xx.xx:0:
(22) Invalid argument
2003/04/16 08:21:21| commResetFD: bind: (22) Invalid argument
2003/04/16 08:21:21| commBind: Cannot bind socket FD 868 to xxx.x.xx.xx:0:
(22) Invalid argument
2003/04/16 08:21:21| commResetFD: bind: (22) Invalid argument
2003/04/16 08:21:22| WARNING! Your cache is running out of filedescriptors
2003/04/16 08:21:21| commBind: Cannot bind socket FD 902 to xxx.x.xx.xx:0:
(22) Invalid argument
2003/04/16 08:21:21| commResetFD: bind: (22) Invalid argument
2003/04/16 08:21:21| commBind: Cannot bind socket FD 868 to xxx.x.xx.xx:0:
(22) Invalid argument
2003/04/16 08:21:21| commResetFD: bind: (22) Invalid argument
2003/04/16 08:21:22| WARNING! Your cache is running out of filedescriptors

The other parent was showing these:

2003/04/16 08:29:03| httpAccept: FD 9: accept failure: (9) Bad file number
2003/04/16 08:29:03| comm_accept: FD 9: (9) Bad file number
2003/04/16 08:29:03| httpAccept: FD 9: accept failure: (9) Bad file number
2003/04/16 08:29:03| comm_accept: FD 9: (9) Bad file number
2003/04/16 08:29:03| httpAccept: FD 9: accept failure: (9) Bad file number

Both parent have identical configuration and are set up as siblings.

I rolled back to 2.4stable7 on the 2 parents and everything started to
operate with no problems, the children proxys are still running 2.5 stable2
with no reported problems.

I have sanity checked the config and cant see a problem.

The other unusual thing is this did not seem to be a issue in a test
environment with no load, it worked perfectly.

Has anyone experienced anything like this? any ideas as to what could be
the problem.

Regards,
Richard Fuser
Firewall Administrator
Received on Tue Apr 15 2003 - 18:22:53 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:14:59 MST