[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930446: popularity-contest: unable to submit report, impossible to debugo



On Thu, Jun 20, 2019 at 06:04:23PM +0200, Stefan Fritsch wrote:
> It seems it is run twice, once from /etc/cron.d/popularity-contest and
> once from /etc/cron.daily. And the run from cron.d is at a different
> time on each host and was successful and did not log anything.

Good!

> But the
> second run via run-parts /etc/cron.daily (without --crond) fails because
> it is at the same time on all systems. And that produces log spam.
> 
> # grep daily /etc/crontab
> 25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts
> --report /etc/cron.daily )
> 
> Maybe the successful run should be remembered somehow?

It is remembered by looking at the date of /var/log/popularity-contest.
If it is recent, nothing is done.
Maybe you have a cronjob that remove this file ?
Or a backup program that mess with the timestamp ?

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 


Reply to: