Skip site navigation (1) Skip section navigation (2)

Re: icps, shmmax and shmall - Shared Memory tuning

From: dorian dorian <dorian37076(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: icps, shmmax and shmall - Shared Memory tuning
Date: 2002-04-28 15:44:44
Message-ID: 20020428154444.73445.qmail@web14808.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-general
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> dorian dorian <dorian37076(at)yahoo(dot)com> writes:
> > Apr 26 09:43:16 mito logger: IpcMemoryCreate:
> > shmget(key=5432001, size=137175040, 03600) failed:
> Invalid argument
> 
> > ------ Shared Memory Segments --------
> > key       shmid     owner     perms     bytes    
> > nattch    status      
> > 0x0052e2c1 98307     postgres  600       137175040
> 28 
> 
> This is very strange.  [...]  There's
> some kind of bug here.  Are you up for tracing
> through IpcMemoryCreate
> with a debugger to see what's going wrong?

Will this involve any kind of downtime for the server?
I'm more than willing to help as long as it doesn't
take the box or postgres down again while testing.

> If you just want to get going again, you can remove
> that segment with
> ipcrm (I think "ipcrm shm 98307" is the syntax to
> use on Linux) and
> then the postmaster should start.

This was also in the logs -

Apr 26 09:34:16 mito logger: DEBUG:  server process
(pid 21540) was terminated by signal 9
Apr 26 09:34:16 mito logger: DEBUG:  terminating any
other active server processes
Apr 26 09:34:16 mito logger: NOTICE:  Message from
PostgreSQL backend:
Apr 26 09:34:16 mito logger: ^IThe Postmaster has
informed me that some other backend
Apr 26 09:34:16 mito logger: ^Idied abnormally and
possibly corrupted shared memory.
Apr 26 09:34:16 mito logger: ^II have rolled back the
current transaction and am 
Apr 26 09:34:16 mito logger: ^Igoing to terminate your
database system connection and exit.
Apr 26 09:34:16 mito logger: ^IPlease reconnect to the
database system and repeat your query.
Apr 26 09:34:16 mito logger: NOTICE:  Message from
PostgreSQL backend:
Apr 26 09:34:16 mito logger: ^IThe Postmaster has
informed me that some other backend
Apr 26 09:34:16 mito logger: ^Idied abnormally and
possibly corrupted shared memory.
Apr 26 09:34:16 mito logger: ^II have rolled back the
current transaction and am 
Apr 26 09:34:17 mito kernel: Out of Memory: Killed
process 21540 (postmaster).

The machine just stopped responding at 9:34 and had to
be rebooted. Is there any way to prevent this from
happening, via a configuration option in postgres?

Thanks very much for all your help!

-d


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

In response to

Responses

pgsql-general by date

Next:From: Justin CliftDate: 2002-04-28 16:32:29
Subject: Re: Compiling 7.2 on Solaris 8: runtime error on
Previous:From: Tom LaneDate: 2002-04-28 14:58:52
Subject: Re: How to track down inconsistent performance?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group