osdir.com
mailing list archive

Subject: Re: Jailed postgres - msg#00225

List: db.postgresql.novice

Date: Prev Next Index Thread: Prev Next Index


On Mon, 27 Oct 2003, Paul Bauer wrote:

> I hope this is ok on this list. I am currently using postgres 7.2 on my
> host machine for some internal information.
>
> I recently created a jail for my apache server and want to install
> postgres (7.3) in it. I am finding that it is nearly impossible to get this
> working.
>
> $ initdb -D /usr/local/pgsql/data
> The files belonging to this database system will be owned by user
> "pgsql".
> This user must also own the server process.
>
> The database cluster will be initialized with locale C.
>
> creating directory /usr/local/pgsql/data... ok
> creating directory /usr/local/pgsql/data/base... ok
> creating directory /usr/local/pgsql/data/global... ok
> creating directory /usr/local/pgsql/data/pg_xlog... ok
> creating directory /usr/local/pgsql/data/pg_clog... ok
> creating template1 database in /usr/local/pgsql/data/base/1...
> IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: Function not
> implemented

Add:

jail.sysvipc_allowed=1

to our /etc/sysctl.conf file


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html



Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Jailed postgres

I hope this is ok on this list. I am currently using postgres 7.2 on my host machine for some internal information. I recently created a jail for my apache server and want to install postgres (7.3) in it. I am finding that it is nearly impossible to get this working. $ initdb -D /usr/local/pgsql/data The files belonging to this database system will be owned by user "pgsql". This user must also own the server process. The database cluster will be initialized with locale C. creating directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok creating template1 database in /usr/local/pgsql/data/base/1... IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: Function not implemented initdb failed. Removing /usr/local/pgsql/data. I have googled and found that it appears to be a problem with; http://lists.imeme.net/archives/imeme-users/2001-October/000473.html I note that it is a bit out of date. is this something that has been resolved, is it the right answer even? I would appreciate any help with this as only running one postgres isn't the solution I would like. I use it for too many things for that to be practicle. Thank you, Paul -- ####################################### # It does not matter how slowly you go so long as you do not stop. # Confucius (551-479 BC) ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)

Next Message by Date: click to view message preview

logging messages this time

I'd like to thank folks who helped me with the authentication problem I had earlier. I may have been asking the wrong question about, as they say, learning is never wasted. Now in order to keep from asking the wrong question again, I'm trying to get logging working so I can observe more closely what is failing and make a more appropriate diagnosis. I went to the administrative manual and found the documentation on the various logging options. It seems like what I want (diagnostic logging of traffic) would be had by the following settings in postgresql.conf: server_min_messages = info # Values, in order of decreasing detail: # debug5, debug4, debug3, debug2, debug1, # info, notice, warning, error, log, fatal, # panic client_min_messages = notice # Values, in order of decreasing detail: # debug5, debug4, debug3, debug2, debug1, # log, info, notice, warning, error silent_mode = false log_connections = true log_pid = false log_statement = true log_duration = false #log_timestamp = false #log_min_error_statement = error # Values in order of increasing severity: and.... syslog = 2 # range 0-2 syslog_facility = 'LOCAL0' syslog_ident = 'postgres' when I run my tests, all I get in /var/log/messages is: Oct 28 16:33:03 relay2 su(pam_unix)[2124]: session opened for user postgres by (uid=0) Oct 28 16:33:03 relay2 postgres[2163]: [1] LOG: database system was shut down at 2003-10-28 16:33:02 EST Oct 28 16:33:03 relay2 postgres[2163]: [2] LOG: checkpoint record is at 0/87F348 Oct 28 16:33:03 relay2 postgres[2163]: [3] LOG: redo record is at 0/87F348; undo record is at 0/0; shutdown T UE Oct 28 16:33:03 relay2 postgres[2163]: [4] LOG: next transaction id: 737; next oid: 17010 Oct 28 16:33:03 relay2 su(pam_unix)[2124]: session closed for user postgres Oct 28 16:33:03 relay2 postgres[2163]: [5] LOG: database system is ready Oct 28 16:33:04 relay2 postgresql: Starting postgresql service: succeeded which looks like the basic startup transaction from the startup script. When I run the application (horde/turba) I get nothing further out of the log. obviously, there's an understanding gap. Whatever feedback I get, I will try to turn into a summary that could be used as part of the documentation if you should want it. ---eric -- Speech recognition in use. Incorrect endings, words, and case is closer than it appears ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)

