Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error - Aack,_child_crashed._(#4.3.0)

32 views
Skip to first unread message

Srdan Dukic

unread,
Feb 7, 2010, 6:00:04 PM2/7/10
to
Hi,

I've recently started seeing the following error in the qmail logs:

delivery 13230: deferral: _/_/_/_//////Aack,_child_crashed._(#4.3.0)/

From my understanding this occurs when qmail delivers to a .qmail file
that specifies a pipe to another program and when this program
crashes, it is reported as a child crashing.

My problem is that there are several programs which are getting piped
to and isolating which of these programs is crashing is proving to be
rather difficult. Does anyone have any tips/tricks which might help to
track down exactly which program is crashing? Also, if I'm wrong in my
assumptions about this message only appearing when output is piped to
a child process through a .qmail file, please tell me.


Thank you
--
Srđan Đukić

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

Srdan Dukic

unread,
Feb 7, 2010, 8:42:47 PM2/7/10
to
On 8 February 2010 12:00, Srdan Dukic <srdan...@gmail.com> wrote:
> Hi,
>
> I've recently started seeing the following error in the qmail logs:
>
> delivery 13230: deferral: _/_/_/_//////Aack,_child_crashed._(#4.3.0)/
>
> From my understanding this occurs when qmail delivers to a .qmail file
> that specifies a pipe to another program and when this program
> crashes, it is reported as a child crashing.
>
> My problem is that there are several programs which are getting piped
> to and isolating which of these programs is crashing is proving to be
> rather difficult. Does anyone have any tips/tricks which might help to
> track down exactly which program is crashing? Also, if I'm wrong in my
> assumptions about this message only appearing when output is piped to
> a child process through a .qmail file, please tell me.
>
>
> Thank you
> --
> Srđan Đukić
>

Hi,

I've just figured out which program is causing the problems by tailing
the 'messages' log. It turned out that the program was segfaulting
causing a kernel error.

0 new messages