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

Spinlock error

From: "Jeff MacDonald <jeff(at)pgsql(dot)com>" <jeffm(at)pgsql(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Spinlock error
Date: 2000-01-27 18:43:22
Message-ID: Pine.BSF.4.10.10001271436530.380-100000@rage.hub.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi folks,

I got a problem with a production database, it's a little
busy with 2 to 5 queries per second. 

Running on Redhat 6.0, 2.2.5-15 SMP (intel)

Currently thre are 128 backends ( postmaster -N 128 )
with share mem set at 256.

in pg_options verbose = 2, syslog = 2,

here are the errors..

FATAL: s_lock(4001404d) at spin.c:125, stuck spinlock. Aborting.

After those spinlock errors the postmaster died.... I tries to start it
back up and it failed with this error.

FindExec: found "/usr/bin/postgres" using argv[0]
IpcMemoryCreate: shmget failed (Identifier removed) key=5432010,
size=120, permission=700
IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010, size=120,
permission=0
IpcMemoryAttach: shmat failed (Invalid argument) id=-2
FATAL 1:  AttachSLockMemory: could not attach segment
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)


Since this is a production database, what are teh first steps i should
take ?



======================================================
Jeff MacDonald
	jeff(at)pgsql(dot)com	irc: bignose on EFnet
======================================================


Responses

pgsql-hackers by date

Next:From: Ross J. ReedstromDate: 2000-01-27 18:55:44
Subject: Re: [HACKERS] Column ADDing issues
Previous:From: Tom LaneDate: 2000-01-27 18:33:16
Subject: Re: [SQL] DISTINCT ON: speak now or forever hold your peace

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