[Mailman-Users] Mailman shuts down silently under FreeBSD
I'm running Mailman out of FreeBSD's 'ports' collection, and for some reason qrunner shuts down silently every now and again. Today, for instance, I created a mailing list through the Mailman command-line interface, then tried to send that list a test message. Nothing arrived at the subscribers' mailboxes. Having noticed this behavior before, I restarted qrunner via /usr/local/etc/rc.d/mailman.sh start It restarted, and the queue cleared; all the messages that should have been delivered were delivered. The machine hasn't restarted; 'uptime' on that end reads 2:58PM up 21 days, 12:43, 0 users, load averages: 1.98, 2.10, 1.99 So can anyone think of why qrunner would have shut down? Thanks much, Steve -- Stephen R. Laniel [EMAIL PROTECTED] +(617) 308-5571 http://laniels.org/ PGP key: http://laniels.org/slaniel.key signature.asc Description: Digital signature -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman shuts down silently under FreeBSD
Stephen R Laniel wrote: So can anyone think of why qrunner would have shut down? Have you looked at the Mailman logs 'error' and 'qrunner'? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman shuts down silently under FreeBSD
On Thu, Oct 20, 2005 at 12:12:21PM -0700, Mark Sapiro wrote: Have you looked at the Mailman logs 'error' and 'qrunner'? Stupid me. I forgot to look at the qrunner log this time 'round, because the last time I had a mailman problem it looked like the log wasn't getting any activity. Anyway, see below for what the log says. Any idea? Thanks for pointing me in the direction of something I should have thought of. :-) /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59829) VirginRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59828) ArchRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59829) VirginRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59828) ArchRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59830) IncomingRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59830) IncomingRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59831) BounceRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59831) BounceRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59832) CommandRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59832) CommandRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59833) NewsRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59833) NewsRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59834) OutgoingRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59834) OutgoingRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59835) RetryRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59835) RetryRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master watcher caught SIGTERM. Exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63166) ArchRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63167) BounceRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63170) NewsRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63174) RetryRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63169) IncomingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63171) OutgoingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63172) VirginRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63168) CommandRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:23 2005 (85507) CommandRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:23 2005 (85509) NewsRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85505) ArchRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85510) OutgoingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85506) BounceRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85508) IncomingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85511) VirginRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85512) RetryRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63168) CommandRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63168) CommandRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63169) IncomingRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63169) IncomingRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63170) NewsRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34
Re: [Mailman-Users] Mailman shuts down silently under FreeBSD
Stephen R Laniel wrote: /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59829) VirginRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59828) ArchRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59829) VirginRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59828) ArchRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59830) IncomingRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59830) IncomingRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59831) BounceRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59831) BounceRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59832) CommandRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59832) CommandRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59833) NewsRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59833) NewsRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59834) OutgoingRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59834) OutgoingRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59835) RetryRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59835) RetryRunner qrunner exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master watcher caught SIGTERM. Exiting. /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit /usr/local/mailman/logs/qrunner:Oct 17 16:44:27 2005 (59007) Master qrunner detected subprocess exit This looks like a normal shut down as a result of 'bin/mailmanctl stop' or 'kill -TERM' of the master watcher process. Presumably, no one knowingly did this, but is it possible the OS did it because of some process limit? /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63166) ArchRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63167) BounceRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63170) NewsRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63174) RetryRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63169) IncomingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63171) OutgoingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63172) VirginRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 19 13:57:48 2005 (63168) CommandRunner qrunner started. Here it looks like a normal start. /usr/local/mailman/logs/qrunner:Oct 20 13:20:23 2005 (85507) CommandRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:23 2005 (85509) NewsRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85505) ArchRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85510) OutgoingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85506) BounceRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85508) IncomingRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85511) VirginRunner qrunner started. /usr/local/mailman/logs/qrunner:Oct 20 13:20:24 2005 (85512) RetryRunner qrunner started. Here it looks like a second start was done while the first set of qrunners from Oct 19 13:57:48 2005 was still running. You mentioned in your first post starting mailman with '/usr/local/etc/rc.d/mailman.sh start'. This script probably does 'bin/mailmanctl -s start'. The '-s' stale lock cleanup is appropriate for a system restart script, but not for a running system. It is better to start mailman on a running system with 'bin/mailmanctl start', at least for the first try. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63168) CommandRunner qrunner caught SIGTERM. Stopping. /usr/local/mailman/logs/qrunner:Oct 20 13:57:34 2005 (63168) CommandRunner qrunner exiting.
