[Mailman-Users] [resend] Could not acquire qrunner lock

[Jon Carnes]

Hmmm, here are some recommendations that may or may not help:

 - Upgrade your python to version 2.2 (then re-install Mailman) - The
problem really sounds like a python problem!

 - Use an EXT2 filesystem instead of EXT3 for /var and for ~mailman -
lots of files are created in these directories in course of operations
and ext3 could slow down the system.

Good Luck - Jon Carnes

===
On Wed, 2003-04-30 at 14:48, Josep L. Guallar-Esteve wrote:
> Hi,
> 
> I send this email about a week ago. Does anyone know anything about this 
> problem?
> 
> ------------ 
> We use mailman at work to manage a few lists (16) with an average of 10 
> users/list. 
> 
> The mail server is a Red Hat Linux 7.3 server, on a P-III-550/1,354,424KB with 
> SCSI drives using ext3 filesystem. We run Postfix version 1.1.7-2 + Mailman 
> version 2.0.13 + Python 1.5.2-43.73. We have a total of 75 mail users. The 
> messages are text-based, i.e., usualy pretty small.
> 
> Postfix works pretty fast. But mailman is slow. Mails to mailing lists take 
> about 6 minutes. Individual mails are about instantaneous:
> 
> Received: from ************ by by ********* (Postfix) with ESMTP
> 	id *******; Wed, 23 Apr 2003 12:54:22 -0400 (EDT)
> Delivered-To: sysadmin at easternrad.com
> Received: from ****** by ******** (Postfix) with SMTP id *********
> 	for <mailinglist@**********>; Wed, 23 Apr 2003 12:48:37 -0400 (EDT)
> 
> Although the smtp log says that it only takes a few seconds:
> 
> (...)
> Apr 23 07:12:02 2003 (28717) smtp for 6 recips, completed in 1.588 seconds
> Apr 23 10:56:10 2003 (30680) smtp for 31 recips, completed in 7.995 seconds
> Apr 23 12:54:23 2003 (31998) smtp for 5 recips, completed in 2.410 seconds
> (...)
> 
> I've checked mailman logs and I've found this error, over and over again, at 
> qrunner log file:
> 
> (...)
> Apr 22 23:53:01 2003 (25973) Could not acquire qrunner lock
> Apr 22 23:54:00 2003 (25979) Could not acquire qrunner lock
> Apr 22 23:55:02 2003 (25994) Could not acquire qrunner lock
> Apr 22 23:56:03 2003 (26028) Could not acquire qrunner lock
> Apr 22 23:57:01 2003 (26035) Could not acquire qrunner lock
> Apr 22 23:58:01 2003 (26043) Could not acquire qrunner lock
> Apr 22 23:59:01 2003 (26045) Could not acquire qrunner lock
> (...)
> 
> I've searched the mailman users archives, and the only symilar error was 
> 
> Date: Tue, 10 Sep 2002 03:54:06 -0400 (EDT)
> Subject: [Mailman-Users] Could not acquire qrunner lock
> 
> The problem there was solved because there were a set of files showing up in 
> the log file, that had to be deleted to improve performance 
> (/home/mailman/qfiles/001b6903fc7ad5bdcdfa930711200d5a1306e7af* )
> 
> Unfortunately, no filenames show up in my logs.
> 
> Also, permissions and DB both look OK:
> # ./check_perms
> No problems found
> ]# ./check_db all
> /home/mailman/lists/all/config.db is fine
> /home/mailman/lists/all/config.db.last is fine
> #
> 
> 
> (changed from last time)
> 
> *Right now* , qrunner **is** running. And I **do** see qrunner lock files at 
> /home/mailman/locks .  And python is eating all my CPU   
> 
> (from top)
> PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
> 15616 mailman   20   0  350M 350M  1580 S    98.0 10.0  18:33 python
> 
> 
> Any ideas?
> 
> 
> Regards,
> Josep