Thread: could not create shared memory segment: Invalid argument

could not create shared memory segment: Invalid argument

From
beyaNet Consultancy
Date:
Hi,
I have just installed the latest version of OS X panther (10.3.3) and 
am now getting the following error message:

postgres$ /usr/local/pgsql/bin/postmaster -i -D /usr/local/pgsql/data
FATAL:  could not create shared memory segment: Invalid argument
DETAIL:  Failed system call was shmget(key=5432001, size=10444800, 
03600).
HINT:  This error usually means that PostgreSQL's request for a shared 
memory segment exceeded your kernel's SHMMAX parameter.  You can either 
reduce the request size or reconfigure the kernel with larger SHMMAX.  
To reduce the request size (currently 10444800 bytes), reduce 
PostgreSQL's shared_buffers parameter (currently 1000) and/or its 
max_connections parameter (currently 100).        If the request size is already small, it's possible that it is 
less than your kernel's SHMMIN parameter, in which case raising the 
request size or reconfiguring SHMMIN is called for.        The PostgreSQL documentation contains more information about

shared memory configuration.

Any ideas on how i can resolve this issue?

many thanks in advance



Re: could not create shared memory segment: Invalid argument

From
Achilleus Mantzios
Date:
O kyrios beyaNet Consultancy egrapse stis Mar 16, 2004 :

> Hi,
> I have just installed the latest version of OS X panther (10.3.3) and 
> am now getting the following error message:

For start do:

sysctl -a | grep -i shm
or equivalent to find out your current kernel settings.

in FreeBSD the way to change shmmax is

# sysctl sysctl kern.ipc.shmmax=<some size>

I dont know about OSX tho..

> 
> postgres$ /usr/local/pgsql/bin/postmaster -i -D /usr/local/pgsql/data
> FATAL:  could not create shared memory segment: Invalid argument
> DETAIL:  Failed system call was shmget(key=5432001, size=10444800, 
> 03600).
> HINT:  This error usually means that PostgreSQL's request for a shared 
> memory segment exceeded your kernel's SHMMAX parameter.  You can either 
> reduce the request size or reconfigure the kernel with larger SHMMAX.  
> To reduce the request size (currently 10444800 bytes), reduce 
> PostgreSQL's shared_buffers parameter (currently 1000) and/or its 
> max_connections parameter (currently 100).
>          If the request size is already small, it's possible that it is 
> less than your kernel's SHMMIN parameter, in which case raising the 
> request size or reconfiguring SHMMIN is called for.
>          The PostgreSQL documentation contains more information about 
> shared memory configuration.
> 
> Any ideas on how i can resolve this issue?
> 
> many thanks in advance
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 

-- 
-Achilleus



Re: could not create shared memory segment: Invalid argument

From
Dana Hudes
Date:
Well, did you consider getting the value of SHMMAX?
Check with ulimit  (as the postgres user).

On Tue, 16 Mar 2004, beyaNet Consultancy wrote:

> Hi,
> I have just installed the latest version of OS X panther (10.3.3) and 
> am now getting the following error message:
> 
> postgres$ /usr/local/pgsql/bin/postmaster -i -D /usr/local/pgsql/data
> FATAL:  could not create shared memory segment: Invalid argument
> DETAIL:  Failed system call was shmget(key=5432001, size=10444800, 
> 03600).
> HINT:  This error usually means that PostgreSQL's request for a shared 
> memory segment exceeded your kernel's SHMMAX parameter.  You can either 
> reduce the request size or reconfigure the kernel with larger SHMMAX.  
> To reduce the request size (currently 10444800 bytes), reduce 
> PostgreSQL's shared_buffers parameter (currently 1000) and/or its 
> max_connections parameter (currently 100).
>          If the request size is already small, it's possible that it is 
> less than your kernel's SHMMIN parameter, in which case raising the 
> request size or reconfiguring SHMMIN is called for.
>          The PostgreSQL documentation contains more information about 
> shared memory configuration.
> 
> Any ideas on how i can resolve this issue?
> 
> many thanks in advance
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 


Re: could not create shared memory segment: Invalid argument

From
xvx
Date:
I'am also getting this same problem with 10.3.3 Server.  Worked fine
with 10.3.2.


kern.sysv.shmmax: 4194304
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 1024

Those are the Values i get from the command posted.  Have you figured
out a fix for this error?

Thanks.



beyaNet Consultancy wrote:
> *Hi,
> I have just installed the latest version of OS X panther (10.3.3)
> and
> am now getting the following error message:
> 
> postgres$ /usr/local/pgsql/bin/postmaster -i -D
> /usr/local/pgsql/data
> FATAL:  could not create shared memory segment: Invalid argument
> DETAIL:  Failed system call was shmget(key=5432001, size=10444800,
> 03600).
> HINT:  This error usually means that PostgreSQL's request for a
> shared
> memory segment exceeded your kernel's SHMMAX parameter.  You can
> either
> reduce the request size or reconfigure the kernel with larger
> SHMMAX.
> To reduce the request size (currently 10444800 bytes), reduce
> PostgreSQL's shared_buffers parameter (currently 1000) and/or its
> max_connections parameter (currently 100).
> If the request size is already small, it's possible that it is
> less than your kernel's SHMMIN parameter, in which case raising the
> request size or reconfiguring SHMMIN is called for.
> The PostgreSQL documentation contains more information about
> shared memory configuration.
> 
> Any ideas on how i can resolve this issue?
> 
> many thanks in advance
> 
> 
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster *



--
xvx
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message151918.html