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

From Torsten Zühlsdorff
Subject Re: InitDB: Bad system call
Date
Msg-id 4C63BEC0.7020709@meisterderspiele.de
Whole thread Raw
In response to Re: InitDB: Bad system call  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: InitDB: Bad system call
List pgsql-general
Hello,

>> Excerpts from Torsten ZÌhlsdorff's message of mié ago 11 02:52:34 -0400 2010:
>>>>> Bad system call (core dumped)
>
>> I think you should try harder to generate the core file.  Maybe you have
>> too low an "ulimit -c" setting?
>
> The kernel message indicates that core *is* being dumped.  Possibly it's
> being dumped in the $PGDATA directory, which initdb will rm -rf on
> failure.  Try using initdb --noclean.

So... yesterday night i was able to change the SyS-IPC Settings and
restart the server. Good bye 216 days uptime :D

After that i recreate the jail from the scratch and compiled PG 9.0 Beta
4 again.  I've compiled PG with:
$ ./configure --enable-debug

InitDB is:
$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data/ --noclean
Running in noclean mode.  Mistakes will not be cleaned up.
The files belonging to this database system will be owned by user "pgsql".
This user must also own the server process.

The database cluster will be initialized with locale en_US.ISO8859-1.
The default database encoding has accordingly been set to LATIN1.
The default text search configuration will be set to "english".

creating directory /usr/local/pgsql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
10
selecting default shared_buffers ... Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
Bad system call
400kB
creating configuration files ... ok
creating template1 database in /usr/local/pgsql/data/base/1 ... Bad
system call
child process exited with exit code 140
initdb: data directory "/usr/local/pgsql/data" not removed at user's request

Result in $PGDATA is:
$ ls -lah /usr/local/pgsql/data/
total 84
drwx------  12 pgsql  pgsql   512B Aug 12 08:56 .
drwx------   6 pgsql  pgsql   512B Aug 12 08:56 ..
-rw-------   1 pgsql  pgsql     4B Aug 12 08:56 PG_VERSION
drwx------   3 pgsql  pgsql   512B Aug 12 08:56 base
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 global
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 pg_clog
-rw-------   1 pgsql  pgsql   3.8K Aug 12 08:56 pg_hba.conf
-rw-------   1 pgsql  pgsql   1.6K Aug 12 08:56 pg_ident.conf
drwx------   4 pgsql  pgsql   512B Aug 12 08:56 pg_multixact
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 pg_notify
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 pg_stat_tmp
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 pg_subtrans
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 pg_tblspc
drwx------   2 pgsql  pgsql   512B Aug 12 08:56 pg_twophase
drwx------   3 pgsql  pgsql   512B Aug 12 08:56 pg_xlog
-rw-------   1 pgsql  pgsql    17K Aug 12 08:56 postgresql.conf
-rw-------   1 pgsql  pgsql    49B Aug 12 08:56 postmaster.pid

Please notice, that after changing the IPC-Settings of the system, no
core-file is dumped anymore. Quiet interessting.

Greetings,
Torsten

pgsql-general by date:

Previous
From: Torsten Zühlsdorff
Date:
Subject: Re: InitDB: Bad system call
Next
From: Mike Christensen
Date:
Subject: Re: Converting join'ed rows into a comma or space delimited list