Re: PostgreSQL7 port fails when I try to run initdb

Based on the additional information you got in your capture, I added
the following options to my kernel:

options		SHMMAXPGS=65536
options		SEMMNI=40
options		SEMMNS=240
options		SEMUME=40
options		SEMMNU=120

and rebuilt it.  initdb then ran successfully, and Postgre was able
to start from the rc script.

I got this information from the PostgreSQL docs.  It's supposed to be
adding _more_ shared memory to allow Postgre to handle up to 180 clients.
I wasn't sure if these options were still valid in 5, as I didn't see
them in the docs anywhere (correct me if I'm wrong, but NOTES has replaced
LINT, right?)
Anyway, the kernel compiled without incident and booted without trouble.
In 4, there was no need to change the defaults just to get Postgre running.
I can only assume that the defaults have changed in 5.  This should probably
be documented somewhere (in the GENERIC file?) or the default values raised
back to where they were in 4?

Thanks Roger.

Roger wrote:
> Agreed Bill I have the same problem:
> 
> %uname -a
> FreeBSD freebee.henocoffice.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Apr 30 
> 0
> 9:27:22 EDT 2003     
> root_at_freebee.henocoffice.com:/usr/obj/.amd_mnt/haydn/host/u
> sr/srcC/src/sys/GENERIC  i386
> %initdb
> 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 C.
> 
> creating directory /usr/local/pgsql/data... ok
> creating directory /usr/local/pgsql/data/base... ok
> creating directory /usr/local/pgsql/data/global... ok
> creating directory /usr/local/pgsql/data/pg_xlog... ok
> creating directory /usr/local/pgsql/data/pg_clog... ok
> creating template1 database in /usr/local/pgsql/data/base/1... 
> IpcSemaphoreCreat
> e: semget(key=1, num=17, 03600) failed: No space left on device
> 
> This error does *not* mean that you have run out of disk space.
> 
> It occurs when either the system limit for the maximum number of
> semaphore sets (SEMMNI), or the system wide maximum number of
> semaphores (SEMMNS), would be exceeded.  You need to raise the
> respective kernel parameter.  Alternatively, reduce PostgreSQL's
> consumption of semaphores by reducing its max_connections parameter
> (currently 1).
> 
> The PostgreSQL Administrator's Guide contains more information about
> configuring your system for PostgreSQL.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com