[Mailman-Developers] Re: First big Mailing

Barry A. Warsaw barry@zope.com
Fri, 11 Jan 2002 01:42:35 -0500

>>>>> "MP" == Marc Perkel <marc@perkel.com> writes:

    MP> Actually the problem is lack of logs.

Is there nothing useful in errors/log?  If not, it definitely ain't a
Mailman problem.
    MP> Mailman appears to be frozen with python tasks backing up as
    MP> if the mailman tasks are locking up. I'm sure it's also
    MP> processing a lot of bounced email.

Well, you can double check and see if there are any stale lock files
in the locks directory.  If you're exhausting your system resources as
Chuq points out, and your Python processes are either hanging,
thrashing with other processes, or just getting waxed by your kernel,
the processes holding the locks will fail hard, leaving stale locks

    MP> Could it be running into a task limit - with just being
    MP> overloaded? Is there something to check the integrity of the
    MP> databases?

See Chuq's excellent post.  Others in more favorable timezones are
going to have to take it from here tonight, I'm beat.  But you can
make sure your list config.db files are still good by using bin/dumpdb
or bin/config_list.  Use --help to get synopsis.