Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B6C7E96CA for ; Mon, 17 Oct 2011 06:55:44 +0000 (UTC) Received: (qmail 67997 invoked by uid 500); 17 Oct 2011 06:55:44 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 67966 invoked by uid 500); 17 Oct 2011 06:55:44 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 67958 invoked by uid 99); 17 Oct 2011 06:55:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Oct 2011 06:55:43 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [196.23.180.100] (HELO zen.co.za) (196.23.180.100) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Oct 2011 06:55:35 +0000 Received: from zenmail.co.za (localhost.localdomain [127.0.0.1]) by zen.co.za (8.13.8/8.13.8) with ESMTP id p9H6t8BA020432 for ; Mon, 17 Oct 2011 08:55:10 +0200 Received: from 196.23.180.209 by zenmail.co.za with HTTP; Mon, 17 Oct 2011 08:55:10 +0200 Message-ID: <73410c40c9dc6b1af4ba69f3a6194a3e.squirrel@zenmail.co.za> In-Reply-To: References: Date: Mon, 17 Oct 2011 08:55:10 +0200 Subject: Re: Parent proxy instead of ICP From: "Henry C." To: users@trafficserver.apache.org User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit On Sat, October 15, 2011 12:39, Henry C. wrote: > I see from the docs and list that ICP is b%rken, so I'm giving parent.config > a try. I've got it configured, but I have no idea whether it's working or > not. I can see the TCP_MISS/200 and subsequent DIRECT-to-origin in squid.log, > but I don't see anything in the parent's log squid.log (ie, I don't know where > to look to confirm that the sibling is consulting the parent about the missed > object). I've turned on debugging in /usr/local/etc/trafficserver/records.config: CONFIG proxy.config.diags.debug.enabled INT 1 and monitored traffic.out (which is where debugging seems to be going), but I can see no connection being made from the sibling proxy to the parent. Not sure where else to look.