Debian Bug report logs - #598509
Invocations of "/etc/init.d/mailman start" spawns multiple instances

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Andrea Gelmini <[email protected]>

To: Debian Bug Tracking System <[email protected]>

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

Date: Wed, 29 Sep 2010 17:24:48 +0200

Package: mailman
Version: 1:2.1.13-4
Severity: normal


deb:/tmp# /etc/init.d/mailman start
Starting Mailman master qrunner: mailmanctl.
deb:/tmp# ps -u list
  PID TTY          TIME CMD
 2102 ?        00:00:00 mailmanctl
 2103 ?        00:00:00 python
 2104 ?        00:00:00 python
 2105 ?        00:00:00 python
 2106 ?        00:00:00 python
 2107 ?        00:00:00 python
 2108 ?        00:00:00 python
 2109 ?        00:00:00 python
 2110 ?        00:00:00 python
deb:/tmp# /etc/init.d/mailman start
Starting Mailman master qrunner: mailmanctl.
deb:/tmp# ps -u list
  PID TTY          TIME CMD
 2102 ?        00:00:00 mailmanctl
 2103 ?        00:00:00 python
 2104 ?        00:00:00 python
 2105 ?        00:00:00 python
 2106 ?        00:00:00 python
 2107 ?        00:00:00 python
 2108 ?        00:00:00 python
 2109 ?        00:00:00 python
 2110 ?        00:00:00 python
 2122 ?        00:00:00 mailmanctl
 2128 ?        00:00:00 python
 2129 ?        00:00:00 python
 2130 ?        00:00:00 python
 2131 ?        00:00:00 python
 2132 ?        00:00:00 python
 2133 ?        00:00:00 python
 2134 ?        00:00:00 python
 2135 ?        00:00:00 python
deb:/tmp# /etc/init.d/mailman start
Starting Mailman master qrunner: mailmanctl.
deb:/tmp# ps -u list
  PID TTY          TIME CMD
 2102 ?        00:00:00 mailmanctl
 2103 ?        00:00:00 python
 2104 ?        00:00:00 python
 2105 ?        00:00:00 python
 2106 ?        00:00:00 python
 2107 ?        00:00:00 python
 2108 ?        00:00:00 python
 2109 ?        00:00:00 python
 2110 ?        00:00:00 python
 2122 ?        00:00:00 mailmanctl
 2128 ?        00:00:00 python
 2129 ?        00:00:00 python
 2130 ?        00:00:00 python
 2131 ?        00:00:00 python
 2132 ?        00:00:00 python
 2133 ?        00:00:00 python
 2134 ?        00:00:00 python
 2135 ?        00:00:00 python
 2142 ?        00:00:00 mailmanctl
 2148 ?        00:00:00 python
 2149 ?        00:00:00 python
 2150 ?        00:00:00 python
 2151 ?        00:00:00 python
 2152 ?        00:00:00 python
 2153 ?        00:00:00 python
 2154 ?        00:00:00 python
 2155 ?        00:00:00 python
deb:/tmp# /etc/init.d/mailman stop 
Stopping Mailman master qrunner: mailmanctl.
deb:/tmp# /etc/init.d/mailman stop
Stopping Mailman master qrunner: mailmanctlPID unreadable in: /var/run/mailman/mailman.pid
[Errno 2] No such file or directory: '/var/run/mailman/mailman.pid'
Is qrunner even running?
..
deb:/tmp# ps -u list
  PID TTY          TIME CMD
 2102 ?        00:00:00 mailmanctl
 2103 ?        00:00:00 python
 2104 ?        00:00:00 python
 2105 ?        00:00:00 python
 2106 ?        00:00:00 python
 2107 ?        00:00:00 python
 2108 ?        00:00:00 python
 2109 ?        00:00:00 python
 2110 ?        00:00:00 python
 2122 ?        00:00:00 mailmanctl
 2128 ?        00:00:00 python
 2129 ?        00:00:00 python
 2130 ?        00:00:00 python
 2131 ?        00:00:00 python
 2132 ?        00:00:00 python
 2133 ?        00:00:00 python
 2134 ?        00:00:00 python
 2135 ?        00:00:00 python

I reported this bug also in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/651182

Thanks a lot,
Andrea

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages mailman depends on:
ii  apache2                      2.2.16-2    Apache HTTP Server metapackage
ii  apache2-mpm-worker [httpd]   2.2.16-2    Apache HTTP Server - high speed th
ii  cron                         3.0pl1-114  process scheduling daemon
ii  debconf [debconf-2.0]        1.5.35      Debian configuration management sy
ii  exim4-daemon-light [mail-tra 4.72-1      lightweight Exim MTA (v4) daemon
ii  libc6                        2.11.2-6    Embedded GNU C Library: Shared lib
ii  logrotate                    3.7.8-6     Log rotation utility
ii  lsb-base                     3.2-23.1    Linux Standard Base 3.2 init scrip
ii  pwgen                        2.06-1+b1   Automatic Password generation
ii  python                       2.6.5-13    interactive high-level object-orie
ii  python-support               1.0.10      automated rebuilding support for P
ii  ucf                          3.0025+nmu1 Update Configuration File: preserv

mailman recommends no packages.

Versions of packages mailman suggests:
pn  listadmin                     <none>     (no description available)
pn  lynx                          <none>     (no description available)
pn  spamassassin                  <none>     (no description available)

-- debconf information:
  mailman/queue_files_present: abort installation
* mailman/default_server_language: en
  mailman/gate_news: false
* mailman/site_languages: en
* mailman/used_languages:
* mailman/create_site_list:

Message #10 received at [email protected] (full text, mbox, reply):

From: Andrea Gelmini <[email protected]>

To: [email protected]

Subject: Fix proposal

Date: Sat, 2 Oct 2010 20:27:10 +0200

[Message part 1 (text/plain, inline)]

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

n.b.: same fix on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/651182

[fix.patch (text/x-diff, attachment)]

Message #15 received at [email protected] (full text, mbox, reply):

From: Ralf Jung <[email protected]>

To: [email protected]

Cc: [email protected]

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

Date: Wed, 07 Aug 2013 13:02:15 +0200

Dear Maintainer,

is there any news on this? This bug is three years old, and Wheezy still
ships with this issue.

Kind regards,
Ralf

Message #20 received at [email protected] (full text, mbox, reply):

From: Geoff Crompton <[email protected]>

To: [email protected]

Subject: possibly fixed upstream

Date: Mon, 18 Jan 2016 15:59:29 +1100

[Message part 1 (text/plain, inline)]

I think this bug was reported upstream, https://bugs.launchpad.net/mailman/+bug/1189558 <https://bugs.launchpad.net/mailman/+bug/1189558>. If that upstream bug is relevant to this bug report, then it was fixed in mailman 2.1.16, and this bug could probably be closed. I’ve tested the wheezy backport 2.1.18 packages, and they fixed this problem for me.

—
Geoff Crompton, Senior ICT Infrastructure Administrator
T: +61 (0)3 9348 7138
Trinity College | University of Melbourne | Royal Parade, Parkville | Victoria 3052, Australia
www.trinity.unimelb.edu.au <http://www.trinity.unimelb.edu.au/>

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.