Re: Postfix+Cyrus-SASL2+Courier-IMAP+MySQL - smtpd pid .... killed by signal 10

[Bummibaer <Bummibaerchen@xxxxxxxxxxxxxxxxxx>]

Victor Duchovni wrote:

> On Wed, Sep 01, 2004 at 05:01:17AM +0200, Bummibaer wrote:
>
> > >     http://www.postfix.org/DEBUG_README.html
> > >
> >
> > kill -l output:
> > HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP
>
> Program died with SIGBUS, this is usually a pointer alignment error. What
> is the hardware? What are the alignment requirements?
>
> > km1601# truss -p 50373>/var/log/truss_postfix
>
> This is useless without "-f" to follow children. What you want is:
>
> I did not know BSD had "truss". On Solaris, truss can suspend
> a process exactly when a signal is delivered
>
>     # truss -f -t '!all' -m '!all' -s'SIGBUS' -SSIGBUS -p 50373
>
> This will trace all subprocesses (of master) and stop any process
> when SIGBUG is delivered. You can then find it with 'ps' and
> use "gcore" to get a core file. Then use a debugger to report
> a stack trace.
>

# truss -f -t '!all' -m '!all' -s'SIGBUS' -SSIGBUS -p <PID> doesn´t work on the
BSD Box.
Result is "all: Event not found."

But i could do a ktrace -idg witch did a trace of all kernel operations of
processes in process group and pass the trace flags to all current and future
children
Result after kdump is on http://www.mktech.de/ktrace.txt

>
> > Any pointers to solving this, or even a place too look for the solution.
> > Thanks.
> >
>
> Otherwise read the instructions for using "-D" and debugger_command
> in the documented referenced at the top of this message.
>
> --
>         Viktor.
>
> Disclaimer: off-list followups get on-list replies or get ignored.
> Please do not ignore the "Reply-To" header.
>
> To unsubscribe from the postfix-users list, visit
> http://www.postfix.org/lists.html or click the link below:
> <mailto:majordomo@xxxxxxxxxxx?body=unsubscribe%20postfix-users>

Tomorror i can test debugger_command.

Thanks.

Bummibaer