qmail-rspawn problem

Hi,
I have posted a similar problem a while back under subject
"qmail-rspawn taking 99% cpu" this is happening only on one of the
machines with a very light load (about 7000 mail/day). I was able to
capture the following when the problem starts:
/var/qmail #> ptree 6339
318 /bin/sh /command/svscanboot
321 readproctitle service errors:
..........................................
322 svscan /service
323 supervise qmail-send
6334 qmail-send
6339 qmail-rspawn
15467 <defunct>
15455 <defunct>
15449 <defunct>
15506 <defunct>
15451 <defunct>
15416 <defunct>
15471 <defunct>
15458 <defunct>
15459 <defunct>
15456 <defunct>
15454 <defunct>
15474 <defunct>
15469 <defunct>
15466 <defunct>
15461 <defunct>
15448 <defunct>
15463 <defunct>
15452 <defunct>
15475 <defunct>
15465 <defunct>
15464 <defunct>
15457 <defunct>
15504 <defunct>
15468 <defunct>
15476 <defunct>
15453 <defunct>
15495 <defunct>
15446 <defunct>
15460 <defunct>
15462 <defunct>
15472 <defunct>
15450 <defunct>
15445 <defunct>
15470 <defunct>
/var/log/qmail #>
I do not really want to reinstall qmail without knowing what the
problem is. Please let me know if this is a familiar problem. In the
above situation, no log is written to current.
Thanks.
Vahid.

Vahid moghaddasi wrote:

> Hi,
> I have posted a similar problem a while back under subject
> "qmail-rspawn taking 99% cpu" this is happening only on one of the
> machines with a very light load (about 7000 mail/day). I was able to
> capture the following when the problem starts:
> /var/qmail #> ptree 6339
> 318 /bin/sh /command/svscanboot
> 321 readproctitle service errors:
> .........................................
> 322 svscan /service
> 323 supervise qmail-send
> 6334 qmail-send
> 6339 qmail-rspawn
> 15467 <defunct>
> 15455 <defunct>
> 15449 <defunct>
> 15506 <defunct>
> 15451 <defunct>
> 15416 <defunct>
> 15471 <defunct>
> 15458 <defunct>
> 15459 <defunct>
> 15456 <defunct>
> 15454 <defunct>
> 15474 <defunct>
> 15469 <defunct>
> 15466 <defunct>
> 15461 <defunct>
> 15448 <defunct>
> 15463 <defunct>
> 15452 <defunct>
> 15475 <defunct>
> 15465 <defunct>
> 15464 <defunct>
> 15457 <defunct>
> 15504 <defunct>
> 15468 <defunct>
> 15476 <defunct>
> 15453 <defunct>
> 15495 <defunct>
> 15446 <defunct>
> 15460 <defunct>
> 15462 <defunct>
> 15472 <defunct>
> 15450 <defunct>
> 15445 <defunct>
> 15470 <defunct>
> /var/log/qmail #>
> I do not really want to reinstall qmail without knowing what the
> problem is. Please let me know if this is a familiar problem. In the
> above situation, no log is written to current.
> Thanks.
> Vahid.
>

Vahid,

It is unclear what caused so many spawned processes to die out.

You need to determine what leads to this condition. Obtaining
information after the fact might not provide an answer.

AK

AK wrote:

> Vahid,
>
> It is unclear what caused so many spawned processes to die out.
>
> You need to determine what leads to this condition. Obtaining
> information after the fact might not provide an answer.
>
Yes, unfortunately I do not know when this happens or what causes this
to happen, we just get alert that queue is over 5k.
I guess I will have to re-install qmail but I was very interested to
know what is in qmail-rspawn's mind.
Thanks AK.

Vahid Moghaddasi wrote:

> AK wrote:
>
>
>>Vahid,
>>
>>It is unclear what caused so many spawned processes to die out.
>>
>>You need to determine what leads to this condition. Obtaining
>>information after the fact might not provide an answer.
>>
>
> Yes, unfortunately I do not know when this happens or what causes this
> to happen, we just get alert that queue is over 5k.
> I guess I will have to re-install qmail but I was very interested to
> know what is in qmail-rspawn's mind.
> Thanks AK.
>

What patches have you applied to the qmail install? What system is it
running on? How many concurrent incoming connections do you allow?

AK