On 6/7/23 21:30, Nelson Strother wrote:
Interestingly if I use
systemctl start mailmanthus far the results are:
- the wall clock duration is shorter than when
mailman startis issued from the command line, and -- either that all of the runners remain present once they are started, -- or I can see in syslog a traceback from each missing runner process starting from .../mailman/.local/bin/runner and ending with "flufl.lock._lockfile.NotLockedError: Already unlocked".I do not yet understand how to make use of these clues, but at least one can see an epitaph from each deceased process.
The NotLockedError is most likely because a lock has been set with a lifetime and its lifetime has passed and some other process has broken the lock before the original process tries to unlock it. This probably has something to do with the long times to do start/restart.
However, the only lock that should be involved is the master lock set by the master watcher, so I don't really understand what might be happening.
What is the full traceback from these errors?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan