On Fri, 22 Oct 2004, Mark Sapiro wrote:
> [EMAIL PROTECTED] wrote:
> >
> >On Slackware 9.1 (kernel 2.4.22), Mailman 2.1.5, Python 2.3.4, Sendmail 8.12.10:
> >
> >ps shows -
> >
> > PID TTY STAT TIME COMMAND
> >26185 ? S 0:00 sendmail: accepting connections
> >26187 ? S 0:00 sendmail: Queue [EMAIL PROTECTED]:25:00 for
> >/var/spool/client
> > 1359 ? S 0:00 /usr/bin/python /usr/local/mailman/bin/qrunner
> > --runner=NewsRunner:0:1 -s
> > 1360 ? S 0:00 /usr/bin/python /usr/local/mailman/bin/qrunner
> > --runner=BounceRunner:0:1 -s
> > 1361 ? S 0:00 /usr/bin/python /usr/local/mailman/bin/qrunner
> > --runner=RetryRunner:0:1 -s
> > 1362 ? S 0:00 /usr/bin/python /usr/local/mailman/bin/qrunner
> > --runner=CommandRunner:0:1 -s
> >
> >The qrunner daemon was fired up by the mailman script copied to /etc/rc.d and
> >called in rc.local at boot time.
> >
> >When I post to a test list mail sits forever in qfiles/in
> >The entry is owned by daemon.mail (mailman was conf'd with --mail-gid=daemon)
>
>
> Probably because the incoming qrunner is not running. Why it isn't
> started (or quits) I don't know.
>
> Your mailman script should be running "mailmanctl -s -q start".
Hey Mark, thanks for the reply. Yeah I figured that the missing qrunners were
the problem but there was no log entry that was revealing. Then I read in the
mailmanctl script that restart doesn't kill the parent ps, just the qrunners.
So I manually stopped and started and that did it. We'll see what happens on
the next boot (last one before yesterday was 72 days ago so I'll have to write
a note to myself).
Thanks again,
Tom
> On my installation "ps -Afw|grep python" shows
>
> 101 1518 1 0 Sep26 ? 00:00:00 /usr/bin/python2.3
> /www/grizz/mailman/bin/mailmanctl -s -q start
> 101 1519 1518 0 Sep26 ? 00:05:32 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
> 101 1520 1518 0 Sep26 ? 00:03:37 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
> 101 1521 1518 0 Sep26 ? 00:03:34 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
> 101 1522 1518 0 Sep26 ? 00:03:52 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
> 101 1523 1518 0 Sep26 ? 00:03:27 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
> 101 1524 1518 0 Sep26 ? 00:04:32 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
> 101 1526 1518 0 Sep26 ? 00:00:12 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
> 101 1527 1518 0 Sep26 ? 00:00:00 /usr/bin/python2.3
> /www/grizz/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
> gpc 17405 16739 0 09:18 pts/2 00:00:00 grep python
>
>
> >The mail will sit there until I run (as mailman OR root): qrunner -r All
> >
> >Where have I veered off course?!!
> >
>
> Figure out what is happening to the missing stuff...
>
> The mailman logs may help.
>
> --
> Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
>
-----------------------------------------------------------------------
Thomas Good e-mail: [EMAIL PROTECTED]
Programmer/Analyst phone: (+1) 718.818.5528
Residential Services fax: (+1) 718.818.5056
Behavioral Health Services, SVCMC-NY mobile: (+1) 347.524.5631
// When you're untroubled by doubt, when your orthodoxy is full up, it
// resists all irony or interruption, all modification or reflection.
-- Bill Ayers
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
