On fre, 2007-07-20 at 12:22 -0500, Scott B. Anderson wrote: > I've done some google searching on this already, but I don't see an answer, just questions about it. While trying to track down this issue where all cache store writes appear to work fine (the cache_dir is working as far as I can tell) but subsequent attempts to read the files out of cache fail, all of them do, greatly increasing the time pages take to load, and in some cases, the fail to load at all. When they do fail to finish loading (they usually start, but fail in the middle) hitting refresh in the browser sometimes works to finish loading the page as well. This problem started for me when I restarted the server for the first time in about a year, a few weeks ago. > > This is what is in my cache.log: > (debug ALL,2) > 2007/07/20 10:53:21| The reply for GET http://www.google.com/intl/en_uk/images/t4_ie.gif is ALLOWED, because it matched 'all' > 2007/07/20 10:53:21| clientReadRequest: FD 67: no data to process ((11) Resource temporarily unavailable) This is completely normal, only seen because you have enabled debugging. The problems you are seeing is somewhere else. Any errors in cache.log without extra debugging enabled? (i.e. just "debug_options ALL,1") What do access.log say? (preferably with log_mime_hdrs on) And what do the cacheability check engine say about the same URL? http://www.ircache.net/cgi-bin/cacheability.py Regards Henrik
Attachment:
signature.asc
Description: This is a digitally signed message part
