PMG sends out double quarantine notifications

L

Lazarus

Active Member
Apr 26, 2019
22
2
43
125
I ran out of disk on PMG some time ago, and after clearing that and rebooting, PMG sends out double quarantine notifications every day. Once at midnight and once at 3am. Really strange behavior and I don't know where to start looking. Any ideas?
 
It's managed by systemd.
Code: 
~# systemctl list-timers
NEXT                        LEFT          LAST                        PASSED       UNIT                         ACTIVATES
Thu 2022-03-24 09:00:00 GMT 32min left    Thu 2022-03-24 08:00:22 GMT 27min ago    pmg-hourly.timer             pmg-hourly.service
Thu 2022-03-24 10:08:29 GMT 1h 40min left Wed 2022-03-23 10:08:29 GMT 22h ago      systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv>
Thu 2022-03-24 17:41:17 GMT 9h left       Wed 2022-03-23 22:25:22 GMT 10h ago      apt-daily.timer              apt-daily.service
Fri 2022-03-25 00:00:00 GMT 15h left      Thu 2022-03-24 00:00:22 GMT 8h ago       logrotate.timer              logrotate.service
Fri 2022-03-25 00:01:00 GMT 15h left      Thu 2022-03-24 00:01:09 GMT 8h ago       pmgreport.timer              pmgreport.service
Fri 2022-03-25 00:05:00 GMT 15h left      Thu 2022-03-24 00:05:22 GMT 8h ago       pmgspamreport.timer          pmgspamreport.service
Fri 2022-03-25 02:32:00 GMT 18h left      Thu 2022-03-24 04:11:19 GMT 4h 16min ago pmg-daily.timer              pmg-daily.service
Fri 2022-03-25 06:53:48 GMT 22h left      Thu 2022-03-24 06:42:52 GMT 1h 44min ago apt-daily-upgrade.timer      apt-daily-upgrade.service
Sun 2022-03-27 03:10:20 BST 2 days left   Sun 2022-03-20 03:10:15 GMT 4 days ago   e2scrub_all.timer            e2scrub_all.service
 
  • Like
Reactions: Stoiko Ivanov
Code: 
NEXT                         LEFT          LAST                         PASSED             UNIT                         ACTIVATES
Sun 2022-04-10 12:00:00 CEST 4min 12s left Sun 2022-04-10 11:00:08 CEST 55min ago          pmg-hourly.timer             pmg-hourly.service
Sun 2022-04-10 16:09:02 CEST 4h 13min left Sat 2022-03-26 02:00:01 CET  2 weeks 1 days ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Mon 2022-04-11 00:00:00 CEST 12h left      Sun 2022-04-10 03:00:01 CEST 8h ago             logrotate.timer              logrotate.service
Mon 2022-04-11 00:01:00 CEST 12h left      Sun 2022-04-10 03:00:01 CEST 8h ago             pmgreport.timer              pmgreport.service
Mon 2022-04-11 00:05:00 CEST 12h left      Sun 2022-04-10 03:00:01 CEST 8h ago             pmgspamreport.timer          pmgspamreport.service
Mon 2022-04-11 00:16:55 CEST 12h left      Sun 2022-04-10 07:43:06 CEST 4h 12min ago       apt-daily.timer              apt-daily.service
Mon 2022-04-11 04:12:22 CEST 16h left      Sun 2022-04-10 03:00:01 CEST 8h ago             pmg-daily.timer              pmg-daily.service
Mon 2022-04-11 06:53:12 CEST 18h left      Sun 2022-04-10 06:17:08 CEST 5h 38min ago       apt-daily-upgrade.timer      apt-daily-upgrade.service
Sun 2022-04-17 03:10:32 CEST 6 days left   Sun 2022-04-10 03:11:08 CEST 8h ago             e2scrub_all.timer            e2scrub_all.service

9 timers listed.
Pass --all to see loaded but inactive timers, too.

The 03:00 timer looks like it could be the one. But why is it also firing at midnight?

Edit:
Found this in /var/log/daemon.log:
Code: 
Apr 10 00:05:08 mailgw systemd[1]: Starting Send Daily Spam Report Mails...
Apr 10 03:00:02 mailgw systemd[1]: Starting Send Daily Spam Report Mails...
So it's definitely systemd triggering when we don't want it to... or so I interpret it.
 
Last edited:
A long long time later, I got to the bottom of this. Figured I’d add some closure to the thread.

A completely different batch job on the machine changed the clock (incorrect use of ’date’ command), which caused the trigger to run twice. However the clock was adjusted back again, so it never looked off on the machine. Fixed the batch and this behavior disappeared with it. Hillarious to have that run for years…
 
You must log in or register to reply here.
Top Bottom