From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 15:09:26 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01BF316A4CE for ; Tue, 26 Apr 2005 15:09:26 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF07B43D2D for ; Tue, 26 Apr 2005 15:09:25 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from localhost (24-53-250-148.pittpa.adelphia.net [24.53.250.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id E849369A26; Tue, 26 Apr 2005 11:09:24 -0400 (EDT) Date: Tue, 26 Apr 2005 11:09:23 -0400 From: Bill Moran To: Alexander Rusinov Message-Id: <20050426110923.3edf8a2e.wmoran@potentialtech.com> In-Reply-To: <426E5713.3010906@eurocom.od.ua> References: <426E5713.3010906@eurocom.od.ua> Organization: Potential Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: PostgreSQL in FreeBSD jails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2005 15:09:26 -0000 Alexander Rusinov wrote: > Hi, > > I need to run a number of PostgreSQL servers in different FreeBSD jails. > I managed to run a first instance of PostgreSQL server in a jail, but > after I launch a new server in another jail the first one starts to > return an error messages like the following: > > semctl(1507328, 4, SETVAL, 0) failed: Invalid argument > > The problem in general is: only one instance of PostgreSQL server > processes clients' connections, all of the others return semctl errors. I had this exact same problem. I never found a solution. The cause appears to be that, since shared memory is not segregated between jails, the newly launched Postgres instances corrupt the shared memory of previously running Postgres instances. Supposedly, this shouldn't be possible, but it was happening and I never found a solution. > > The system is FreeBSD 5.4-PRERELEASE. PostgreSQL-7.4.7. SEM and SHM > sysctl setting are: > > # sysctl -a | grep shm > kern.ipc.shmmax: 100000000 > kern.ipc.shmmin: 1 > kern.ipc.shmmni: 192 > kern.ipc.shmseg: 128 > kern.ipc.shmall: 32768 > kern.ipc.shm_use_phys: 0 > kern.ipc.shm_allow_removed: 0 > > # sysctl -a | grep sem > kern.ipc.semmap: 256 > kern.ipc.semmni: 256 > kern.ipc.semmns: 512 > kern.ipc.semmnu: 256 > kern.ipc.semmsl: 60 > kern.ipc.semopm: 100 > kern.ipc.semume: 10 > kern.ipc.semusz: 92 > kern.ipc.semvmx: 32767 > kern.ipc.semaem: 16384 > > Trying to solve the problem I've set the following in postgresql.conf > files: > max_connections = 5 > shared_buffers = 100 > > Please help! What am I doing wrong? > > -- > Alexander Rusinov > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Bill Moran Potential Technologies http://www.potentialtech.com