[ mailman-Bugs-670535 ] qrunner stops for no apparent reason

SourceForge.net noreply at sourceforge.net
Fri Mar 21 16:54:27 EST 2003


Bugs item #670535, was opened at 2003-01-19 04:04
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 8
Submitted By: David Gibbs (midrangeman)
Assigned to: Nobody/Anonymous (nobody)
Summary: qrunner stops for no apparent reason

Initial Comment:
About once every day or so, qrunner will stop for no 
apparent reason.

The qrunner log file has the following ...

Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner 
caught SIGTERM.  Stopping.
Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner 
exiting.
Jan 18 14:29:09 2003 (3441) BounceRunner qrunner 
caught SIGTERM.  Stopping.
Jan 18 14:29:09 2003 (3441) BounceRunner qrunner 
exiting.
Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner 
caught SIGTERM.  Stopping.
Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner 
exiting.
Jan 18 14:29:09 2003 (3442) CommandRunner qrunner 
caught SIGTERM.  Stopping.
Jan 18 14:29:09 2003 (3442) CommandRunner qrunner 
exiting.
Jan 18 14:29:09 2003 (3446) VirginRunner qrunner 
caught SIGTERM.  Stopping.
Jan 18 14:29:09 2003 (3446) VirginRunner qrunner 
exiting.
Jan 18 14:29:09 2003 (3440) ArchRunner qrunner caught 
SIGTERM.  Stopping.
Jan 18 14:29:09 2003 (3440) ArchRunner qrunner exiting.
Jan 18 14:29:10 2003 (3444) NewsRunner qrunner 
caught SIGTERM.  Stopping.
Jan 18 14:29:12 2003 (3444) NewsRunner qrunner 
exiting.

No other log has any indication of what might be 
happening.  

Is there a way to increase the logging somewhere so the 
cause can be identified?


----------------------------------------------------------------------

>Comment By: Thomas Wouters (twouters)
Date: 2003-03-22 01:54

Message:
Logged In: YES 
user_id=34209

No, having multiple versions of Python should not be causing
this. Nor should the SIGALRM handler being triggered cause
it, unless something is seriously broken in your setup --
but we've already been there.

The only way to see if a SIGTERM is actually being delivered
is running the processes under strace or gdb, but this
seriously disrupts regular operation. There is no way that i
know of to find out where a signal is coming from, once you
find out that it really is a signal. If it *isn't* a real
signal, I would start looking at libc bugs and other
platform bugs. You can try upgrading Python to 2.2.2 (the
latest bugfix release) but I would be very suprised if it
fixed your problem. RedHat does not have a great reputation
for stability, so be sure to check for any RedHat updates.



----------------------------------------------------------------------

Comment By: David Gibbs (midrangeman)
Date: 2003-03-17 18:44

Message:
Logged In: YES 
user_id=86339

Additional environment details:

Redhat Linux 8.0, uname = "Linux xxx.midrange.com 2.4.18-
26.8.0 #1 Mon Feb 24 10:21:42 EST 2003 i686 i686 i386 
GNU/Linux"

Python: 2.2.1

CPU: P4 2.4ghz, 512mb RAM

Dunno if this makes a difference, but I have the following 
directories ...

/usr/lib/python1.5  
/usr/lib/python2.1  
/usr/lib/python2.2

Any chance there is a conflict?


----------------------------------------------------------------------

Comment By: David Gibbs (midrangeman)
Date: 2003-01-24 19:31

Message:
Logged In: YES 
user_id=86339

I added some debug code to mailmanctl and found out that the 
sigalarm handler is firing just before the qrunners are terminating.

----------------------------------------------------------------------

Comment By: David Gibbs (midrangeman)
Date: 2003-01-22 22:31

Message:
Logged In: YES 
user_id=86339

After some further research, QRUNNER seems to stop after 
exactly 24 hours of operation.  That is, 24 hours after qrunner 
starts, it ends as if someone killed it with SIGTERM.  I know 
for a fact that nobody is actually doing this ... and no process 
on my system should be aware of the fact that qrunner is 
actually running.

I will not discount the possiblity that this is an environmental 
factor, but it seems to me that a daemon process should not 
be affected by environmental factors.  

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-01-19 23:46

Message:
Logged In: YES 
user_id=12800

I'm not sure what kind of logging would help.  Some process
somewhere is SIGTERMing the mailmanctl controller process. 
There's no way to know where a signal is coming from, so I'm
not sure what more you could do in mailmanctl.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103



More information about the Mailman-coders mailing list