Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed) - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)
Date
Msg-id Pine.BSF.4.05.9901282130500.3436-100000@thelab.hub.org
Whole thread Raw
In response to Postmaster dies with many child processes (spinlock/semget failed)  (Patrick Verdon <patrick@kan.co.uk>)
List pgsql-hackers
On Thu, 28 Jan 1999, Patrick Verdon wrote:

> IpcSemaphoreCreate: semget failed (No space left on device) key=5432017, num=16, permission=600
> NOTICE:  Message from PostgreSQL backend:
>         The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory.
>         I have rolled back the current transaction and am going to terminate your database system connection and
exit.
>         Please reconnect to the database system and repeat your query.
> 
> FATAL: s_lock(28001065) at spin.c:125, stuck spinlock. Aborting.
> 
> Note that the 'no space left on device' is
> misleading as there is a minimum of 400 MB 
> available on each file-system on the server.

My first guess is that you don't have enough semaphores enabled in your
kernel...increase that from the default, and I'm *guessing* that you'll
get past your 48...

Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)
Next
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)