[Mailman-Users] Mail going to list archives but not to list!

[Allan Trick]

At 03:23 PM 10/15/2006, Mark Sapiro wrote:

>Is OutgoingRunner running? If not, are there any messages in 
>Mailman's 'qrunner' log indicating why or when it stopped?

I think so.  See below.

>Have you tried 'bin/mailmanctl restart'?

Yes, to no avail.  When I do that, this is what is logged in the qrunner log:

>Oct 15 16:24:25 2006 (3753) NewsRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (1662) Master watcher caught SIGINT.  Restarting.
>Oct 15 16:24:25 2006 (3752) VirginRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (3754) ArchRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (3753) NewsRunner qrunner exiting.
>Oct 15 16:24:25 2006 (3756) CommandRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (3752) VirginRunner qrunner exiting.
>Oct 15 16:24:25 2006 (3756) CommandRunner qrunner exiting.
>Oct 15 16:24:25 2006 (3757) BounceRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (3757) BounceRunner qrunner exiting.
>Oct 15 16:24:25 2006 (3751) RetryRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (3751) RetryRunner qrunner exiting.
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3756, sig: None, sts: 2, class: CommandRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (3755) IncomingRunner qrunner caught SIGINT.  Stopping.
>Oct 15 16:24:25 2006 (3754) ArchRunner qrunner exiting.
>Oct 15 16:24:25 2006 (3755) IncomingRunner qrunner exiting.
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3757, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3753, sig: None, sts: 2, class: NewsRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3755, sig: None, sts: 2, class: IncomingRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3751, sig: None, sts: 2, class: RetryRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3754, sig: None, sts: 2, class: ArchRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (1662) Master qrunner detected subprocess exit
>(pid: 3752, sig: None, sts: 2, class: VirginRunner, slice: 1/1) [restarting]
>Oct 15 16:24:25 2006 (8830) NewsRunner qrunner started.
>Oct 15 16:24:25 2006 (8828) CommandRunner qrunner started.
>Oct 15 16:24:25 2006 (8832) IncomingRunner qrunner started.
>Oct 15 16:24:25 2006 (8833) RetryRunner qrunner started.
>Oct 15 16:24:25 2006 (8834) ArchRunner qrunner started.
>Oct 15 16:24:25 2006 (8829) BounceRunner qrunner started.
>Oct 15 16:24:25 2006 (8835) VirginRunner qrunner started.

>Are there any recent entries in Mailman's 'error', 'smtp', and 
>'smtp-failure' logs?

No - no entries in smtp since last Wednesday (but Mailman still 
archives attempts to send out, as if they went).  However, the error 
log is a bit strange.  This is how it starts, exactly:

>Jan 15 12:15:36 2004 mailmanctl(24486): Primary start-up and 
>shutdown script for Mailman's qrunner daemon.
>
>This script starts, stops, and restarts the main Mailman queue runners, making
>sure that the various long-running qrunners are still alive and kicking.  It
>does this by forking and exec'ing the qrunners and waiting on their pids.
>When it detects a subprocess has exited, it may restart it.
>
>The qrunners respond to SIGINT, SIGTERM, and SIGHUP.  SIGINT and SIGTERM both
>cause the qrunners to exit cleanly, but the master will only restart qrunners
>that have exited due to a SIGINT.  SIGHUP causes the master and the qrunners
>to close their log files, and reopen then upon the next printed message.
>
>The master also responds to SIGINT, SIGTERM, and SIGHUP, which it simply
>passes on to the qrunners (note that the master will close and reopen its own
>log files on receipt of a SIGHUP).  The master also leaves its own process id
>in the file data/master-qrunner.pid but you normally don't need to use this
>pid directly.  The `start', `stop', `restart', and `reopen' commands handle
>everything for you.
>
>Usage: ./mailmanctl [options] [ start | stop | restart | reopen ]
>
>Options:
>
>     -n/--no-restart
>         Don't restart the qrunners when they exit because of an error or a
>         SIGINT.  They are never restarted if they exit in response to a
>         SIGTERM.  Use this only for debugging.  Only useful if the `start'
>         command is given.
>
>     -u/--run-as-user
>         Normally, this script will refuse to run if the user id and group id
>         are not set to the `mailman' user and group (as defined when you
>         configured Mailman).  If run as root, this script will change to this
>         user and group before the check is made.
>
>         This can be inconvenient for testing and debugging 
> purposes, so the -u
>         flag means that the step that sets and checks the uid/gid is skipped,
>         and the program is run as the current user and group.  This flag is
>         not recommended for normal production environments.
>
>         Note though, that if you run with -u and are not in the 
> mailman group,
>         you may have permission problems, such as begin unable to delete a
>         list's archives through the web.  Tough luck!
>
>     -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.
>
>     -q/--quiet
>         Don't print status messages.  Error messages are still printed to
>         standard error.
>
>     -h/--help
>         Print this message and exit.
>
>Commands:
>
>     start   - Start the master daemon and all qrunners.  Prints a message and
>               exits if the master daemon is already running.
>
>     stop    - Stops the master daemon and all qrunners.  After stopping, no
>               more messages will be processed.
>
>     restart - Restarts the qrunners, but not the master process.  Use this
>               whenever you upgrade or update Mailman so that the 
> qrunners will
>               use the newly installed code.
>
>     reopen  - This will close all log files, causing them to be re-opened the
>               next time a message is written to them
>Jan 15 12:15:36 2004 mailmanctl(24486):
>Jan 15 12:15:36 2004 mailmanctl(24486): No command given.
>Jan 15 12:17:25 2004 mailmanctl(24740): No child with pid: 22488
>Jan 15 12:17:25 2004 mailmanctl(24740): [Errno 3] No such process
>Jan 15 12:17:25 2004 mailmanctl(24740): Stale pid file removed.
>Jan 15 12:25:00 2004 qrunner(25779): Run one or more qrunners, once 
>or repeatedly.
>
>Each named runner class is run in round-robin fashion.  In other words, the
>first named runner is run to consume all the files currently in its
>directory.  When that qrunner is done, the next one is run to consume all the
>files in /its/ directory, and so on.  The number of total iterations can be
>given on the command line.
>
>Usage: ./qrunner [options]
>
>Options:

. . . . <snip> . . . .

Does look like I expect it should.  Does this look like corruption 
that may have something to do with my problem?

Thx,

Allan

P.S.  Sorry about the duplicate post of my original message!  I 
wasn't sure I was subscribed.  My message didn't appear for many 
minutes so I thought there was a problem.