- Package:
- popularity-contest
- Source:
- popularity-contest
- Submitter:
- Martin-Éric Racine
- Date:
- 2025-02-27 11:03:02 UTC
- 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.
Hi, While you still have the journal log, can you check for a race condition ? # journalctl | grep popul | grep service (it looks like #1052053) Le ven. 22 sept. 2023 à 10:18, Martin-Éric Racine <perkelix@iki.fi> a écrit :
Hello Martin-Éric, Does it happen every time or it is just this time ? Do you have files /var/log/popularity-contest.* ? Sorry for the trouble! Cheers,
It gave me this: Sep 22 10:41:55 u1400 systemd[1]: Starting cron-daily-popularity-contest.service - [Cron] /etc/cron.daily/popularity-contest... Sep 22 10:43:21 u1400 systemd[1]: cron-daily-popularity-contest.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Sep 22 10:43:21 u1400 systemd[1]: cron-daily-popularity-contest.service: Failed with result 'exit-code'. Sep 22 10:43:21 u1400 systemd[1]: Failed to start cron-daily-popularity-contest.service - [Cron] /etc/cron.daily/popularity-contest. Sep 22 10:43:21 u1400 systemd[1]: cron-daily-popularity-contest.service: Triggering OnFailure= dependencies. Sep 22 10:43:21 u1400 systemd[1]: cron-daily-popularity-contest.service: Consumed 2.512s CPU time. Sep 22 10:43:21 u1400 systemd[1]: Starting cron-mail@cron-daily-popularity-contest.service:Failure.service - systemd-cron job mail — cron-daily-popularity-contest.service:Failure... Sep 22 10:43:36 u1400 systemd[1]: cron-mail@cron-daily-popularity-contest.service:Failure.service: Deactivated successfully. Sep 22 10:43:36 u1400 systemd[1]: Finished cron-mail@cron-daily-popularity-contest.service:Failure.service - systemd-cron job mail — cron-daily-popularity-contest.service:Failure.
This looks like something else.
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,