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
On Thu, Feb 28, 2002 at 07:48:45PM +0000, Michael Johnson wrote:
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?
Unless you are having crashes (like a bad message crashing qrunner), in which case, it should show up in your mailman logs (~mailman/logs/), qrunner doesn't just casually die and leave a lock behind. At least, it doesn't on my sites.
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
Hmmm.. qrunner not running & no lockfile found (using postfix) Am I barking up the wrong tree?
On Thursday 28 February 2002 02:48 pm, you wrote:
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>
<<snip>>
On Thu, Feb 28, 2002 at 02:58:30PM -0500, Jay S Curtis wrote:
Hmmm.. qrunner not running & no lockfile found (using postfix) Am I barking up the wrong tree?
Hold on, so you are saying that your qrunner is running once a minute from cron, that it complains that it's finding a lockfile and hence doesn't run, but that you can't find a lockfile?
If so, run the cron entry by hand under strace Something like: su - mailman strace -f /usr/bin/python -S /var/local/mailman/cron/qrunner
Hopefully that will give you a clue as to why it's not running
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
I know I've seen the answer to this question on this list, but I can't find it in the archives.
I therefore ask again. (sorry all)
We have ca. 100 lists and I want to change the "Ceiling for acceptable number of postings" variable for each one. There is a quick command line way of doing this (A three line shell script perhaps) but I don't remember how.
Any suggestions?
Thanks Hakon
participants (4)
-
Hakon Brynildsen -
Jay S Curtis -
Marc MERLIN -
Michael Johnson