Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Patrick Verdon <patrick(at)kan(dot)co(dot)uk>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)
Date: 1999-01-29 01:31:58
Message-ID: Pine.BSF.4.05.9901282130500.3436-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 1999-01-29 03:06:24 Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)
Previous Message Tatsuo Ishii 1999-01-29 01:10:28 Re: [HACKERS] Postmaster dies with many child processes (spinlock/semget failed)