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

Re: initdb fails quietly

From: "Michael Muratet US-Huntsville" <Michael(dot)Muratet(at)operon(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-novice(at)postgresql(dot)org>
Subject: Re: initdb fails quietly
Date: 2006-07-24 18:23:58
Message-ID: 2000234931344D4BA434A0C235D1956B0C491B@hsv-exmail02.operonads.local (view raw or flat)
Thread:
Lists: pgsql-novice
> 
> Do you have SELinux turned on?  Some of the earlier RHEL4 releases had
> selinux rules that prevented /usr/bin/postgres from writing /dev/tty,
> which is a reasonable rule for a daemon process but served to prevent
> any error messages from appearing in interactive use :-(.  To 
> get around
> that you can either temporarily disable selinux, or update to a more
> recent set of selinux policy rules.

Tom

Thanks, that was it. I didn't look there because I thought I already had it turned off. Works great now.

Thanks

Mike

> 
> As for the failure that it's not able to tell you about, 
> that's probably
> selinux as well.  I believe the standard policy constrains postgres to
> write only under /var/lib/pgsql, which means you *must* put 
> the database
> in the default place, unless you want to modify the policy.
> 
> You could check in /var/log/messages for "avc denied" messages to
> confirm these theories...
> 
> 			regards, tom lane
> 

pgsql-novice by date

Next:From: Fred FrazelleDate: 2006-07-25 00:09:15
Subject: Re: Is there a gui front end for this wonderful db program
Previous:From: Richard Broersma JrDate: 2006-07-24 01:07:58
Subject: Re: Is there a gui front end for this wonderful db program which works like MSAccess?

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