Re: [squid-users] About log file record

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Mon, 10 Dec 2001 10:34:27 +0100

The one you have.

What happens is

1. ICP times out

2. never_direct (or prefer_direct off) tells Squid it still needs to find a
parent

3. Squid goes throught the different normal parent selection methods it has
but did not find any good parent to use

4. You are using never_direct, so Squid simply tries to use any of it's
parents even if none looked too good. Trying is better than rejecting the
request.

The ICP_TIMEOUT_ part is indeed a problem and should be addressed. As you do
not seem to actually use ICP or need it, specify the no-query option on the
cache_peer line to disable the use of ICP to this peer.

The ANY_PARENT part is not a problem. It is only telling you that despite the
fact that ICP failed, Squid ended up doing what you intended.

Regards
Henrik

On Monday 10 December 2001 07.27, Oleg Sorokin wrote:
> ok...but i've only one parent for this child.... no more...
> what else this child can try except this one defined....???
>
>
>
>
> -----Original Message-----
> From: hno@hem.passagen.se [mailto:hno@hem.passagen.se]On Behalf Of Henrik
> Nordstrom
> Sent: Saturday, December 08, 2001 12:40 AM
> To: Oleg Sorokin
> Cc: squid
> Subject: Re: [squid-users] About log file record
>
>
> ANY_PARENT is one of the peer selection mechanisms. When never_direct is
> true, ICP does not find a peer, you do not have a "default" parent and
> so on, squid as a last resort tries any parent..
>
> Regards
> Henrik
>
> Oleg Sorokin wrote:
> > Hello,
> > can anybody describe what does the record in access.log file
> > mean:
> > x.x.x.x urlhttp://somewhere.in.the.net TCP_MISS:ANY_PARENT
> > on a child cache with the record in the squid.conf file:
> >
> > never_direct allow all
> >
> > and both the child & parent caches in the private network.Parent
> > cache doesn't have any upper level caches...
> >
> > that means, as i understand, ( never_direct allow all ) doesn't
> > allow to download pages directly, but only using parent cache
> > which is defined as
> >
> > cache_peer y.y.y.y 3128 0 ...
> >
> > if a child cache can't find requested page in the personal cache it
> > redirects
> > the request for the parent cache, if parent cache can't find the
> > requested page it refers directly...right???
> >
> > so, why the record ANY_PARENT appears in the access.log of the child
> > cache???
> > there should be only ( theoreticaly ):
> >
> > DEFAULT_PARENT ( parent cache )
> > NONE ( self cache )
> >
> > for all requests.....
> >
> > can anybody describe the functionality of such configuration...???
> > pls, really need help for understanding....
> >
> > thanks in advance,
> > Oleg
Received on Mon Dec 10 2001 - 03:00:49 MST

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