pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Koen Martens <pgsql@metro.cx>
To: Marc G. Fournier <scrappy@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: semctl(): Invalid argument
Date: Wed, 05 Apr 2006 10:25:57 +0200
Message-ID: <44337F15.20709@metro.cx> (raw)
In-Reply-To: <20060402163341.P947@ganymede.hub.org>
References: <20060402143109.T947@ganymede.hub.org>
	<20060402163341.P947@ganymede.hub.org>

FWIW, i've been running two postmasters on the same port on a
FreeBSD 6.0-RELENG server, one in the host and one in a jail (this
is on a devel server). I don't like running postgresql in a jail
anyway, because it involves enabling sysv IPC inside jails, which
sort of defeats the entire purpose of having a jail..

Gr,

Koen

Marc G. Fournier wrote:
> 
> It looks like moving to FreeBSD 6.x for some of our servers is biting me
> in the butt ... they "broke" something with semaphores that used to work
> with 4.x, so that you can't run two postmasters on port 5432 within two
> seperate jails ... :(
> 
> On Sun, 2 Apr 2006, Marc G. Fournier wrote:
> 
>>
>> What would cause the following?
>>
>> # psql -U pgsql -l
>> psql: FATAL:  semctl(327686, 3, SETVAL, 0) failed: Invalid argument
>>
>> The server is FreeBSD 6.1-PRERELEASE ... there are two jails running
>> on it ... both jails are running PostgreSQL 7.4 ... I have the kernel
>> built with enough semaphores:
>>
>> options         SYSVSHM
>> options         SHMMAXPGS=199608
>> options         SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)
>>
>> options         SYSVSEM
>> options         SEMMNI=4096
>> options         SEMMNS=8192
>>
>> options         SYSVMSG                 # SYSV-style message queues
>>
>> And am definitely not using that many:
>>
>> (from ipcs -a):
>>           ID          KEY MODE        OWNER    GROUP    CREATOR 
>> CGROUP NSEMS OTIME    CTIME s       393216      5432001
>> --rw-------       70 70       70       70           17 13:46:07 13:46:07
>> s       393217      5432002 --rw-------       70       70      
>> 70       70 17 13:46:07 13:46:07
>> s       393218      5432003 --rw-------       70       70      
>> 70       70 17 13:46:07 13:46:07
>> s       393219      5432004 --rw-------       70       70      
>> 70       70 17 13:46:07 13:46:07
>> s       393220      5432005 --rw-------       70       70      
>> 70       70 17 13:46:07 13:46:07
>> s       393221      5432006 --rw-------       70       70      
>> 70       70 17 13:46:07 13:46:07
>> s       393222      5432007 --rw-------       70       70      
>> 70       70 17 13:46:07 13:46:07
>>
>> So figure there must be something else that I should be looking at ...
>>
>> Thanks ...
>>
>> ----
>> Marc G. Fournier           Hub.Org Networking Services
>> (http://www.hub.org)
>> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ:
>> 7615664
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 6: explain analyze is your friend
>>
> 
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 
> 


-- 
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, hosting, embedded systems, unix, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/



view thread (3+ messages)

Message-ID: <44337F15.20709@metro.cx>
Permalink:  ../44337F15.20709@metro.cx/
Also on:    postgresql.org/message-id/44337F15.20709@metro.cx

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pgsql@metro.cx, scrappy@postgresql.org
  Subject: Re: semctl(): Invalid argument
  In-Reply-To: <44337F15.20709@metro.cx>
  References: <20060402143109.T947@ganymede.hub.org> <20060402163341.P947@ganymede.hub.org> <44337F15.20709@metro.cx>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox