Myron Kowalski wrote:
>I think I found the (a) problem. There was a corrupted .db and .pck
>file in the
>qfiles/virgin directory. After I deleted those files, mailman would
>start up w/o error
>messages.
But I don't see that that would stop outgoing mail, so there may also
be a problem in th
Myron Kowalski wrote:
>
>I found one .pck out of place and move it. Restarted mailman with the
>same error.
>I moved the whole directory out of the way and restarted mailman--
>same error.
Originally, you said the messages were being archived, so that
indicated that IncomingRunner and ArchRunn
Myron Kowalski wrote:
>On Oct 25, 2007, at 5:54 PM, Mark Sapiro wrote:
>
>> Presumably, this is OutgoingRunner encountering the problem, because
>> IncomingRunner and ArchRunner both have to work for messages to be
>> archived.
>>
>> The problem may be as simple as some spurious file in qfiles/out
I think I found the (a) problem. There was a corrupted .db and .pck
file in the
qfiles/virgin directory. After I deleted those files, mailman would
start up w/o error
messages.
--myron
=
Myron Kowalski
MoCoSIN Network/Systems Administrator
Moravian College
[EMAI
On Oct 26, 2007, at 7:58 AM, Myron Kowalski wrote:
> On Oct 25, 2007, at 5:54 PM, Mark Sapiro wrote:
>
>> Myron Kowalski wrote:
>>
>>> I noticed that messages were not going out to my mailing lists. When
>>> I restarted mailman, this comes up. Any mail sent to the list is
>>> being archived,
>>> b
On Oct 25, 2007, at 5:54 PM, Mark Sapiro wrote:
> Myron Kowalski wrote:
>
>> I noticed that messages were not going out to my mailing lists. When
>> I restarted mailman, this comes up. Any mail sent to the list is
>> being archived,
>> but is not going to the members.
>>
>> Traceback (most recent
Myron Kowalski wrote:
>I noticed that messages were not going out to my mailing lists. When
>I restarted mailman, this comes up. Any mail sent to the list is
>being archived,
>but is not going to the members.
>
>Traceback (most recent call last):
> File "/users/mailman/bin/qrunner", line 270,
I noticed that messages were not going out to my mailing lists. When
I restarted mailman, this comes up. Any mail sent to the list is
being archived,
but is not going to the members.
Traceback (most recent call last):
File "/users/mailman/bin/qrunner", line 270, in ?
main()
File "/use
Young, Darren wrote:
>Mailman 2.1.5 on RedHat EL 3.0... Getting the following error, any
>thoughts?
>
>[EMAIL PROTECTED] bin]# ./qrunner -r Outgoing:0:1 -v
>Traceback (most recent call last):
> File "./qrunner", line 270, in ?
>main()
> File "./qrunner", line 230, in main
>qrunner.run()
Mailman 2.1.5 on RedHat EL 3.0... Getting the following error, any
thoughts?
[EMAIL PROTECTED] bin]# ./qrunner -r Outgoing:0:1 -v
Traceback (most recent call last):
File "./qrunner", line 270, in ?
main()
File "./qrunner", line 230, in main
qrunner.run()
File "/home/mailman-2.1/Mailm
My lists appear to be working fine, but...
In preparing for an upgrade, i was scanning the files in my mailman
directory. In the logs directory, I found one named qrunner, 52 MB in
size. In looking at the contents, I found a pattern of error reports,
about 2 per minute, of the following form:
D
I am also having qrunner problems, but they have to do with the
/etc/cron.d/mailman that tries to run. I am getting an authentication error
in my logs, (Nov 24 22:03:01 livingsky CRON[27016]: Authentication service
cannot retrieve authentication info.) and was wondering (after someone else
told me
I am also having qrunner problems, but they have to do with the
/etc/cron.d/mailman that tries to run. I am getting an authentication error
in my logs, (Nov 24 22:03:01 livingsky CRON[27016]: Authentication service
cannot retrieve authentication info.) and was wondering (after someone else
told me
Your logs tell it all;)
Check the permissions on the files, I believe there's a permcheck script in
the mailman directory.. Run that as root.
On Sunday 24 November 2002 8:50 pm, Victor Allen wrote:
> Background:
>
> Debian Stable with Postfix as MTA and Apache as webserver.
>
> After apt-get insta
Background:
Debian Stable with Postfix as MTA and Apache as webserver.
After apt-get install-ing mailman, I get the following crontab error over
and over again:
Traceback (most recent call last):
File "/var/lib/mailman/cron/qrunner", line 276, in ?
lock.lock(timeout=0.5)
File "/var/lib/m
Hello,
Thanks very much. I upgrade to Mailman 2.0.13 and all is ok.
regards,
rozio
El Thursday 01 August 2002 16:24, Richard Barrett ha dicho:
> This error is a known problem if you are using an older version of Python
> than 2.0 and the subject of prior postings to this list.
>
> Insta
This error is a known problem if you are using an older version of Python
than 2.0 and the subject of prior postings to this list.
Installing Mailman 2.0.13 should cure it: the Mailman 2.0.13 the release
note says:
This release fixes some Python 1.5.2 incompatibilities that crept into
Mailma
bject: [Mailman-Users] qrunner error
Date: Thu, 1 Aug 2002 14:55:09 +0200
From: Rocio Alfonso Pita <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
hello,
I have mailman version 2.0.12. This version was actualized on 26/07/2002.
>From 30/07/2002 I see in error log every minute this:
Aug 01
hello,
I have mailman version 2.0.12. This version was actualized on 26/07/2002.
>From 30/07/2002 I see in error log every minute this:
Aug 01 14:14:01 2002 qrunner(23729): Traceback (innermost last):
Aug 01 14:14:01 2002 qrunner(23729): File "/usr/local/mailman/cron/qrunner",
line 283, in
Hi!
Recently I posted that my crons don't work, but I just discovered some
errors in Mailman log files.
In qrunner log there is following:
Feb 04 12:01:01 2002 (15869) Unlinking orphaned .db file:
/var/spool/mailman/qfiles/386e8adf9c3b966180d9d5db1109a3f59c722914.db
and in the error log:
Feb
Does anyone know what this error means and how to fix it.
Traceback (innermost last):
File "/home/mailman/cron/qrunner", line 78, in ?
import time
ImportError: /usr/lib/python1.5/lib-dynload/timemodule.so: undefined
symbol: PyErr_Format
--
###
Webmaster
[EMAIL P
Hi all,
Can anyone tell me what these errors translate to ...
May 09 18:10:01 2001 (5646) Unlinking orphaned .db file:
/home/mailman/qfiles/13b85892a42e3150b7155af5a138950ffc120d28.db
May 09 23:10:01 2001 (6396) Unlinking orphaned .db file:
/home/mailman/qfiles/22c01ddde
I keep getting this error message sent to me every minute. What is
wrong. Nothing has changed on our system. I am using RED HAT 7.0 with
Mailman 2.0.3 with the right python version
No mail is being sent, does someone have a solution?
Traceback (innermost last):
File "/home/mailman/cron/qrunner"
23 matches
Mail list logo
