Re: [squid-users] cache_peer configuration is not being reliably hit in Squid 3.2.1

On Thu, Sep 20, 2012 at 2:30 PM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
>
> From your use of client_dst_passthru I assume you have this Squid configured
> as a transparent interception proxy?

Yes, but it is also configured as a direct proxy.

>
> This is apache format for web end-servers. Do you have anything in Squid
> format which has better logging information for proxy details?

Which log format would be the most useful?
>
> Any cache.log traces of LIVE/DEAD status on the peer and indication of how
> that interacts with the access.log timing? It could simply be the peer going
> unavailable for a while.

I've made a change to the logformat here to give some more
information, and set the cache log to ALL,9.

1348118652.804 83 10.3.100.40 TCP_MISS_ABORTED/000 0 GET
http://appldnld.apple.com/iOS6/Restore/041-7181.20120919.lEuOK/iPhone4,1_6.0_10A403_Restore.ipsw
- HIER_DIRECT/150.101.195.90 - - 150.101.195.90 appldnld.apple.com 80
0.0.0.0 0

Primary output for the second that request was processed:
http://www.getoffmalawn.com/static/squid/front.nomatch.log
Peer output for the second that requested was processed:
http://www.getoffmalawn.com/static/squid/peer.nomatch.log

1348118655.149 109 10.3.100.40 TCP_MISS_ABORTED/000 0 GET
http://appldnld.apple.com/iOS6/Restore/041-7181.20120919.lEuOK/iPhone4,1_6.0_10A403_Restore.ipsw
- FIRSTUP_PARENT/127.0.0.1 - - 127.0.0.1 objectcache-peer 60084
127.0.0.1 52393

Primary output for the second that request was processed and hit the
cache: http://www.getoffmalawn.com/static/squid/front.match.log
Peer output for the second that requested was processed and hit the
cache: http://www.getoffmalawn.com/static/squid/peer.match.log

If you need more context from the cache.log files than what I've
provided, let me know how much you need. I'm not entirely sure, but it
does look like the peer was uncontactable - during the second when a
match did not occur, there was very little activity in the peer's
cache.log.

>
>
>>
>> This issue was also present in 3.2.0.19 and 3.2.0.20. Are there any
>> configuration options I may be missing? I've had this working before,
>> in Squid 3.2.0.16 and Squid 3.2.0.17, with the options detailed above.
>>
>> Thanks,
>>
>> Nathan.
>
>
Received on Thu Sep 20 2012 - 06:44:56 MDT