
On 2/12/25 09:24, Christian via Mailman-users wrote:
Running Debian 4.19.316-1 Python 3.7.3
I am unable to start mailman core
mailman@lists:~$ /opt/mailman/mm/bin/mailman start Usage: mailman start [OPTIONS] Try 'mailman start -h' for help.
Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force mailman@lists:~$
I try using --force and it did not work. So how do I start it?
In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are:
master.lck
master.lck|<host_name>|<pid>|<random_integer>
First verify that pid is not running or if it is, that it's not
Mailman's master
process. Then remove all the files from the
var/locks/ directory and Mailman should start.
Bottom line: I would like for Mailman core to start when I reboot the server. How can this be achieved please?
See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan