Re: InitDB: Bad system call

Excerpts from Torsten Zühlsdorff's message of mié ago 11 02:52:34 -0400 2010:
> Hi Tom,
>
> >>> Bad system call (core dumped)
> >
> >> Have you tried running the initdb with strace or truss? That might give
> >> you a clue as to exactly what system call is failing. Your jail isn't
> >> allowing something fundamental here, but it's hard to guess what.
> >
> > Or even easier, gdb the core file ...
>
> As written early i can't locate the core file. But now i use truss:
> $ truss -o /tmp/pg.truss /usr/local/bin/initdb /usr/local/pgsql/

This isn't as helpful because you're tracing the initdb process. The
core file would give a backtrace of the postgres process, which is what
is actually crashing.

> The first suspicious i can see are a lots of "ERR#32 'Broken pipe'" entries.

This is the result of postgres crashing and thus initdb being unable to
write any more data to it.

I think you should try harder to generate the core file. Maybe you have
too low an "ulimit -c" setting?

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support