Re: PostgreSQL in FreeBSD jails

From: Alexander Rusinov (boot_at_eurocom.od.ua)
Date: 04/26/05

  • Next message: Torfinn Ingolfsen: "apsfilter 7.2.6 - warning about unknown option 'hostname'"
    Date: Tue, 26 Apr 2005 22:59:12 +0300
    To: "Marc G. Fournier" <scrappy@hub.org>
    
    

    Marc G. Fournier wrote:

    > On Tue, 26 Apr 2005, Bill Moran wrote:
    >
    >> Alexander Rusinov <boot@eurocom.od.ua> 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.
    >
    >
    > I'm running 9 jails on a server right now, each with their own instance:
    > ....
    > and never noticed any issues ... but, this is with 4.11, not 5.x, so
    > maybe something has changed?

    Can you tell please what version of PostgreSQL are you running?

    _______________________________________________
    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"


  • Next message: Torfinn Ingolfsen: "apsfilter 7.2.6 - warning about unknown option 'hostname'"

    Relevant Pages

    • Re: PostgreSQL in FreeBSD jails
      ... >> I had this exact same problem. ... >> appears to be that, since shared memory is not segregated between jails, ... >> previously running Postgres instances. ...
      (freebsd-stable)
    • Re: [HACKERS] semaphore usage "port based"?
      ... existence of the other process, and therefore having some calls that ... This example shows that each jail must have its own SysV ... By default SysV shared memory is disallowed in jails. ...
      (freebsd-stable)
    • Re: shared memory in jails
      ... > I've been playing with shared memory in jails, ... > (The exact problem is that postgresqls, when run in jails, try to use same ...
      (freebsd-hackers)