Today it was just the one maint_ log, even though this morning I had
manually run the expire-caller with the path check and checksum options
in effect, saw some 'Bad' files, tagged them and deleted them, then also
immediately deleted debs scheduled for removal. Everything looked nice
and clean after I finished, then another error. I don't have the logs
for error today because a couple of minutes after I noticed the error I
decided to just re-run the cron job and it ran cleanly then deleted old
maint_ logs at the end of the run.
I might monkey around with the cron script to call
expire-caller.pl a second time if it errors on the first run.
I know that's a hack but it's really annoying to see the same
garbage every day. It seems like the contrib/Packages.bz2 and
security InRelease files are the most frequent triggers for the error
but I can't tell what the problem is when the cron job is run, it only
shows up after the fact. If I run the expire-caller from the web
interface with the path and checksum checkers it gives more information
but having to do that manually every time there is an error, _and_ then
run the cron job after to clear out old logs is no good.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
