On Fri, Sep 22, 2023 at 11:14:52AM +0300, Martin-Éric Racine wrote: > Package: popularity-contest > Version: 1.77 > Severity: normal > > × cron-daily-popularity-contest.service - [Cron] > /etc/cron.daily/popularity-contest > Loaded: loaded (/etc/cron.daily/popularity-contest; generated) > Active: failed (Result: exit-code) since Fri 2023-09-22 10:43:21 EEST; > 228ms ago > TriggeredBy: ● cron-daily-popularity-contest.timer > Docs: man:systemd-crontab-generator(8) > Process: 631 ExecStart=/etc/cron.daily/popularity-contest (code=exited, > status=2) > Main PID: 631 (code=exited, status=2) > CPU: 2.512s > 2023-09-22T10:41:55+0300 u1400 systemd[1]: Starting > cron-daily-popularity-contest.service - [Cron] > /etc/cron.daily/popularity-contest... > 2023-09-22T10:43:21+0300 u1400 popularity-contest[1690]: gpg: can't open > '/var/log/popularity-contest.631': Tiedostoa tai hakemistoa ei ole > 2023-09-22T10:43:21+0300 u1400 popularity-contest[1690]: gpg: > /var/log/popularity-contest.631: encryption failed: Tiedostoa tai hakemistoa > ei ole > 2023-09-22T10:43:21+0300 u1400 systemd[1]: > cron-daily-popularity-contest.service: Main process exited, code=exited, > status=2/INVALIDARGUMENT > 2023-09-22T10:43:21+0300 u1400 systemd[1]: > cron-daily-popularity-contest.service: Failed with result 'exit-code'. > 2023-09-22T10:43:21+0300 u1400 systemd[1]: Failed to start > cron-daily-popularity-contest.service - [Cron] > /etc/cron.daily/popularity-contest. > 2023-09-22T10:43:21+0300 u1400 systemd[1]: > cron-daily-popularity-contest.service: Triggering OnFailure= dependencies. > 2023-09-22T10:43:21+0300 u1400 systemd[1]: > cron-daily-popularity-contest.service: Consumed 2.512s CPU time.
Hello Martin-Éric, Did you find you what happened ? Did it happen again ? Was /var/log/ full ? Are there two containers instance sharing the same /var/log by mistake. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
