> -----Original Message----- > From: Daniel Lim [mailto:Daniel.Lim@xxxxxxxxxxxxxxxxxxx] > Sent: Monday, July 11, 2005 10:45 PM > To: squid-users@xxxxxxxxxxxxxxx > Subject: Detected DEAD Parent > > > Hi, > We have Squid-2.5.STABLE7 running on production SuSE Linux SLES 8.1. > Sometimes when the proxy encountered "Detected DEAD Parent" it recovered > and revived itself see errors enclosed below. But it also happened on > few occasions when squid failed to REVIVE so a stop/start or reboot to > restart squid normally fixed the problem. > When the problem occurred and squid could not revive no users' browser > could connect to the internet. But we also have a test box which worked > OK with the same parent while the production box was experiencing > connection problem. The > test box is hardly used though, NO users connecting to it except me. > The errors said it all that the parent was having problem but why the > test box was NOT experiencing the same problem? The parent is also the > firewall. > Is it possible a bug that casuing Squid not to REVIVE? Will an upgrade > to higher STABLE revision solve the problem? > > Many thanks. > > Regards, > Daniel Lim Check your firewall/parent squid. Is it possible that you are hitting a connection rate limit (SYN flood prevention)? In other words, your inner squid server is making new connections to the firewall at a rate that the firewall perceives as an attack. If you have specified in your squid.conf "never_direct allow all" then squid will give errors when all parent proxies become unresponsive. Chris
