> Wietse Venema wrote:
> You might want to repeat your precise Postfix version at this point,
> and which queue manager version is configured in your master.cf.
> Current Postfix versions have (qmgr=new, oqmgr=old) in master.cf.
> Older Postfix versions have (nqmgr=new, qmgr=old) instead. The
> programs are the same except for the job selection algorithm.
r...@egeo:~# postconf mail_version
mail_version = 2.5.1
r...@egeo:~# grep -i qmgr /etc/postfix/master.cf
qmgr fifo n - n 300 1 qmgr
#qmgr fifo n - - 300 1 oqmgr
> If you are using the new queue manager, it is worthwhile to see if
> the problem persists when you switch to the old queue manager.
It seems I'm using the new one...
> OK, leave the above settings and see if this helps
> (Postfix 2.5 or later).
>
> I have not been able to reproduce the problem, but there was
> some bogosity with the handling of _destination_rate_delay.
>
>
> diff --exclude=man --exclude=html --exclude=README_FILES
> --exclude=.indent.pro --exclude=Makefile.in -cr
> src/qmgr/qmgr_entry.c- src/qmgr/qmgr_entry.c
Well, I'm using postfix's ubuntu package, so it's not compiled from
source code because I need all my ~=100 Linux machines to be easily
updatable (apt-get update && apt-get upgrade).
In this case, I'm going to recompile .deb source package including your
patch to see if that solves the problem ...
Please, allow me a couple of days to recompile / install it (it's a
production system, I need to find a working window with customers). I'll
inform you in this list if the problem happens again or if the patch
seemed to fix the problem. Do you want any kind of aditional change /
logging / config to make the "problem" more easy to happen?
(I mean, setting rate_ values higher or lower so that the problem
reproduces again faster, because it passed 5 days between the last 2
times qmgr ate the CPU...).
Thanks.
--
Santiago Romero
