On 5/24/05, Gavin Carr gavin@openfusion.com.au wrote:
Yep, I came across this a couple of months ago - it's an selinux bug on postgres initialisation:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150979
There's an updated policy in that thread that fixes the problem, and it'll be included in the upcoming RHEL4 U1.
thanks to everyone who replied particulary to gavin, the information above solved my problem.
i downloaded the selinux-policy-targeted and policycoreutils RPMs from ftp://people.redhat.com/dwalsh/SELinux/RHEL4/u1/ and did an rpm -Uvh on those packages. everything went fine after that.
p.s.: with selinux still enabled, i had an error starting apache afterwards. it was complaining about "bad user name apache" but i had it fixed by running "/sbin/fixfiles restore"
matt