More importantly, how to prevent such things as future occurences. Certainly, manually checking and removing the lock may work on a per instance basis, but, in reality, it appears less than ideal. This problem happens way to frequently. Would changing the frequency depending the system of qrunner cron alleviate difficult locks? Is this a race condition issue with qrunner?
From: "Marc MERLIN" <marc_news@vasoftware.com> To: "Jay S Curtis" <camel@lrllamas.com> CC: mailman-users@python.org Subject: Re: [Mailman-Users] qrunner lock Date: Thu, 28 Feb 2002 11:39:21 -0800 List-Archive: <http://mail.python.org/pipermail/mailman-users/>
On Thu, Feb 28, 2002 at 02:03:31PM -0500, Jay S Curtis wrote:
Someone remind me how to fix this (or make it stop)
Feb 28 10:25:02 2002 (15932) Could not acquire qrunner lock Feb 28 10:53:02 2002 (16194) Could not acquire qrunner lock Feb 28 13:50:03 2002 (17701) Could not acquire qrunner lock etc..etc..etc..
check if qrunner is running yes) do a strace -f -p pidofqrunner to see what it's busy doing no) remove the qrunner lock in ~mailman/locks/
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users
Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com