On Mon, 11 Nov 1996, Don Rolph <w-rolph@ds.mc.ti.com> wrote:
> In our case, it looks like the ip address of the parent changed during
> servicing over the weekend. Since squid continued to run, it used the
> previously cached ip address of the parent. Of course since this had
> changed.....
>
> Restarting squid fixed the problem, of course, and it does not appear
> that my case is a serious excursion from normal operations.
In my case IP address of parent is constant and only link is down time to time
> > After a long successful working my Squid-1.0.18 on FreeBSD machine confugured
> > as used behind firewall begun to mark parents as dead when a single external
> > link is down. Link is down for a short time frequently enough
> > It's interesting that usually when line is down
> > [11/Nov/1996:15:10:25 +0300] comm.c:372: connect: 193.233.9.14:3128: (65) No route to host.
> > [11/Nov/1996:15:10:32 +0300] comm.c:372: connect: 193.233.9.14:3128: (65) No route to host.
> >
> > but sometimes
> > [11/Nov/1996:15:11:15 +0300] neighbors.c:563: neighborsUdpPing: Detected DEAD PARENT: hawk.landau.ac.ru
> > [11/Nov/1996:15:11:15 +0300] neighbors.c:563: neighborsUdpPing: Detected DEAD PARENT: webcache1.free.net
> >
> > and only reload (by "kill -HUP" or "kill -KILL") forces "revive" a parent
> >
Serge Krashakov
Received on Mon Nov 11 1996 - 22:49:11 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:33:32 MST