Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <41B8F516.9040709@hq.astra.ph>
Date: Fri, 10 Dec 2004 09:00:06 +0800
From: Carlo Florendo <list-subscriber AT hq DOT astra DOT ph>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: Reini Urban <rurban AT x-ray DOT at>
Cc: pgsql-cygwin AT postgresql DOT org, cygwin AT cygwin DOT com
Subject: Re: Postgresql error  "pg_ctl stop" is invoked after a "postmaster -i &" invocation
References: <41B7B840 DOT 4060508 AT hq DOT astra DOT ph> <41B85BF2 DOT 3060304 AT x-ray DOT at>
In-Reply-To: <41B85BF2.3060304@x-ray.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Reini Urban wrote:

> Carlo Florendo schrieb:
>
>> I invoked:
>>
>> "postmaster -i -D /var/postgresql/data  &"
>>
>> and was able to start and connect to my database. Since the process 
>> was made to run on the background, I wanted a way to stop it without 
>> doing a "kill -9".  Thus, on another instance of my shell, I invoked :
>>
>> "pg_ctl stop -D /var/postgresql/data"
>>
>> Postgres says it was unsuccessful in shutting down the database.   
>> However, doing a "ps" revealed that no postgres processes were running.
>>
>> I then tried to restart the DB once again with:
>>
>> "postmaster -i -D /var/postgresql/data  &"
>>
>> This time, I got this errror:
>>
>> $ postmaster -i -D /var/postgresql/data &
>> FATAL:  could not create semaphores: No space left on device
>> DETAIL:  Failed system call was semget(5432004, 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.
>>
>>
>> I have a lot of diskspace.  Doing a "df" revealed:
>
>
> Now the tricky part:
> Did you actually read what the error message told you?


Oh sheeesh!  I'm so sorry.  (How come I didn't see the hint?....sorry, 
must've been my sleepiness.)  No, I didn't read everything.  And yes, 
the explanation is really straightforward and to the point ( I realized 
after I read it.) . 

Apologies for the noise.

Thanks!

Best Regards,

Carlo

-- 
Carlo Florendo
Astra Philippines Inc.
www.astra.ph


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/