Back at the beginning of this thread, Fletcher Cocquyt wrote:
Config:
Solaris 10 x86
Python 2.5.2
Mailman 2.1.9 (8 Incoming queue runners - the leak rate increases with this)
SpamAssassin 3.2.5
At this point I am looking for ways to isolate the suspected memory leak - I
am looking at using dtr
I did a test - I disabled the SpamAssassin integration and watched the heap
grow steadily - I do not believe its SA related:
[EMAIL PROTECTED]:mailman-2.1.9 10:51pm 68 # pmap 22804 | egrep heap
08175000 14060K rwx--[ heap ]
[EMAIL PROTECTED]:mailman-2.1.9 10:51pm 69 # pmap 22804 | egrep heap
On 7/2/08, John Hicks wrote:
I have no idea how far the system has gotten in processing the entire list.
Is there any way to find out? (The message already appears in the archives
but there is no entry in the Mailman "post" log.)
Other than what is showing up in the Mailman smtp logs and in
I have been hosting a mailing list of 16,000 names which has been
purring along for over a year now with no problems. (I am running
Mailman 2.1.5, Postfix-2.2.10, on RHES 4.0)
Recently I reconfigured this list to enable personalization so my client
could do a better job of processing cancella
On 7/1/08, Fletcher Cocquyt wrote:
Fletcher Cocquyt
Senior Systems Administrator
Information Resources and Technology (IRT)
Stanford University School of Medicine
BTW, in case it hasn't come through yet -- I am very sensitive to
your issues. In my "real" life, I am currently employed as
On 7/1/08, Mark Sapiro wrote:
In this snapshot
PID USERNAME LWP PRI NICE SIZE RES STATETIMECPU COMMAND
10123 mailman1 590 314M 311M sleep1:57 0.02% python
10131 mailman1 590 310M 307M sleep1:35 0.01% python
10124 mailman1 590 309M 78
On 7/1/08, Fletcher Cocquyt wrote:
Pmap shows its the heap
[EMAIL PROTECTED]:in 8:08pm 64 # pmap 24167
24167:/bin/python /opt/mailman-2.1.9/bin/qrunner
--runner=IncomingRunner:5:8
08038000 64K rwx--[ stack ]
0805 940K r-x-- /usr/local/stow/Python-2.5.2/bin/python
08
On 7/1/08, Mark Sapiro wrote:
In any case, I know you're reluctant to just let it run, but I think if
you did let it run for a couple of days that the IncomingRunners
wouldn't get any bigger than the 310 +- MB that you're already seeing
after 3 hours, and the rest of the runners would remain
Fletcher Cocquyt wrote:
>Pmap shows its the heap
>
>[EMAIL PROTECTED]:in 8:08pm 64 # pmap 24167
>24167:/bin/python /opt/mailman-2.1.9/bin/qrunner
>--runner=IncomingRunner:5:8
>08038000 64K rwx--[ stack ]
>0805 940K r-x-- /usr/local/stow/Python-2.5.2/bin/python
>0814A000 1
Pmap shows its the heap
[EMAIL PROTECTED]:in 8:08pm 64 # pmap 24167
24167:/bin/python /opt/mailman-2.1.9/bin/qrunner
--runner=IncomingRunner:5:8
08038000 64K rwx--[ stack ]
0805 940K r-x-- /usr/local/stow/Python-2.5.2/bin/python
0814A000 172K rwx-- /usr/local/stow/Python
Mark Sapiro wrote:
Which processes correspond to which runners. And why are the two
processes that have apparently done the least the ones that have grown
the most.
and
What are these last 2? Presumably they are the missing NewsRunner and
RetryRunner, but what is the extra stuff in the ps ou
That's great Mark, many thanks.
Just recapping for anyone else's interest.
--
After installing Mailman, when first attemping to create a new list
using the webpage - it returned a "You don't have permission".
(Creating a new list f
Fletcher Cocquyt wrote:
>
>Here is the current leaked state since the the cron 13:27 restart only 3
>hours ago:
>last pid: 20867; load averages: 0.53, 0.47, 0.24
>16:04:15
>91 processes: 90 sleeping, 1 on cpu
>CPU states: 99.1% idle, 0.3% user, 0.6% kernel, 0.0% iowait, 0.0% swap
>Memory:
On 7/1/08 3:37 PM, "Mark Sapiro" <[EMAIL PROTECTED]> wrote:
> Fletcher Cocquyt wrote:
>
>> Not finding a "leak" ref - save a irrelevant (for this runner issue) admindb
>
>
> Nothing has been done in Mailman to fix any memory leaks. As far as I
> know, nothing has been done to create any eith
Fletcher Cocquyt wrote:
>Not finding a "leak" ref - save a irrelevant (for this runner issue) admindb
Nothing has been done in Mailman to fix any memory leaks. As far as I
know, nothing has been done to create any either.
If there is a leak, it is most likely in the underlying Python and not
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Finkel wrote:
| * Mark Sapiro <[EMAIL PROTECTED]>:
|> I am happy to announce the final release of the Mailman 2.1.11.
|
| Ralf Hildebrandt <[EMAIL PROTECTED]> replied:
|> I get lots of these:
|> initialization differ in signedness
|> src/_koco_u
Not finding a "leak" ref - save a irrelevant (for this runner issue) admindb
one:
[EMAIL PROTECTED]:mailman-2.1.11 1:26pm 58 # ls
ACKNOWLEDGMENTS Mailman README-I18N.enSTYLEGUIDE.txt
configure doc misc templates
BUGS Makefile.in
>I'm having a hard time finding the release notes for 2.1.11 - can you please
>provide a link?
>(I want to see where it details any memory leak fixes since 2.1.9)
>Fletcher Cocquyt
>Senior Systems Administrator
>Information Resources and Technology (IRT)
>Stanford University School of Medicine
The
I'm having a hard time finding the release notes for 2.1.11 - can you please
provide a link?
(I want to see where it details any memory leak fixes since 2.1.9)
thanks
On 7/1/08 10:09 AM, "Vidiot" <[EMAIL PROTECTED]> wrote:
>> Solaris 10 x86
>> Python 2.5.2
>> Mailman 2.1.9 (8 Incoming queue run
* Mark Sapiro <[EMAIL PROTECTED]>:
> I am happy to announce the final release of the Mailman 2.1.11.
Ralf Hildebrandt <[EMAIL PROTECTED]> replied:
>I get lots of these:
>initialization differ in signedness
>src/_koco_uhc.h:2349: warning: pointer targets in initialization
>differ in signedness
>src
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 2:42 PM, Ralf Hildebrandt wrote:
* Mark Sapiro <[EMAIL PROTECTED]>:
I am happy to announce the final release of the Mailman 2.1.11.
I get lots of these:
initialization differ in signedness
src/_koco_uhc.h:2349: warning: pointer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 2:40 PM, Hank van Cleef wrote:
I'm also concerned about this proposed scheme to discontinue montnly
mailings. It most definitely needs some mechanism whereby a user can
reset or re-obtain their password without moderator interven
* Mark Sapiro <[EMAIL PROTECTED]>:
> I am happy to announce the final release of the Mailman 2.1.11.
I get lots of these:
initialization differ in signedness
src/_koco_uhc.h:2349: warning: pointer targets in initialization
differ in signedness
src/_koco_uhc.h:2349: warning: pointer targets in init
- Pesan Asli
Dari: Mark Sapiro <[EMAIL PROTECTED]>
Kepada: [EMAIL PROTECTED]; Mailman-Users@python.org
Terkirim: Selasa, 1 Juli, 2008 20:59:40
Topik: Re: [Mailman-Users] Bug reported when creating a new list from webpage
Mark Dale wrote:
>
>Can anyone shed any light on this error I ge
The esteemed Mark Sapiro has said:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The release notes and NEWS file for Mailman 2.1.11 contains the
> following innocuous looking item.
>
> ~- Improved bounce loop detection and handling in BounceRunner.py.
>
> This actually first appea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The release notes and NEWS file for Mailman 2.1.11 contains the
following innocuous looking item.
~- Improved bounce loop detection and handling in BounceRunner.py.
This actually first appeared in 2.1.11rc2. It turns out this had an
unintended c
Hi all, I am finally doing a followup on this. Mark asked me to vet his
proposed solution to my ISP and see what they said. They actually took it
quite seriously and discussed it. I just got a phone call from the head
guy in that department who wanted to speak to me directly about it. (Mark,
I'
>Solaris 10 x86
>Python 2.5.2
>Mailman 2.1.9 (8 Incoming queue runners - the leak rate increases with this)
>SpamAssassin 3.2.5
>
>At this point I am looking for ways to isolate the suspected memory leak - I
>am looking at using dtrace: http://blogs.sun.com/sanjeevb/date/200506
>
>Any other tips ap
Dony Tata wrote:
>
>>Did Mailman create a set of entries
>
>>[EMAIL PROTECTED] abc
>>[EMAIL PROTECTED] abc-admin
>...
>Mailman doesn't create that set but Mailman create this set
>[EMAIL PROTECTED]abc-virtual.org
>[EMAIL PROTECTED]abc-virtual.org-admin
>
>in data/virtual-m
An update - I've upgraded to the latest stable python (2.5.2) and its made
no difference to the process growth:
Config:
Solaris 10 x86
Python 2.5.2
Mailman 2.1.9 (8 Incoming queue runners - the leak rate increases with this)
SpamAssassin 3.2.5
At this point I am looking for ways to isolate the su
Mark Dale wrote:
>
>Can anyone shed any light on this error I get when creating a new list
>from the webpage. (I can create lists okay from the "newlist" command)
>
>*** extract from the error log ***
>--
>
>Jul 01 05:27:46 2008 (14663) command failed: /usr/sbin/postmap
From: Doug Laidlaw <[EMAIL PROTECTED]>
... one would think that an OS that wants to rule the world would
be compatible with the most popular mailing list software. Oh,
well...
Wow, you mean Microsoft is going to be compatible with Mailman?
Cool! :-)
Jesus Saves!... Passes to Gre
--On July 1, 2008 4:39:34 PM +1000 Doug Laidlaw <[EMAIL PROTECTED]>
wrote:
On my inquiry, one would think that an OS that wants to rule the world
would be compatible with the most popular mailing list software. Oh,
well...
To which I reply:
There is the source of your confusion. You are u
>Did Mailman create a set of entries
>[EMAIL PROTECTED] abc
>[EMAIL PROTECTED] abc-admin
...
Mailman doesn't create that set but Mailman create this set
[EMAIL PROTECTED]abc-virtual.org
[EMAIL PROTECTED]abc-virtual.org-admin
in data/virtual-mailman and aliases
abc-
34 matches
Mail list logo
