on 10/9/02 11:03 AM, Jon Carnes at [EMAIL PROTECTED] typed:
> Just to remove any thought of rights issues, how about setting the
> rights to that file so that it is read/writable to all.
>
> The current rights should look like this:
> -rw-rw-r-- mailman mailman
They do now. But they didn't
On Wed, 2002-10-09 at 00:37, Chris Lawson wrote:
> admin(8367): fp = open(self.__filename, 'w')
> admin(8367): IOError: [Errno 13] Permission denied:
> '/home/mailman/lists/test/request.db'
>
Just to remove any thought of rights issues, how about setting the
rights to that file so that it is
on 10/8/02 2:01 PM, Jon Carnes aka [EMAIL PROTECTED] wrote:
> On Mon, 2002-10-07 at 23:08, Chris Lawson wrote:
>
>>> Are the proper directories setup as Set-gid?
>>
>> Um... a bit of a knowledge blind spot for me. The directory of a given
>> private list archive is mailman.mailman.
>
> In the
On Tue, 2002-10-08 at 08:28, Chris Lawson wrote:
>
> Another bit of wierdness. There are a ton of .msg and .db files piled up in
> /var/spool/mailman/qfiles
>
> Or is that normal?
Not normal. You might try running qrunner by hand and see what happens:
su mailman
/usr/bin/python -S ~mailman
On Mon, 2002-10-07 at 23:08, Chris Lawson wrote:
> > Are the proper directories setup as Set-gid?
>
> Um... a bit of a knowledge blind spot for me. The directory of a given
> private list archive is mailman.mailman.
In the INSTALL file for Mailman it details some setup directions:
Make sure t
on 10/7/02 7:27 PM, Jon Carnes aka [EMAIL PROTECTED] wrote:
> Hmmm, interesting error. Have you run ~mailman/bin/check_perms ? Are
> the proper directories setup as Set-gid? Have you run out of space on
> any of your volumes?
Another bit of wierdness. There are a ton of .msg and .db files pile
on 10/7/02 7:27 PM, Jon Carnes aka [EMAIL PROTECTED] wrote:
> Hmmm, interesting error. Have you run ~mailman/bin/check_perms ?
Yes. "No problems found."
> Are the proper directories setup as Set-gid?
Um... a bit of a knowledge blind spot for me. The directory of a given
private list archive is
Hmmm, interesting error. Have you run ~mailman/bin/check_perms ? Are
the proper directories setup as Set-gid? Have you run out of space on
any of your volumes?
> I'm running mailman 2.0.13-0.7.0 aka
> the RedHat RPM version of 2.0.13 on RedHat 7.0
>
> I just sent a message to my test list, and
on 10/7/02 10:47 AM, Jon Carnes aka [EMAIL PROTECTED] wrote:
> This one should be in the FAQ if it is not already.
Leaping before I look, once again. Of course it is. I followed the advice
and checked for a running qrunner. There was none. I went to
/usr/share/mailman/locks/ and deleted *a ton*
This one should be in the FAQ if it is not already.
This is normal in Mailman version 2.0.x which you are *probably* running
(you didn't tell us your version or really anything about your system -
shame on you!)
This version of Mailman uses a cron job to launch qrunner every minute -
but if qrun
Hi.
My qrunner log (in /var/log/mailman) is generating hundreds of lines like
the following:
Oct 07 10:33:04 2002 (6942) Could not acquire qrunner lock
What is trying to lock qrunner? Why would it be failing to acquire a lock?
What would be the consequences of failing to acquire a lock?
cmkl
Simon,
That is not an error, as such. You get that notice in your qrunner
log whenever qrunner starts up and finds that there is already
another qrunner process running, by virtue of the fact that there is
a lock in ~mailman/locks/. Now ~mailman/qfiles is where emails and
such live, so if y
Hmmm,
My lists stopped last night.
This was in the qrunner log:
May 14 16:29:01 2002 (11337) Could not acquire qrunner lock
I have upgraded to Python 2.2.1
Downloaded, configured, make install, mailman-2.0.10
And I still get the error.
I have removed all the files from
/home/mailman/qfiles
qrunner cron alleviate difficult locks? Is this a race condition issue
with qrunner?
>From: "Marc MERLIN" <[EMAIL PROTECTED]>
>To: "Jay S Curtis" <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: [Mailman-Users] qrunner lock
>Date: Thu,
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 he
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 b
On Thu, Feb 28, 2002 at 07:48:45PM +, 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
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 qrunne
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..
--
Jay S. Curtis
MM 2.0.8
-
The same problem appeared last day on our mailhost (cnl.di.uoa.gr) running
mailman 2.0.6 on RedHat 7.1 (kernel 2.4.3/sendmail 8.11.6) but it seems bind
to a speciffic email message with many attachments (word documents) when
that message was removed from the qrunner queue all returnd to normal.
-
- Original Message -
From: "Lalo Castro" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 26, 2001 7:02 PM
Subject: [Mailman-Users] Qrunner lock
> Hello,
> I recently installed mailman 2.0.6 on our OpenBsd 2.9 mail machine,
> run
Hello,
I recently installed mailman 2.0.6 on our OpenBsd 2.9 mail machine,
running python 1.5.2. Our qrunner is taking an extraordinarily long
time to get going. 450 second smtp cycles.
The qrunner log shows 'Could not acquire qrunner lock'.
The smtp error log shows: smtp-failure:
My qrunner log is filling up with:
Jan 15 19:12:04 2001 (183) Could not acquire qrunner lock
What causes qrunner to not be able to get a lock? The only thing I can see
in the logs at the particular time this one was generated was a successful
post to one of the lists.
Thanks for any help.
--
23 matches
Mail list logo
