Hello!
today, we received support requests from Ariadne and Oxfam. Both reported that mails sent from KARL did not arrive to the recipients (in this case: community invitations and blog post notifications)
We investigated and found the following in the /srv/multikarl/production/current/var/log/mailout.log:
2012-03-29 02:30:15,746 WARNING karlserve.scripts.main: mailout already running with pid 3246
2012-03-29 02:30:15,747 WARNING karlserve.scripts.main: Exiting.
It turned out that for some reason the lock file /srv/multikar/production/current/var/lock/mailout.pid had not been touched since quite a while and that meanwhile, there was a different process running with this PID.
Removing the PID file helped and mails that still were in the queue have been sent successfully.
To discover problems like these more quickly in the future, we wondered if it would be possible to introduce some kind of a mailout check in analogy to the one that checks for the correct mailin behaviour (mailin-trace).
Best regards,
Alex
Sounds like a good idea.