Red Hat Bugzilla – Bug 150979
postgresql does not initialize db properly
Last modified: 2007-11-30 17:07:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6)
Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2
Description of problem:
There is a problem after postgresql server db initialization:
-bash-3.00$ psql -l
ERROR: relation "pg_catalog.pg_user" does not exist
Looks much like the fedora core 3 bug
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rm -rf /var/lib/pgsql/data
2. service postgresql start
3. psql -l
Actual Results: ERROR: relation "pg_catalog.pg_user" does not exist
Expected Results: List of available databases
Created attachment 111935 [details]
Dmesg output after database initialization
It is clean installation of RHEL 4, all available updates added and
(after I recognized the problem) relabeled on reboot.
I copied the postgresql.te policy source file from current FC3, recreated policy
by runing make, run relabel on reboot. However, the problem persists.
I found this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149237
It is exactly the same bug. Setenforce 0; postgresql start; setenforce
1 works as the workaround.
Created attachment 111959 [details]
erros when /tmp is mounted on tmpfs
If /tmp is mounted on tmpfs, there are more problems with targeted policy and
postgresql. The attached errors were generated when I did:
# setenforce 0
# /etc/init.d/postgresql start
# setenforce 1
/tmp entry from /etc/fstab looks like this:
none /tmp tmpfs defaults 0 0
The policy in U1 should fix this problem.
A prerelease is available in
You need to update policycoreutils and selinux-policy-targeted.\
I'm hitting this bug as well. Daniel, could you post the SRPM to your prerelease
policycoreutils for those of us on non-i386 arches?
I have posted all arch's and the SRPM.