Search squid archive

Re: Need better debug_options values to track down cache MISSes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Greg,

I use this combo to check if request is cached or no and why:
debug_options 20,9 27,9 31,9 70,9 82,9 22,9 84,9 90,9

Then in cache.log file you can search by 'YES' or 'NO' (uppercase) to see if the content is cacheable (and cached) or not and the reason of this decision. Hope this will help.

Best wishes,
Pavel

On 02/24/2015 03:54 PM, Greg wrote:
Hi all,

I'm new to squid administration, with basic *nix admin skills. My task now is to replace an old Squid reverse proxy server (3.1.15 on an old Fedora) with a new one (Squid 3.3.8 on Ubuntu 14 LTS) and ran into a problem.

I've spent 2 days tweaking-googling-debugging, now looking for some help...

Problem is, with the ~same configuration, the old Squid caches HTML pages well and the new doesn't. This is a major concern, we're using Squid exactly to do that and get the load off our appservers.

In this first mail, I'm only asking for a hint on what debug_options to use. In previous list emails I've seen that some details help, so here they are:
- Reverse proxy, port 80 only, one uplink straight to the app servers.
- Pretty standard configuration, standard refresh_patterns.
- Disk and memory cache, disk cache initialised with -z.
- Clocks are in sync (except for the old proxy server) using ntpd.
- Squid gives HITs for favicon.ico and RSS feeds only - these have different headers and mimetypes compared to HTML files (and that's by design).
- This new server seems to save accessed HTML files on disk but still gives X-Cache-Lookup:MISS for all of them later.
- I've found the debug_options sections page but section names are ambiguous for someone who's not a Squid programmer. I had to download the source code, analysed it and tried "debug_options 11,1 22,6 85,3 88,5 33,1 31,5 90,5" which is too much and "debug_options 88,5 85,5 22,6 11,5 33,1" which might be too little.
- Headers look okay (Cache-Control, Pragma, Vary), stale/fresh calculation looks okay (pages are deemed fresh) in the debug log.
- The best I got so far is this: "client_side_reply.cc(1618) identifyFoundObject: clientProcessRequest2: StoreEntry is NULL -  MISS", even for pages I see in the disk cache -- I'd like to know why does it occur, probably need some more good debug_options. I don't understand the code too well, don't know which direction to take.

Please suggest some more good debug_options to continue with.

Best regards,
Greg

PS. Also, I'll submit another mail with the details of the problem + the config, hoping someone spots a problem right away.



_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux