Invocations of "/etc/init.d/mailman start" spawns multiple instances

Bug #651182 reported by Andrea Gelmini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Debian
New
Unknown
mailman (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: mailman

root@vaio:/tmp# ps -u list
  PID TTY TIME CMD
 8490 ? 00:00:00 mailmanctl
 8491 ? 00:00:00 python
 8492 ? 00:00:00 python
 8493 ? 00:00:00 python
 8494 ? 00:00:00 python
 8495 ? 00:00:00 python
 8496 ? 00:00:00 python
 8497 ? 00:00:00 python
 8498 ? 00:00:00 python
root@vaio:/tmp# /etc/init.d/mailman start
 * Starting Mailman master qrunner mailmanctl [ OK ]
root@vaio:/tmp# ps -u list
  PID TTY TIME CMD
 8490 ? 00:00:00 mailmanctl
 8491 ? 00:00:00 python
 8492 ? 00:00:00 python
 8493 ? 00:00:00 python
 8494 ? 00:00:00 python
 8495 ? 00:00:00 python
 8496 ? 00:00:00 python
 8497 ? 00:00:00 python
 8498 ? 00:00:00 python
 8516 ? 00:00:00 mailmanctl
 8518 ? 00:00:00 python
 8519 ? 00:00:00 python
 8525 ? 00:00:00 python
 8526 ? 00:00:00 python
 8527 ? 00:00:00 python
 8528 ? 00:00:00 python
 8529 ? 00:00:00 python
 8530 ? 00:00:00 python
root@vaio:/tmp# /etc/init.d/mailman stop
 * Stopping Mailman master qrunner mailmanctl [ OK ]
root@vaio:/tmp# ps -u list
  PID TTY TIME CMD
 8490 ? 00:00:00 mailmanctl
 8491 ? 00:00:00 python
 8492 ? 00:00:00 python
 8493 ? 00:00:00 python
 8494 ? 00:00:00 python
 8495 ? 00:00:00 python
 8496 ? 00:00:00 python
 8497 ? 00:00:00 python
 8498 ? 00:00:00 python
root@vaio:/tmp# export LANG='C'
root@vaio:/tmp# /etc/init.d/mailman stop
 * Stopping Mailman master qrunner mailmanctl PID unreadable in: /var/run/mailman/mailman.pid
[Errno 2] No such file or directory: '/var/run/mailman/mailman.pid'
Is qrunner even running?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mailman 1:2.1.13-1
Uname: Linux 2.6.36-rc5g+ i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Sep 29 16:31:46 2010
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: mailman

Revision history for this message
Andrea Gelmini (gelma) wrote :
James Page (james-page)
Changed in mailman (Ubuntu):
assignee: nobody → James Page (james-page)
Revision history for this message
James Page (james-page) wrote :

Bug reproduced on up-to-date Lucid 10.04.1 server image.

Confirmed that the mailman startup script does not check current status before starting mailman, which in turn does not inhibit multiple execution on the same machine. This results in multiple instances of mailman executing at the same time which are not stopped in full by the startup/shutdown script.

Proposed importance: Low
Proposed status: Confirmed

Revision history for this message
James Page (james-page) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in mailman (Ubuntu):
assignee: James Page (james-page) → nobody
status: New → Confirmed
James Page (james-page)
Changed in mailman (Ubuntu):
status: Confirmed → New
James Page (james-page)
Changed in mailman (Ubuntu):
status: New → Confirmed
Revision history for this message
C de-Avillez (hggdh2) wrote :

Marking Confirmed/Low; todo: add upstream bug link

Changed in mailman (Ubuntu):
importance: Undecided → Low
Revision history for this message
Andrea Gelmini (gelma) wrote :

Hi all,
   and thanks a lot for your work.
   Yesterday I filled same bug for Debian (same evidence on Testing):
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598509

 Ciao,
Andrea

Revision history for this message
C de-Avillez (hggdh2) wrote :

Marking Triaged, we already have the upstream bug courtesy of Andrea.

Changed in mailman (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Andrea Gelmini (gelma) wrote :

Hi all,
   and thanks a lot for your attention.
   The simple patch in attachment fix the problem, so it means
   the bug is inside
       /usr/lib/mailman/bin/mailmanctl
   not in init script
       /etc/init.d/mailman

   I suppose there's a wrong implementation of flag '-s':

       -s/--stale-lock-cleanup
        If mailmanctl finds an existing master lock, it will normally exit
        with an error message. With this option, mailmanctl will perform an
        extra level of checking. If a process matching the host/pid described
        in the lock file is running, mailmanctl will still exit, but if no
        matching process is found, mailmanctl will remove the apparently stale
        lock and make another attempt to claim the master lock.

Thanks a lot for your work,
Andrea

Changed in debian:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.