Re: Running two postmasters on one host: could not create semaphores

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Edwin New <edwin_new(at)toll(dot)com(dot)au>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Running two postmasters on one host: could not create semaphores
Date: 2004-06-25 04:53:43
Message-ID: 2070.1088139223@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Edwin New <edwin_new(at)toll(dot)com(dot)au> writes:
> I get the error:

> FATAL: could not create semaphores: No space left on device
> DETAIL: Failed system call was semget(6100001, 17, 03600).
> HINT: This error does *not* mean that you have run out of disk
> space.
> It occurs when either the system limit for the maximum
> number of semaphore sets (SEMMNI),
> Or the system wide maximum number of semaphores (SEMMNS), would be
> exceeded. You need to raise
> The respective kernel parameter. Alternatively, reduce PostgreSQL's
> consumption of semaphores
> By reducing its max_connections parameter (currently 40).
> The PostgreSQL documentation contains more information about
> configuring your system for PostgreSQL.

> Is it a shortage of semaphores, or a competition problem between the
> postmasters? Is there something else I need to do?

Isn't the HINT clear enough? Raise SEMMNI and/or SEMMNS.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-06-25 05:18:25 Re: Deadlock. Referential Integrity checks select for update?
Previous Message Grant McLean 2004-06-25 04:40:27 Deadlock. Referential Integrity checks select for update?