Bug#894602: [dpkg] Strange cron error mails from executing /etc/cron.daily/dpkg
On Thu, 2018-04-12 at 18:45:48 +0200, Dirk Heinrichs wrote: > Am 12.04.2018 um 14:16 schrieb Guillem Jover: > > Do you perhaps have something like unattended-ugrades or something > > similar enabled on all those hosts? > > No, I don't. That's one of the packages I uninstall immediately ;-) Then I'm afraid I'm a bit at a loss here. Could you check your dpkg.log files and compare times with when those errors occurred on those hosts, to try to see whether there was some dpkg invoked at the same time? Thanks, Guillem
Bug#894602: [dpkg] Strange cron error mails from executing /etc/cron.daily/dpkg
Am 12.04.2018 um 14:16 schrieb Guillem Jover: > Do you perhaps have something like unattended-ugrades or something > similar enabled on all those hosts? No, I don't. That's one of the packages I uninstall immediately ;-) Bye... Dirk -- Dirk Heinrichs GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de signature.asc Description: OpenPGP digital signature
Bug#894602: [dpkg] Strange cron error mails from executing /etc/cron.daily/dpkg
Hi! On Mon, 2018-04-02 at 08:58:58 +0200, Dirk Heinrichs wrote: > Package: dpkg > Version: 1.18.24 > Severity: normal > since a couple of days, I'm getting strange error mails from cron > daemon with subject > > "Cron test -x /usr/sbin/anacron || ( cd / && run- > parts --report /etc/cron.daily )" > > from some hosts. They're all related to executing /etc/cron.daily/dpkg > but with slightly different content. One host even sends 2(!) mails. > Here's the content: > Host1: > > /etc/cron.daily/dpkg: > cp: cannot create regular file 'dpkg.status': File exists This smells like a race condition, between logrotate and dpkg being called and recreating the file before logrotate does. But I might be wrong. > mv: cannot move './/dpkg.status.5.gz' to './/dpkg.status.6.gz': No such > file or directory > mv: cannot move './/dpkg.status.4.gz' to './/dpkg.status.5.gz': No such > file or directory > mv: cannot move './/dpkg.status.3.gz' to './/dpkg.status.4.gz': No such > file or directory > mv: cannot move './/dpkg.status.2.gz' to './/dpkg.status.3.gz': No such > file or directory > mv: cannot move './/dpkg.status.1.gz' to './/dpkg.status.2.gz': No such > file or directory But I'm not sure why it would fail to move aside the one that I'd expect had been moved before. I'd need to check logrotate's code. […] > run-parts: /etc/cron.daily/logrotate exited with return code 1 > If I execute /etc/cron.daily/dpkg manually, it always finishes without > error. That's to be expected on normal conditions, yes. :) > In case it matters, these hosts are setup as LXC-based OS containers > running on libvirt. But I think I've seen these mails from physical > hosts in the past as well. Do you perhaps have something like unattended-ugrades or something similar enabled on all those hosts? Thanks, Guillem
Bug#894602: [dpkg] Strange cron error mails from executing /etc/cron.daily/dpkg
Package: dpkg Version: 1.18.24 Severity: normal --- Please enter the report below this line. --- Hi, since a couple of days, I'm getting strange error mails from cron daemon with subject "Cron test -x /usr/sbin/anacron || ( cd / && run- parts --report /etc/cron.daily )" from some hosts. They're all related to executing /etc/cron.daily/dpkg but with slightly different content. One host even sends 2(!) mails. Here's the content: Host1: /etc/cron.daily/dpkg: cp: cannot create regular file 'dpkg.status': File exists mv: cannot move './/dpkg.status.5.gz' to './/dpkg.status.6.gz': No such file or directory mv: cannot move './/dpkg.status.4.gz' to './/dpkg.status.5.gz': No such file or directory mv: cannot move './/dpkg.status.3.gz' to './/dpkg.status.4.gz': No such file or directory mv: cannot move './/dpkg.status.2.gz' to './/dpkg.status.3.gz': No such file or directory mv: cannot move './/dpkg.status.1.gz' to './/dpkg.status.2.gz': No such file or directory cp: cannot create regular file 'dpkg.diversions': File exists gzip: .//dpkg.diversions.0: No such file or directory mv: cannot move './/dpkg.diversions.0.gz' to './/dpkg.diversions.1.gz': No such file or directory mv: cannot move 'dpkg.diversions' to './/dpkg.diversions.0': No such file or directory /etc/cron.daily/logrotate: error: error renaming temp state file /var/lib/logrotate/status.tmp run-parts: /etc/cron.daily/logrotate exited with return code 1 Host2: /etc/cron.daily/dpkg: mv: cannot move './/dpkg.status.5.gz' to './/dpkg.status.6.gz': No such file or directory mv: cannot stat './/dpkg.status.4.gz': No such file or directory mv: cannot stat './/dpkg.status.2.gz': No such file or directory gzip: .//dpkg.diversions.0: No such file or directory cp: cannot create regular file 'dpkg.statoverride': File exists Host3 (mail1): /etc/cron.daily/dpkg: mv: cannot move './/dpkg.status.2.gz' to './/dpkg.status.3.gz': No such file or directory cp: cannot create regular file 'dpkg.diversions': File exists gzip: .//dpkg.diversions.0: No such file or directory mv: cannot stat './/dpkg.statoverride.4.gz': No such file or directory mv: cannot stat './/dpkg.statoverride.2.gz': No such file or directory mv: cannot stat './/dpkg.statoverride.1.gz': No such file or directory gzip: .//dpkg.statoverride.0: No such file or directory mv: cannot stat './/dpkg.statoverride.0.gz': No such file or directory Host3 (mail2): /etc/cron.daily/dpkg: cp: cannot create regular file 'dpkg.status': File exists mv: cannot move './/dpkg.status.5.gz' to './/dpkg.status.6.gz': No such file or directory mv: cannot stat './/dpkg.status.4.gz': No such file or directory mv: cannot stat './/dpkg.status.3.gz': No such file or directory mv: cannot move './/dpkg.status.1.gz' to './/dpkg.status.2.gz': No such file or directory gzip: .//dpkg.status.0: No such file or directory mv: cannot stat './/dpkg.status.0.gz': No such file or directory mv: cannot stat 'dpkg.status': No such file or directory mv: cannot stat './/dpkg.diversions.0.gz': No such file or directory mv: cannot stat 'dpkg.diversions': No such file or directory mv: cannot stat './/dpkg.statoverride.5.gz': No such file or directory mv: cannot stat './/dpkg.statoverride.3.gz': No such file or directory /etc/cron.daily/logrotate: error: destination /var/lib/logrotate/status.tmp already exists, renaming to /var/lib/logrotate/status.tmp-2018040206.backup error: error renaming temp state file /var/lib/logrotate/status.tmp run-parts: /etc/cron.daily/logrotate exited with return code 1 If I execute /etc/cron.daily/dpkg manually, it always finishes without error. In case it matters, these hosts are setup as LXC-based OS containers running on libvirt. But I think I've seen these mails from physical hosts in the past as well. --- System information. --- Architecture: Kernel: Linux 4.14.0-0.bpo.3-amd64 Debian Release: 9.4 600 stretch-backports vwakviie2ienjx6t.onion 500 syncthing apt.syncthing.net 500 stable www.deb-multimedia.org 500 stable vwakviie2ienjx6t.onion 500 stable sgvtcaew4bxjd7ln.onion 500 stable repo.saltstack.com 500 stable dl.google.com 500 stable archive.grahamedgecombe.com --- Package information. --- Depends (Version) | Installed ===-+- tar (>= 1.28-1) | 1.29b-1.1 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== apt | 1.4.8 debsig-verify| Bye... Dirk -- Dirk Heinrichs GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de signature.asc Description: This is a digitally signed message part
