[Mailman-Users] Single list dies for no apparent reason

[Juha Saarinen]

I'm seeing a weird problem on our listserver. A single list is giving me
headaches -- the Web interface for the listadmin becomes inaccessible
(nothing is returned to the client browser from the Web server), and I
see these entries in MAILMAN_DIR$/locks:

-rw-rw-r--   2 nobody  mailman    59 Jun  7 17:51 topnews.lock
-rw-rw-r--   2 nobody  mailman    59 Jun  7 17:51
topnews.lock.lists.idg.co.nz.76417
-rw-rw-r--   1 nobody  mailman    59 Jun  7 17:51
topnews.lock.lists.idg.co.nz.76419
-rw-rw-r--   1 nobody  mailman    59 Jun  7 18:06
topnews.lock.lists.idg.co.nz.76538
-rw-rw-r--   1 nobody  mailman    59 Jun  7 19:08
topnews.lock.lists.idg.co.nz.76917
-rw-rw-r--   1 nobody  mailman    59 Jun  7 19:29
topnews.lock.lists.idg.co.nz.77039

Sending an email to the list-request address creates more lock files,
but no reply from Mailman.

If I rm these, the list starts working again, but it only takes a day
for the list to fall over again. None of the other lists exhibit this
behaviour... 

Note that while the date is correct, the time is isn't -- it's in the
future, off by several hours (about six in each case, I think). The
system date is correct, and I run ntp to synch the clock.

This is on a FreeBSD 4.3-STABLE box with Mailman 2.03; the Web server is
Apache 1.3.19 mod_ssl 2.8.2.

What could be causing this?

-- Juha