pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Shared memory error using initdb on Solaris 8
5+ messages / 2 participants
[nested] [flat]

* Shared memory error using initdb on Solaris 8
@ 2004-05-21 15:15  Kevin Schroeder <kschroeder@mirageworks.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Kevin Schroeder @ 2004-05-21 15:15 UTC (permalink / raw)
  To: pgsql-admin

Hello,
    I'm trying to install PostgreSQL 7.4.2 on a brand new SunFire 120 with
2GB of RAM but when I run initdb -D /usr/local/pgsql/data I get the
following error:

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
selecting default max_connections... 10
selecting default shared_buffers... 50
creating configuration files... ok
creating template1 database in /usr/local/pgsql/data/base/1... FATAL:  could
not create shared memory segment: Invalid argument
DETAIL:  Failed system call was shmget(key=1, size=1081344, 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 1081344 bytes), reduce PostgreSQL's
shared_buffers parameter (currently 50) and/or its max_connections parameter
(currently 10).
        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.

initdb: failed
initdb: removing data directory "/usr/local/pgsql/data"

When I run ulimit -a I get

time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     0
nofiles(descriptors) 256
vmemory(kbytes)      unlimited

There does not seem to be an option in initdb to reduce the shared buffers
size.  Plus, with 2GB of RAM I don't know that I'd want to go below the
"lowest common denominator" that Postgres defaults to.

Kevin




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Shared memory error using initdb on Solaris 8
@ 2004-05-21 15:57  Jim Seymour <jseymour@LinxNet.com>
  0 siblings, 1 reply; 5+ messages in thread

From: jseymour@LinxNet.com @ 2004-05-21 15:57 UTC (permalink / raw)
  To: pgsql-admin

> 
> Hello,
>     I'm trying to install PostgreSQL 7.4.2 on a brand new SunFire 120 with
> 2GB of RAM but when I run initdb -D /usr/local/pgsql/data I get the
> following error:
> 
[snip]
> creating template1 database in /usr/local/pgsql/data/base/1... FATAL:  could
> not create shared memory segment: Invalid argument
> DETAIL:  Failed system call was shmget(key=1, size=1081344, 03600).
> HINT:  This error usually means that PostgreSQL's request for a shared
> memory segment exceeded your kernel's SHMMAX parameter.
[snip]
> 
> When I run ulimit -a I get
> 
[snip]

You're looking at the wrong thing.  You need to do:

    sysdef |egrep -i 'shm|sem'

> 
> There does not seem to be an option in initdb to reduce the shared buffers
> size.

It tries to reduce things as far as it "sanely" can to fit within
what's available.  You can hand-tweak initdb to over-ride its
limits, but you'd end-up with a sub-optimal installation.

>        Plus, with 2GB of RAM I don't know that I'd want to go below the
> "lowest common denominator" that Postgres defaults to.

Nope.  You need to adjust certain values by placing settings in
/etc/system and rebooting.  I use:

    /etc/system
        set shmsys:shminfo_shmmax=0x2000000  (33554432 decimal)
        set shmsys:shminfo_shmmin=1
        set shmsys:shminfo_shmmni=256
        set shmsys:shminfo_shmseg=256
         
        set semsys:seminfo_semmap=256
        set semsys:seminfo_semmni=512
        set semsys:seminfo_semmns=512
        set semsys:seminfo_semmsl=32

I arrived at the above values from Google'ing.

Jim



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Shared memory error using initdb on Solaris 8
@ 2004-05-21 17:01  Kevin Schroeder <kschroeder@mirageworks.com>
  parent: Jim Seymour <jseymour@LinxNet.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Kevin Schroeder @ 2004-05-21 17:01 UTC (permalink / raw)
  To: pgsql-admin

There we go.  For reference, what page did you get that info and what did
you search for to get it?

Kevin

----- Original Message ----- 
From: "Jim Seymour" <jseymour@LinxNet.com>
To: <pgsql-admin@postgresql.org>
Sent: Friday, May 21, 2004 10:57 AM
Subject: Re: [ADMIN] Shared memory error using initdb on Solaris 8


