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

From Torsten Zühlsdorff
Subject Re: InitDB: Bad system call
Date
Msg-id 4C60FF42.6020905@meisterderspiele.de
Whole thread Raw
In response to Re: InitDB: Bad system call  (Thom Brown <thom@linux.com>)
List pgsql-general
Hello Thom,

> See http://www.postgresql.org/docs/9.0/static/kernel-resources.html
> and the section under NetBSD/OpenBSD.

I already know the FreeBSD section. My current values are:

kern.ipc.shmall: 131072
kern.ipc.shmmax: 2684225436
kern.ipc.semmap: 4096

kern.ipc.semmnu: 512
kern.ipc.semmns: 1024
kern.ipc.semmni: 512

kern.ipc.shm_use_phys: 0

security.jail.sysvipc_allowed: 1

I also run the user with different UIDs:

$ grep pgsql -h /usr/local/jail/*/*/etc/passwd
pgsql:*:1070:70:PostgreSQL Daemon:/usr/local/pgsql:/bin/sh
pgsql:*:7575:7575:PostgreSQL Daemon:/usr/local/pgsql:/bin/sh
pgsql:*:1074:70:PostgreSQL Daemon:/usr/local/pgsql:/bin/sh
pgsql:*:1071:70:PostgreSQL Daemon:/usr/local/pgsql:/bin/sh

I also rebuild the complete jail to make sure, that it is not an error
while creating the jail.
I also disable all - but one (the live-db ;)) - postgresql instance to
make sure, that enough shared memory is free.
But the "bad system call" messages don't go away. Any other hint?

Greetings,
Torsten


pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: RETURN QUERY SELECT & TYPE
Next
From:
Date:
Subject: pl/pgsql editor and postgres developemnt tool