Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 22 Jul 2003 15:05:56 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: Postmaster failing 'not enough core' Message-ID: <20030722190556.GF1180@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <000a01c34dfa$5b8f3320$0400a8c0 AT milo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000a01c34dfa$5b8f3320$0400a8c0@milo> User-Agent: Mutt/1.4i Kevin, [Sorry for the sluggish response time, but I have been distracted by the impending Python 2.3 release...] On Sat, Jul 19, 2003 at 02:33:35PM +0100, Kevin Jones wrote: > I'm running Cygwin 1.3.22.1 on Windows 2003. Note that I do not have access to Windows 2003, so you will probably have to debug this yourself... > I've installed ipc-daemon as a service and I'm trying to get > postmaster started. > > [snip] > > "IpcMemoryCreate: shmget(key=5432001, size=1499136, 03600) failed: Not > enough core" > > followed by the rest of the message. I've tried reducing buffer sizes to > 16 (the minimum) and the max connections to 8 (as can be seen above) and > I'm still getting the problem. This could be a cygipc under 2003 problem -- adjusting PostgreSQL parameters most likely will not have any affect. > I suspect it's a permissions problem (most of these seem to be:) ) Do I > need to do anything special to the postgres user, or allow it access to > any particular directory? > > Any help would be much appreciated. Does ipctest work? $ ipctest h Test v0.03 Shared memory segment 132 created shmat return code= 0 shmat ok adr= 0x680000 ok Does removing the cygipc temp files help? $ rm -fr /tmp/MultiFile* /tmp/cygipc_? Does making /tmp world writable help? $ chmod 777 /tmp If none of the above helps, then you will have to build a debug version of cygipc, rebuild PostgreSQL against it, figure out which cygipc operation is failing with ENOMEM, and *why* it is failing. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/