next up previous contents index
Next: 6.10 Troubleshooting Up: 6 The Object Cache Previous: 6.8.7 Summary: object caching

6.9 Meanings of log files

 

The Cache supports logging to four files, the locations for the first three of which are specified from the cached.conf file. (The final file is always stored in the file log in the cache's data directory):

  1. cache_access_log: this is Cache access logfile, which logs the hits and misses. The format of this file is one line per access, with the following fields:

    1. timestamp (the standard UNIX count of seconds since midnight Jan 1, 1970)
    2. retrieved URL
    3. client's IP address
    4. object size (only non-zero when there's a hit)
    5. hit/miss indicator. This field encodes the access method (TCP, UDP, and our binary protocol), HIT/MISS, and occasionally a reason (e.g., TCP_MISS_TTL means it was a miss because the object had timed out). Note: prior to Harvest Version 1.2, the client's IP address was not logged to this file.

  2. cache_log: this file contains logs of error messages, such as errors binding to sockets that are already in use (e.g., because you restarted the cache too quickly; see Section 6.10).

  3. cache_hierarchy_log: this is the hierarchical caching access logfile.

  4. data/log: this file contains the mapping from The cache stores objects on disk as numbered files inside of numbered directories. data/log file stores the mapping between URL and numbered file is stored in this log file.



next up previous contents index
Next: 6.10 Troubleshooting Up: 6 The Object Cache Previous: 6.8.7 Summary: object caching



Darren Hardy
Mon Apr 3 15:22:37 MDT 1995