On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
El 1/4/23 a las 20:44, Mark Sapiro escribió:
... lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart.
You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start.
I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail.
Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content:
master.lck|www.proteccion-civil.eu|9389|7022761192045613065
Those are the master lock that prevents Mailman core from starting when it is running. They should not be removed unless Mailman core is stopped.
will try deleting the content of var/locks and restarting the server
If you had completely stopped Mailman core and then started it, lmtp runner should have started. What are the complete log messages from mailman.log following the start?
What does mailman conf -s runner.lmtp show?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan