Mailman Masterrunner keeps locks after force

Bug #925559 reported by benste
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
High
Unassigned

Bug Description

I've existed Mailman just closing my terminal which didn't stop it properly.

Since a8 I'm getting a message to use --force to start it which doesn't delete the locks directory hence doesn't start it.

benste@benste-vpc-sb1c5e:~/Projects/Mailman/mailman-3.0.0a8$ bin/mailman start --force
usage: mailman [-h] [-v] [-C CONFIG]

               {help,aliases,create,import21,info,inject,lists,members,qfile,remove,reopen,restart,start,status,stop,unshunt,version,withlist}
               ...
mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force.

Deleting all files in ./locks enables me to start it again.

Barry Warsaw (barry)
tags: added: mailman3
Barry Warsaw (barry)
Changed in mailman:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Barry Warsaw (barry) wrote :

Hi Benste,

I think this is user error. `bin/mailman start` is just a little front-end that forks and execs the actual master script. This runs in the background and detaches itself from the controlling terminal, so exiting the terminal is not meant to stop the master, or any of its own subprocesses. I think the locks aren't getting deleted because everything's still running.

You should not use --force in this case. Only use --force when you know the master is no longer running. Use `bin/mailman status` to find that out. In your case, just open up a new terminal and run `bin/mailman stop` and everything should work properly.

Changed in mailman:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers