Your message dated Fri, 23 Jun 2023 16:39:24 +0200 with message-id <CADsTwjKu2jA+MLvniV8-N-ZYCBC=1ssxbgmg_lwyqj5qqgc...@mail.gmail.com> and subject line Re: systemd-cron: timed job fails has caused the Debian Bug report #1018843, regarding systemd-cron: timed job fails to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd-cron Version: 1.15.19-1 Severity: normal Hi Maintainer, I'm unsure of why this started, or how. I'm getting these messages in my daily log reports: × cron-tmick-tmick-0.service - [Cron] "59 23 * * * /usr/bin/clamscan --exclude- dir=/home/tmick/.clamtk/viruses --exclude-dir=smb4k --exclude- dir=/run/user/tmick/gvfs --exclude-dir=/home/tmick/.gvfs --exclude- dir=.thunderbird --exclude-dir=.mozilla-thunderbird --exclude-dir=.evolution --exclude-dir=Mail --exclude-dir=kmail -i --detect-pua -r /home/tmick --log="$HOME/.clamtk/history/$(date +\%b-\%d-\%Y).log" 2>/dev/null # clamtk- scan" Loaded: loaded (/var/spool/cron/crontabs/tmick; generated) Active: failed (Result: exit-code) since Wed 2022-08-31 05:00:46 CDT; 1s ago TriggeredBy: ● cron-tmick-tmick-0.timer Docs: man:systemd-crontab-generator(8) Process: 4051496 ExecStart=/bin/sh /run/systemd/generator/cron-tmick- tmick-0.sh (code=exited, status=1/FAILURE) Main PID: 4051496 (code=exited, status=1/FAILURE) CPU: 4h 9min 43.153s Aug 31 05:00:46 DebianTim sh[4051498]: Data scanned: 54544.98 MB Aug 31 05:00:46 DebianTim sh[4051498]: Data read: 231444.55 MB (ratio 0.24:1) Aug 31 05:00:46 DebianTim sh[4051498]: Time: 18077.934 sec (301 m 17 s) Aug 31 05:00:46 DebianTim sh[4051498]: Start Date: 2022:08:30 23:59:27 Aug 31 05:00:46 DebianTim sh[4051498]: End Date: 2022:08:31 05:00:45 Aug 31 05:00:46 DebianTim systemd[1]: cron-tmick-tmick-0.service: Main process exited, code=exited, status=1/FAILURE Aug 31 05:00:46 DebianTim systemd[1]: cron-tmick-tmick-0.service: Failed with result 'exit-code'. Aug 31 05:00:46 DebianTim systemd[1]: Failed to start [Cron] "59 23 * * * /usr/bin/clamscan --exclude-dir=/home/tmick/.clamtk/viruses --exclude-dir=smb4k --exclude-dir=/run/user/tmick/gvfs --exclude-dir=/home/tmick/.gvfs --exclude- dir=.thunderbird --exclude-dir=.mozilla-thunderbird --exclude-dir=.evolution --exclude-dir=Mail --exclude-dir=kmail -i --detect-pua -r /home/tmick --log="$HOME/.clamtk/history/$(date +\%b-\%d-\%Y).log" 2>/dev/null # clamtk- scan". Aug 31 05:00:46 DebianTim systemd[1]: cron-tmick-tmick-0.service: Triggering OnFailure= dependencies. Aug 31 05:00:46 DebianTim systemd[1]: cron-tmick-tmick-0.service: Consumed 4h 9min 43.153s CPU time. So I'm unsure if it failed and retried and succeeded or what. I tried looking in the man page to see if I could find where or how to go to fix this but it's not clear where the timed services are/ how they get configured. So how do I shut this up?? -- Package-specific info: -- output of systemd-delta -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd-cron depends on: ii cron-daemon-common 3.0pl1-149 ii libc6 2.34-4 ii python3 3.10.6-1 ii systemd [systemd-sysusers] 251.3-1 ii systemd-sysv 251.3-1 Versions of packages systemd-cron recommends: ii exim4-daemon-light [mail-transport-agent] 4.96-3 systemd-cron suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi, I see myself systemd-cron as a legacy adaptor for old crontabs shipped in old Debian packages. For you own personal use, I'd rather suggest to use a native .service + .timer where you'll get full control. I can not give support for your system, I don't use ClamAV. Greetings,
--- End Message ---
