Re: running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Dave VanAuken <dave(at)hawk-systems(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2
Date: 2001-01-05 04:30:16
Message-ID: Pine.BSF.4.31.0101050029580.368-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-hackers


read the jail man page:

jail.sysvipc_allowed
This MIB entry determines whether or not processes within a jail
have access to System V IPC primitives. In the current jail imple-
mentation, System V primitives share a single namespace across the
host and jail environments, meaning that processes within a jail
would be able to communicate with (and potentially interfere with)
processes outside of the jail, and in other jails. As such, this
functionality is disabled by default, but can be enabled by setting
this MIB entry to 1.

On Thu, 4 Jan 2001, Dave VanAuken wrote:

> Have a FreeBSD 4.2 box... have created two Virtual machines with the
> jail process.
> Apache and PHp configure and execute fine, but am having some
> configuration and execution problems with pgsql... not sure if I am
> missing something or if pgsql just cannot deal with being in the jail
> and sharing the sysv memory
>
> Attempting to manually start the postmaster produces the following:
>
> %postmaster -i
> IpcMemoryCreate: shmget failed (Function not implemented) key=5432010,
> size=144, permission=700
> This type of error is usually caused by an improper
> shared memory or System V IPC semaphore configuration.
> For more information, see the FAQ and platform-specific
> FAQ's in the source directory pgsql/doc or on our
> web site at http://www.postgresql.org.
> IpcMemoryIdGet: shmget failed (Function not implemented) key=5432010,
> size=144, permission=0
> IpcMemoryAttach: shmat failed (Function not implemented) id=-2
> FATAL 1: AttachSLockMemory: could not attach segment
> %
>
> Have modified the sysctl.conf file to allow usage of sysv memory, but
> as it is already shared from the host machine, this may be causing
> pgsql to barf on it.
>
> Searching for jail faq's and posts regarding this matter produces some
> close, but not helpful posts regarding chroot'ed environments.
>
> Any insights, requests for details, and assistance are appreciated.
>
> Dave
>
>

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Paul Breen 2001-01-05 11:09:56 Postmaster crashes with "Serverloop: select failed" message
Previous Message Luis Fernando Fabara M. 2001-01-05 04:28:33 Re: Cobol TO SQL To PostgreSQL

Browse pgsql-general by date

  From Date Subject
Next Message Lincoln Yeoh 2001-01-05 05:05:29 Re: Synchronous LISTEN/NOTIFY?
Previous Message Luis Fernando Fabara M. 2001-01-05 04:28:33 Re: Cobol TO SQL To PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-05 06:18:47 Well, we seem to be proof against cache-inval problems now
Previous Message Luis Fernando Fabara M. 2001-01-05 04:28:33 Re: Cobol TO SQL To PostgreSQL