Previous Message by Thread: click to view message preview

Jailed postgres

I hope this is ok on this list. I am currently using postgres 7.2 on my host machine for some internal information. I recently created a jail for my apache server and want to install postgres (7.3) in it. I am finding that it is nearly impossible to get this working. $ initdb -D /usr/local/pgsql/data The files belonging to this database system will be owned by user "pgsql". This user must also own the server process. The database cluster will be initialized with locale C. creating directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok creating template1 database in /usr/local/pgsql/data/base/1... IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: Function not implemented initdb failed. Removing /usr/local/pgsql/data. I have googled and found that it appears to be a problem with; http://lists.imeme.net/archives/imeme-users/2001-October/000473.html I note that it is a bit out of date. is this something that has been resolved, is it the right answer even? I would appreciate any help with this as only running one postgres isn't the solution I would like. I use it for too many things for that to be practicle. Thank you, Paul -- ####################################### # It does not matter how slowly you go so long as you do not stop. # Confucius (551-479 BC) ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)

Next Message by Thread: click to view message preview

logging messages this time

I'd like to thank folks who helped me with the authentication problem I had earlier. I may have been asking the wrong question about, as they say, learning is never wasted. Now in order to keep from asking the wrong question again, I'm trying to get logging working so I can observe more closely what is failing and make a more appropriate diagnosis. I went to the administrative manual and found the documentation on the various logging options. It seems like what I want (diagnostic logging of traffic) would be had by the following settings in postgresql.conf: server_min_messages = info # Values, in order of decreasing detail: # debug5, debug4, debug3, debug2, debug1, # info, notice, warning, error, log, fatal, # panic client_min_messages = notice # Values, in order of decreasing detail: # debug5, debug4, debug3, debug2, debug1, # log, info, notice, warning, error silent_mode = false log_connections = true log_pid = false log_statement = true log_duration = false #log_timestamp = false #log_min_error_statement = error # Values in order of increasing severity: and.... syslog = 2 # range 0-2 syslog_facility = 'LOCAL0' syslog_ident = 'postgres' when I run my tests, all I get in /var/log/messages is: Oct 28 16:33:03 relay2 su(pam_unix)[2124]: session opened for user postgres by (uid=0) Oct 28 16:33:03 relay2 postgres[2163]: [1] LOG: database system was shut down at 2003-10-28 16:33:02 EST Oct 28 16:33:03 relay2 postgres[2163]: [2] LOG: checkpoint record is at 0/87F348 Oct 28 16:33:03 relay2 postgres[2163]: [3] LOG: redo record is at 0/87F348; undo record is at 0/0; shutdown T UE Oct 28 16:33:03 relay2 postgres[2163]: [4] LOG: next transaction id: 737; next oid: 17010 Oct 28 16:33:03 relay2 su(pam_unix)[2124]: session closed for user postgres Oct 28 16:33:03 relay2 postgres[2163]: [5] LOG: database system is ready Oct 28 16:33:04 relay2 postgresql: Starting postgresql service: succeeded which looks like the basic startup transaction from the startup script. When I run the application (horde/turba) I get nothing further out of the log. obviously, there's an understanding gap. Whatever feedback I get, I will try to turn into a summary that could be used as part of the documentation if you should want it. ---eric -- Speech recognition in use. Incorrect endings, words, and case is closer than it appears ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by