Am 20.06.19 um 13:25 schrieb Bill Allombert: >> When submission fails, popcon-upload dies with a timeout. There should >> probably be a randomized sleep to distribute the server load better. I >> think there could be a lot more popcon submissions if this is done. > > What is the time in /etc/cron.d/popularity-contest ? > (something like 33 5 * * *) > > Does it work better if you change it to some other time ? > What cron ae you using
# cat /etc/cron.d/popularity-contest SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 41 4 * * * root test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond # dpkg -l *cron* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================= un anacron <none> <none> (no description available) ii cron 3.0pl1-133 amd64 process scheduling daemon un cron-daemon <none> <none> (no description available) 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. 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?
