Skip site navigation (1) Skip section navigation (2)

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

From: "Dave VanAuken" <dave(at)hawk-systems(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: RE: running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2
Date: 2001-01-05 14:11:13
Message-ID: DBEIKNMKGOBGNDHAAKGNCELPCLAA.dave@hawk-systems.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-generalpgsql-hackers
As listed in the initial post immediately following the screen output,
I have already set the sharing in the sysctl.conf file, the same error
is being generated.

Dave

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org]On Behalf Of The Hermit
Hacker
Sent: Thursday, January 04, 2001 11:30 PM
To: Dave VanAuken
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: running pgsql 7 under Jail'ed virtual machine on FreeBSD
4.2



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

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-01-05 16:20:43
Subject: Re: [HACKERS] Re: pg_dump return status..
Previous:From: Philip WarnerDate: 2001-01-05 13:25:13
Subject: Re: [HACKERS] Re: pg_dump return status..

pgsql-admin by date

Next:From: Tom LaneDate: 2001-01-05 17:10:04
Subject: Re: Postmaster crashes with "Serverloop: select failed" message
Previous:From: Paul BreenDate: 2001-01-05 11:09:56
Subject: Postmaster crashes with "Serverloop: select failed" message

pgsql-general by date

Next:From: Ron PetersonDate: 2001-01-05 14:34:25
Subject: Re: How passwords can be crypted in postgres?
Previous:From: Philip WarnerDate: 2001-01-05 13:25:13
Subject: Re: [HACKERS] Re: pg_dump return status..

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group