[squid-users] Forwarding loop after rebooting.

Sorry if this a double post.

Squid version:squid-2.5.STABLE10
O/S: 5.8 Generic_117350-12 sun4u sparc SUNW,Ultra-80

Hi,

I'm a sysadmin who has inherited a small cluster of squid servers, the
setup is as follows.

4 x Squid Slave Accelerators that accel a master squid.

1 x Master Squid running a custom made redirect script written in perl
that accel a Webserver .

1 x Backend Webserver.

Each slave is running 4 versions of squid accelerating separate sites.

The master runs 4 instances of squid.

The farm is constantly under a fair load - roughly half a million hits a day.

The setup works fine, however, recently when the master server was
taken down for repair, and brought back up again with the same
configuration, it failed to serve content for the

busiest instance, and every request returned is with a TCP_DENIED 403
error. The following error was reported in the cache.log

2006/03/18 06:04:52| WARNING: Forwarding loop detected for:
GET /folder1/subfolder/subfolder/ HTTP/1.0
If-Modified-Since: Sat, 14 Jan 2006 01:44:45 GMT
Host: 192.168.0.10
Accept: */*
From: googlebot(at)googlebot.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1;
+http://www.google.com/bot.html)
Accept-Encoding: gzip
Via: 1.1 slave1.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver), 1.0
master.mydomain.com:80 (webserver/webserver)

This has happened previously when the server rebooted, it is likely
that the master squid service is getting hammered by all slaves as
soon as it is brought back into service, could the fact that it's
under such heavy load as soon as it starts up be causing a problem in
Squid?

I have altered the output to respect privacy of client.
Received on Sat Mar 18 2006 - 06:47:32 MST