Hello everyone,
I am observing increased CPU(%) usage whenever a Mailman User Service
runs. The journal tells me that SELinux is preventing httpd from map
access on the
file /var/lib/mailman/archives/private///.html. A
setroubleshoot service follows. This cycle repeats quickly, resulting
in a
On Sun, Feb 15, 2004 at 10:34:16PM -0500, Jon Carnes wrote:
So ArchRunner is the one... not too surprising. And the other Qrunners
are all behaving themselves?
The rest are fine for CPU usage.
You should upgrade to the latest version of Mailman, it does fix some
problems with the
So ArchRunner is the one... not too surprising. And the other Qrunners
are all behaving themselves?
# ps aux |grep python
/usr/bin/python ./mailmanctl start
/usr/bin/python /var/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
/usr/bin/python /var/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
I have scoured the archives and google for answer to my problem but
none of the fixes I have found seem to work. I have mailman 2-1.1-91
installed w/ postfix 1.1.12-12 on a Suse 8.2 box and qrunner/python is
eating the cpu. Most of the posts I read describe this as a postfix
problem and to
There are a lot of items that can cause this.
- Using top look at the qrunners process ID's and see which ones are
eating the most cpu time.
- Now use ps aux on a *wide* terminal so you can see which qrunner is
associated with the high cpu process ID
Each of the qrunners is launched with its
Thanks for the reply:
On Sat, Feb 14, 2004 at 08:34:07PM -0500, Jon Carnes wrote:
Each of the qrunners is launched with its specific job:
The qrunner which is using 98% of CPU is ArchRunner.
What is your Qrunner_Sleep_Time set to in ~mailman/Mailman/mm_cfg.py (or
Defaults.py)? The default of
I have scoured the archives and google for answer to my problem but none
of the fixes I have found seem to work. I have mailman 2-1.1-91
installed w/ postfix 1.1.12-12 on a Suse 8.2 box and qrunner/python is
eating the cpu. Most of the posts I read describe this as a postfix
problem and to
Hello,
Perhaps somebody can explain me why I have a task (mailman) to eat all of
my CPU:
60 processes: 56 sleeping, 4 running, 0 zombie, 0 stopped
CPU states: 5.1% user, 94.8% system, 0.0% nice, 0.0% idle
Mem: 259688K av, 154984K used, 104704K free, 0K shrd, 90484K
buff
Swap:
I have experienced the same problem recently (v2.0.6), and ended
up
having to disable the Mailman web interface as Python2.1 procs were taking
down my
machine (a mere P75 w/16MB or ram, which may account for the problem).
Unless I killed the processes immediately, all daemons would
