Re: Running two postmasters on one host: could not create semaphores - Mailing list pgsql-general

From Tom Lane
Subject Re: Running two postmasters on one host: could not create semaphores
Date
Msg-id 2070.1088139223@sss.pgh.pa.us
Whole thread Raw
In response to Running two postmasters on one host: could not create semaphores  (Edwin New <edwin_new@toll.com.au>)
List pgsql-general
Edwin New <edwin_new@toll.com.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

pgsql-general by date:

Previous
From: Grant McLean
Date:
Subject: Deadlock. Referential Integrity checks select for update?
Next
From: Tom Lane
Date:
Subject: Re: Deadlock. Referential Integrity checks select for update?