Hi,
Yesterday after 5 years of operation ou mailman application has died it seems
to be barely running taking 3 or more hours to process lists...previous load
was 0.2 now its around 1 with a python process absorbing 1 CPU constantly.
We are running on RHEL3-32bit and the errors are,
Steven Jones wrote:
Yesterday after 5 years of operation ou mailman application has died it
seems to be barely running taking 3 or more hours to process lists...previous
load was 0.2 now its around 1 with a python process absorbing 1 CPU
constantly.
Which python process - i.e.which qrunner.
-users@python.org
Subject: Re: [Mailman-Users] Mailman no longer working or working very slowly
Steven Jones wrote:
Yesterday after 5 years of operation ou mailman application has died it
seems to be barely running taking 3 or more hours to process lists...previous
load was 0.2 now its around 1
: Thursday, 18 February 2010 3:56 a.m.
To: Steven Jones; mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman no longer working or working very slowly
Steven Jones wrote:
Yesterday after 5 years of operation ou mailman application has died it
seems to be barely running taking 3 or more hours
8---
Yes, that. Something is really hosed.
===
LOL..
===
Have you tried just restarting
Mailman?
=
Yes and a reboot.no difference...
=
What's at the start of that traceback leading up to the first call to
deepcopy?
=
Feb 16 15:05:45 2010
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Thursday, 18 February 2010 3:56 a.m.
To: Steven Jones; mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman no longer working or working very slowly
Steven Jones wrote:
Yesterday after 5 years of operation
Steven Jones wrote:
What's at the start of that traceback leading up to the first call to
deepcopy?
=
Feb 16 15:05:45 2010 (2632) Traceback (most recent call last):
File /var/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File
Steven Jones wrote:
Which python process - i.e.which qrunner.
Also look in Mailmans qfiles/* directories to see which one has a large
number of messages.
==
in.
==
We moved the queues and restarted its now running finewhich isnt a real
fix of course.
I think our messages
: [Mailman-Users] Mailman no longer working or working very slowly
Steven Jones wrote:
Which python process - i.e.which qrunner.
Also look in Mailmans qfiles/* directories to see which one has a large
number of messages.
==
in.
==
We moved the queues and restarted its now running
February 2010 2:26 p.m.
To: Mark Sapiro; mailman-users@python.org
Cc: Andrey Sabitov
Subject: Re: [Mailman-Users] Mailman no longer working or working very slowly
Hi,
Looking at shunt we have 127 itemsbut its not all the same list we have at
least 5 so far
When I do a, find /var/mailman
Steven Jones wrote:
While looking at the shunt queue I see a all pcks at a certain time (Feb 17
20:21) I have looked at so far have this as a content, instead of normal
content.
[r...@vuwunicosmtp004 shunt]# /var/mailman/bin/show_qfiles
Mark Sapiro wrote:
Steven Jones wrote:
While looking at the shunt queue I see a all pcks at a certain time (Feb 17
20:21) I have looked at so far have this as a content, instead of normal
content.
[r...@vuwunicosmtp004 shunt]# /var/mailman/bin/show_qfiles
As below.
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Thursday, 18 February 2010 3:03 p.m.
To: Steven Jones; mailman-users@python.org
Cc: Andrey Sabitov
Subject: RE: [Mailman-Users] Mailman no longer working or working very slowly
Steven Jones wrote:
While
Please copy your replise to the list.
Noah wrote:
Mark Sapiro wrote:
Where are the messages ('ls -lR /usr/local/mailman/qfiles/')?
yes
# ls -lR /usr/local/mailman/qfiles/ | wc -l
14430
# ls /usr/local/mailman/qfiles/
archive bounces in out shunt
I am puzzled. As I read the code, it is not possible to create the
shunt queue entry without also logging the error and the SHUNTING
message. Ordinarily, I would suggest that you might be logging to a
different set of log files in a different directory, but an earlier
post showed error log
Noah wrote:
I can see that only one installation is running.
But is it the same Mailman from the same directory as the one that was
running when the messages were shunted on Oct 6 21:33?
# /usr/local/bin/python -V
Python 2.4.3
after running bin/unshunt there are tons of SHUNT errors messages
Mark Sapiro wrote:
Noah wrote:
I can see that only one installation is running.
But is it the same Mailman from the same directory as the one that was
running when the messages were shunted on Oct 6 21:33?
# /usr/local/bin/python -V
Python 2.4.3
after running bin/unshunt
Noah wrote:
okay well there were no relevant SHUNT messages in logs/error . how
else could I have figure this out from bin/dumpdb ?
You can't. In general, there may be nothing at all wrong with the
message that was shunted. It may be shunted due to a software error or
some other condition not
mailman-2.1.9
FreeBSD 4-11
python-2.3.5_1
python-2.4.3
Hi there,
I recently upgraded python and mailman and a bunch of other FreeBSD
ports. mailman no longer appears to be forwarding mail. I can see in
my sendmail logs that the mail is received and piped to mailman with the
post command
On 10/7/06, Noah [EMAIL PROTECTED] wrote:
I recently upgraded python and mailman and a bunch of other FreeBSD
ports. mailman no longer appears to be forwarding mail. I can see in
my sendmail logs that the mail is received and piped to mailman with the
post command like -
Patrick Bogen wrote:
On 10/7/06, Noah [EMAIL PROTECTED] wrote:
I recently upgraded python and mailman and a bunch of other FreeBSD
ports. mailman no longer appears to be forwarding mail. I can see in
my sendmail logs that the mail is received and piped to mailman with the
post command like
Noah wrote:
yeah they are/were running. something a little deeper is happening
here. Again it is only one mail list at the momment that is not working
or posting rather. I can sub and unsub and receive notifications. but
the post is an issue right now.
Where are the messages ('ls -lR
22 matches
Mail list logo
