On Wed, Jan 31, 2018 at 7:47 PM, Chase Pettet <cpettet(a)wikimedia.org> wrote: I don't really know. Is clearly a transient error, given the offending file is now in place. But if I delete the file by hand and re-run the cron script I can't reproduce the issue. This is my guess: somehow the repo info get outdated or invalid. Some additional bits: * the /etc/cron.daily dir contains an apt script that can sleep a random amount of time, and is executed just before this offending cron script: % sudo run-parts --report -v /etc/cron.daily/ run-parts: executing /etc/cron.daily//acct run-parts: executing /etc/cron.daily//apache2 run-parts: executing /etc/cron.daily//apt run-parts: executing /etc/cron.daily//apt-show-versions run-parts: executing /etc/cron.daily//bsdmainutils run-parts: executing /etc/cron.daily//dpkg run-parts: executing /etc/cron.daily//exim4-base run-parts: executing /etc/cron.daily//logrotate run-parts: executing /etc/cron.daily//man-db run-parts: executing /etc/cron.daily//ntp run-parts: executing /etc/cron.daily//passwd run-parts: executing /etc/cron.daily//popularity-contest run-parts: executing /etc/cron.daily//sysstat run-parts: executing /etc/cron.daily//upstart * Why do we even need this cron script? It's included in the apt-show-versions package, but I don't see any benefit of having it. Perhaps we could disable it via puppet. _______________________________________________ Cloud-admin mailing list Cloud-admin(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/cloud-admin