Mailman startup script missing --force option.

Bug #869317 reported by Stephen A. Goss
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Medium
Barry Warsaw

Bug Description

I rebooted the VM that mailman was running on, when I tried to start mailman up after the reboot, i got this output:

    $ mailman -C /etc/mailman.cfg start
    usage: mailman [-h] [-v] [-C CONFIG]
    {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases}
                   ...
    mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force.

Running with the --force option didn't work:

    $ mailman --force -C /etc/mailman.cfg start
    usage: mailman [-h] [-v] [-C CONFIG]

    {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases}
                   ...
    mailman: error: unrecognized arguments: --force

Revision history for this message
Stephen A. Goss (postfuturist) wrote :

OK, the option is not missing, I was using it wrong. However, it still doesn't do anything!

    $ mailman -C /etc/mailman.cfg start --force
    usage: mailman [-h] [-v] [-C CONFIG]
                        {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases}
               ...
    mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force.

Revision history for this message
Stephen A. Goss (postfuturist) wrote :

I found the acquire_lock method and it seems to honor the force option, so the attached patch has allowed me to get past this stale lock situation.

Barry Warsaw (barry)
Changed in mailman:
milestone: none → 3.0.0b1
importance: Undecided → Medium
assignee: nobody → Barry Warsaw (barry)
status: New → In Progress
Revision history for this message
Stephen A. Goss (postfuturist) wrote :

The patch I uploaded doesn't really fix the problem. With that patch, if there is a stale lock file, it raises an AttributeError, then if you run with --force, you get a different error, and then if you try again without the --force option it starts up normally :/

Revision history for this message
Barry Warsaw (barry) wrote : Re: [Bug 869317] Re: Mailman startup script missing --force option.

On Oct 14, 2011, at 06:21 PM, Stephen A. Goss wrote:

>The patch I uploaded doesn't really fix the problem. With that patch,
>if there is a stale lock file, it raises an AttributeError, then if you
>run with --force, you get a different error, and then if you try again
>without the --force option it starts up normally :/

I think I have a fix in my local copy, but I'm currently hung up on one
particularly nasty test failure.

Barry Warsaw (barry)
Changed in mailman:
status: In Progress → Fix Committed
Barry Warsaw (barry)
Changed in mailman:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers