| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Thoma <mthoma(at)schlagundrahm(dot)ch> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: initdb failed with PostgreSQL 7.4 |
| Date: | 2005-03-17 16:40:12 |
| Message-ID: | 24964.1111077612@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Martin Thoma <mthoma(at)schlagundrahm(dot)ch> writes:
> I try to init the DB cluster without success. I am working on a RHEL 4
> box and I installed postgresql, postgresql-server and postgresql-jdbc.
> ...
> setting password...
> initdb: The password file wasn't generated. Please report this problem.
Do you have SELinux enabled in enforcement mode? That's been the cause
of most of the initdb failures we've seen reported on RHEL4 and FC3
... though this particular symptom is a new one on me. If you do,
the best bet is to turn it off (sudo /usr/sbin/setenforce 0) while you
are running initdb. There is no chance that initdb will work
under SELinux enforcement before postgresql-7.4.7-3, which I don't
think has hit the street for RHEL4 yet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2005-03-17 17:46:39 | Re: Too frequent warnings for wraparound failure |
| Previous Message | Heather Johnson | 2005-03-17 16:06:30 | Re: help with plpgsql function called by trigger |