> >
> > Hello,
> >     I'm trying to install PostgreSQL 7.4.2 on a brand new SunFire 120
with
> > 2GB of RAM but when I run initdb -D /usr/local/pgsql/data I get the
> > following error:
> >
> [snip]
> > creating template1 database in /usr/local/pgsql/data/base/1... FATAL:
could
> > not create shared memory segment: Invalid argument
> > DETAIL:  Failed system call was shmget(key=1, size=1081344, 03600).
> > HINT:  This error usually means that PostgreSQL's request for a shared
> > memory segment exceeded your kernel's SHMMAX parameter.
> [snip]
> >
> > When I run ulimit -a I get
> >
> [snip]
>
> You're looking at the wrong thing.  You need to do:
>
>     sysdef |egrep -i 'shm|sem'
>
> >
> > There does not seem to be an option in initdb to reduce the shared
buffers
> > size.
>
> It tries to reduce things as far as it "sanely" can to fit within
> what's available.  You can hand-tweak initdb to over-ride its
> limits, but you'd end-up with a sub-optimal installation.
>
> >        Plus, with 2GB of RAM I don't know that I'd want to go below the
> > "lowest common denominator" that Postgres defaults to.
>
> Nope.  You need to adjust certain values by placing settings in
> /etc/system and rebooting.  I use:
>
>     /etc/system
>         set shmsys:shminfo_shmmax=0x2000000  (33554432 decimal)
>         set shmsys:shminfo_shmmin=1
>         set shmsys:shminfo_shmmni=256
>         set shmsys:shminfo_shmseg=256
>
>         set semsys:seminfo_semmap=256
>         set semsys:seminfo_semmni=512
>         set semsys:seminfo_semmns=512
>         set semsys:seminfo_semmsl=32
>
> I arrived at the above values from Google'ing.
>
> Jim
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Shared memory error using initdb on Solaris 8
@ 2004-05-21 18:14  Jim Seymour <jseymour@LinxNet.com>
  0 siblings, 1 reply; 5+ messages in thread

From: jseymour@LinxNet.com @ 2004-05-21 18:14 UTC (permalink / raw)
  To: pgsql-admin

> 
> There we go.  For reference, what page did you get that info and what did
> you search for to get it?

Like I said: I derived it all from Google'ing on various search
terms, IIRC.  Probably things like "postgresql+Solaris+shmmax" and
the like.  I didn't save any URL references.

Jim



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Shared memory error using initdb on Solaris 8
@ 2004-05-21 18:37  Kevin Schroeder <kschroeder@mirageworks.com>
  parent: Jim Seymour <jseymour@LinxNet.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Kevin Schroeder @ 2004-05-21 18:37 UTC (permalink / raw)
  To: pgsql-admin

Searching Google brought up this page.

http://www.postgresql.org/docs/current/interactive/kernel-resources.html



----- Original Message ----- 
From: "Jim Seymour" <jseymour@LinxNet.com>
To: <pgsql-admin@postgresql.org>
Sent: Friday, May 21, 2004 1:14 PM
Subject: Re: [ADMIN] Shared memory error using initdb on Solaris 8


> >
> > There we go.  For reference, what page did you get that info and what
did
> > you search for to get it?
>
> Like I said: I derived it all from Google'ing on various search
> terms, IIRC.  Probably things like "postgresql+Solaris+shmmax" and
> the like.  I didn't save any URL references.
>
> Jim
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend




^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2004-05-21 18:37 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-05-21 15:15 Shared memory error using initdb on Solaris 8 Kevin Schroeder <kschroeder@mirageworks.com>
2004-05-21 15:57 Re: Shared memory error using initdb on Solaris 8 Jim Seymour <jseymour@LinxNet.com>
2004-05-21 17:01 ` Kevin Schroeder <kschroeder@mirageworks.com>
2004-05-21 18:14 Re: Shared memory error using initdb on Solaris 8 Jim Seymour <jseymour@LinxNet.com>
2004-05-21 18:37 ` Kevin Schroeder <kschroeder@mirageworks.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox