Logs older than 1 hour are Orphans
GoogleCodeExporter opened this issue · 5 comments
GoogleCodeExporter commented
Logs past an hour systematically become orphan, I've the following warning :
"There are 47 logs in cache dir, but there are 15 in database, which is
something weird :/"
I'm running the latest svn version.
Original issue reported on code.google.com by zenmas...@ifzenelse.net on 24 May 2012 at 2:22
GoogleCodeExporter commented
Well, it's not related to logs time as I thought, today I've got quite few logs
between 3pm and 11pm, and now have the following warning :
"There are 49 logs in cache dir, but there are 20 in database, which is
something weird :/"
We'll see how it goes with latest svn, I'll keep you informed, please ask me if
I can provide any other usefull info related to this warning.
Original comment by zenmas...@ifzenelse.net on 24 May 2012 at 9:12
GoogleCodeExporter commented
It seems like random logs become orphan, I can't see why. Any idea?
Original comment by Didier.B37 on 25 May 2012 at 4:43
GoogleCodeExporter commented
Typically, "if there are 49 logs in cache dir, but there are 20 in database"
means that only 20 users were tracked. Could be that a page is being cached
twice? I don't know because I cannot reproduce the error in my PC.
Please provide platform (OS) and browser (name, version) so that I can
investigate further.
Original comment by luis.lei...@gmail.com on 25 May 2012 at 7:29
GoogleCodeExporter commented
I don't really know which specifics clients become orphans, but they usually
were tracked properly at first.
For exemple :
"There are 4 cached pages that are no longer referenced on smt2_records table,
so it is safe to delete them."
When/why does this happen ?
Original comment by zenmas...@ifzenelse.net on 25 May 2012 at 9:43
GoogleCodeExporter commented
That means that some logs (>= 4) are pointing to 4 deleted cached pages.
Original comment by luis.lei...@gmail.com on 17 Oct 2012 at 5:56
- Changed state: Done