> This indicates a 'mailmanctl stop' command or some other event resulted
> in a SIGTERM being sent to the running mailmanctl. (And are these messages
> from two and a half days later supposed to be related to those above?)
Nope. But that's all I saw in the logs that was in the same week.
>> Mar
> Kurt Werle wrote:
>
>
>> I have twice got the following error:
>> ---
>> Mar 14 22:41:58 2006 mailmanctl(54): The master qrunner lock could not
>> be acquired. It appears as though there is a stale master qrunner lock.
>> Try re-running mailmanctl wi
I have twice got the following error:
---
Mar 14 22:41:58 2006 mailmanctl(54): The master qrunner lock could not be
acquired. It appears as though there is
a stale master qrunner lock. Try re-running mailmanctl with the -s flag.
Mar 14 22:41:58 2006 mailmanctl(54):
Mar 14 22:56:02 2006 mailmanctl
