On Tue, Apr 5, 2011 at 12:28 PM, Tory M Blue <tmblue@xxxxxxxxx> wrote: > On Tue, Apr 5, 2011 at 12:32 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: >> On 05/04/11 17:09, Tory M Blue wrote: >>>> >>>> Problem is that this is happening in every cache server. Even if I >>>> start clean I get these. What debug level/numbers can I use to track >>>> this down? This happens constantly, so ya as you said something is >>>> going on but it doesn't appear to be, someone mucking with the cache >>>> or other odity, since it happens with new fresh squid instances and is >>>> happening a lot.. >>>> >>>> Thanks Amos >>>> >>>> Tory >>>> >>> >>> hmmm >>> >>> 746665-2011/04/04 21:57:05| storeClientReadHeader: swapin MD5 mismatch >>> 746729-2011/04/04 21:57:05| 1949E8301BB74F8CD2E16773A23B8D26 >>> 746784-2011/04/04 21:57:05| 3BD0B17768C3A6F6A85A4C4684A311C0 >>> >>> >>> That has to be the cause, but it makes no sense. Why would they be >>> there with a fresh cache install, on 3 different servers.. >> >> >> What OS filesystem is this using? >> does it do any sort of fancy file de-duplication or compression underneath >> Squid? >> is there any system process which might do that sort of thing? >> >> Can you try 2.7.STABLE9? >> >> If this is ufs/aufs/diskd, do you have the ufsdump tool installed with >> Squid? that can dump the content of cache files for manual checking. > Nope clean install on 2.7STABLE9 and the first hour or so no error messages but now I'm getting them 2011/04/06 12:33:46| storeClientReadHeader: no URL! 2011/04/06 12:34:02| storeClientReadHeader: no URL! 2011/04/06 12:34:12| storeClientReadHeader: no URL! 2011/04/06 12:34:12| storeClientReadHeader: no URL! 2011/04/06 12:34:33| storeClientReadHeader: no URL! 2011/04/06 12:34:34| storeClientReadHeader: no URL! 2011/04/06 12:34:35| storeClientReadHeader: no URL! 2011/04/06 12:34:37| storeClientReadHeader: no URL! 2011/04/06 12:35:03| storeClientReadHeader: no URL! 2011/04/06 12:35:03| storeClientReadHeader: no URL! 2011/04/06 12:35:40| storeClientReadHeader: no URL! 2011/04/06 12:35:50| storeClientReadHeader: no URL! 2011/04/06 12:35:52| storeClientReadHeader: no URL! 2011/04/06 12:36:17| storeClientReadHeader: no URL! 2011/04/06 12:36:18| storeClientReadHeader: no URL! 2011/04/06 12:36:18| storeClientReadHeader: no URL! Since this was a absolutely fresh install, clean cache directory, this is either a request coming in or something. We did make some changes with headers, but since this was a clean install, can't believe it's the apache changes from the app servers. Very strange, would like to identify Tory
