Re: RELEASE in store.log

On Thu, 1 Jul 1999, Morin wrote:

]RELEASE tag in the store.log means that a file has been removed from the
]cache. (SWAPOUT means that a file has been written in the cache, and
]SWAPIN a file has been read from the chache, and has been put in the
]memory). If this is true, then how is it possible for a file to be
]removed (RELEASE) twice, without being written on the cache (SWAPOUT)
]between the two RELEASE?

The store.log should be regarded as a debug file. Makeing sense of the info
in store.log is not as trivial as the FAQ makes one believe (apart from
that part of the FAQ being quite old).

You are omitting the file numbers (or citing a non-squid-2), but those are
important for diagnosing your "problem", e.g. a filenumber of FFFFFFFF
denominates a "memory only" object.

](here's what I've done to see this :
]*929220228.786 SWAPOUT 200 929228983 929220088 -2 text/html
]7890/7890 GET http://canal-fr.afp.com/canal/fr/menu.htm 1384/1384
]*---------------------- here is the problem !!!!!!
]--------------------------------------
]*929244047.181 RELEASE 304 929252803 -2 -2 unknown 0/0
]GET http://canal-fr.afp.com/canal/fr/menu.htm -2/-2

This is an IMS "not modified" answer, which was probably release from
memory...

]*929257426.470 RELEASE 200 929228983 929220088 -2 text/html
]7890/7890 GET http://canal-fr.afp.com/canal/fr/menu.htm -2/-2
]*--------------------------------------------------------------------------------------------
]*929257426.645 SWAPOUT 200 929266183 929263761 -2 text/html
]7897/7897 GET http://canal-fr.afp.com/canal/fr/menu.htm 1017/1017
]*---------------------- here is the problem !!!!!!
]--------------------------------------
]*929277185.302 RELEASE 200 929266183 929263761 -2 text/html
]7897/7897 GET http://canal-fr.afp.com/canal/fr/menu.htm -2/-2
]*929290244.417 RELEASE 500 -2 -2 -2 text/html
]0/433 GET http://canal-fr.afp.com/canal/fr/menu.htm -2/-2
]*929290392.687 RELEASE 400 -2 -2 -2 unknown
]0/1081 GET http://canal-fr.afp.com/canal/fr/menu.htm -2/-2

These are error answers, code 400 and 500 (internal server error),
probably released from memory.

[...]

](The URL used is certainly not the only one in that case)
]Another question, if possible : why isn't there more elapsed time
]between the date of a file removal (RELEASE) and the date when the same
]file is written again (SWAPOUT) in the cache? (see the last two lines in
]the exemple)

Have you looked at the headers, e.g. Expires, Cache-Control, Pragme, etc.?

Le deagh dh�rachd,
Dipl.-Ing. Jens-S. V�ckler (voeckler@rvs.uni-hannover.de)
Institute for Computer Networks and Distributed Systems
University of Hanover, Germany; +49 511 762 4726
Received on Thu Jul 01 1999 - 09:14:10 MDT