[Mailman-Users] Summary, whats next?

[Joern Nettingsmeier]

hi danny.

i have no idea what's wrong, and i don't know python, but if such
things happen to me, i try strace.
my suggestion is disable the mailman cronjobs, invoke qrunner by
hand under strace (strace <command>) and see if it hangs or loops
somewhere. it will spew out a lot of garbage, but in some cases,
there are useful hints for mere mortals in it.

just a guess,

jörn


Danny Terweij wrote:
> 
> 
> top not running qrunner:
>   2:19am  up  4:21,  1 user,  load average: 1.17, 1.54, 1.58
> 66 processes: 65 sleeping, 1 running, 0 zombie, 0 stopped
> CPU states:  1.9% user,  2.3% system,  0.0% nice, 95.7% idle
> Mem:    94124K av,   44044K used,   50080K free,       4K shrd,    2760K
> buff
> Swap:  192772K av,   31316K used,  161456K free                   23684K
> cached
> 
> top running qrunner:
>   2:23am  up  4:25,  1 user,  load average: 1.46, 1.58, 1.58
> 68 processes: 65 sleeping, 3 running, 0 zombie, 0 stopped
> CPU states: 97.5% user,  2.4% system,  0.0% nice,  0.0% idle
> Mem:    94124K av,   63608K used,   30516K free,       4K shrd,    4384K
> buff
> Swap:  192772K av,   31252K used,  161520K free                   33332K
> cached
> 
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>  8288 mailman   14   0  8388 8388  1388 R    92.7  8.9   1:56 python
> 

--
Watch out where the huskies go and don't you eat
the yellow snow !
	- Frank Zappa