Re: InitDB: Bad system call - Mailing list pgsql-general

From Greg Smith
Subject Re: InitDB: Bad system call
Date
Msg-id 4C620BD5.7030702@2ndquadrant.com
Whole thread Raw
In response to InitDB: Bad system call  (Torsten Zühlsdorff <foo@meisterderspiele.de>)
Responses Re: InitDB: Bad system call
List pgsql-general
Torsten Zühlsdorff wrote:
> selecting default max_connections ... Bad system call (core dumped)
> Bad system call (core dumped)
> Bad system call (core dumped)
> Bad system call (core dumped)
> Bad system call (core dumped)
> Bad system call (core dumped)
> 10
> selecting default shared_buffers ... Bad system call (core dumped)
> Bad system call (core dumped) ...

What it's doing in this part is trying to start the server process in a
special testing mode, starting with large values for the settings that
impact shared memory, then stepping down the sizes until that works.
That's why there are so many of these.  But it looks like none of them
actually work.

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.

--
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us


pgsql-general by date:

Previous
From: Greg Smith
Date:
Subject: Re: MySQL versus Postgres
Next
From: Tom Lane
Date:
Subject: Re: InitDB: Bad system call