[Mailman-Users] qrunner locks?

[Lim Hui Min]

Dear all,

I am using FreeBSD 4.0 and mailman-2.0b6
the problem of qrunner got stuck halfway reoccur after i upgraded from 2.0b5
the qrunner log shows

Could not acquire qrunner lock

if a mesg size bigger than 40kb is sent to the list. the list will stop
functioning until the lock files and the process is cleared.

please refer to the url for similar problem that occur in 2.0b5.

http://www.python.org/pipermail/mailman-users/2000-September/007257.html

does anyone got a fix for this?


HM



At Wed, 4 Oct 2000 10:09:03 -0700, Chuq Von Rospach wrote:
>At 12:47 PM -0400 10/4/00, Chris Hedemark wrote:
>>You are not alone.  I have Mailman 2.0beta6 on Red Hat 6.2.  Check this
out:

>The answer is:

>it depends. If qrunner is already running when cron spawns qrunner,
>the new one can't get the lock and exits. that's a feature.

>If qrunner isn't running and it can't get a lock, that's a problem,
>usually permission, sometimes a leftover lock.

>So you need to go into the system and see what it's doing at the
>time. If you see the log entry hit, try "ps -ef | grep mailman" and
>see what's going on with mailman. And check your ~mailman/locks
>directory for leftover lock files and the like.

>And make sure check_perms runs clean.

>--
>Chuq Von Rospach - Plaidworks Consulting (mailto:chuqui at plaidworks.com)
>Apple Mail List Gnome (mailto:chuq at apple.com)

>You seem a decent fellow. I hate to die.