| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | chenchuanling(at)msn(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #11365: denied apache cgi connect |
| Date: | 2014-09-07 16:36:24 |
| Message-ID: | 6186.1410107784@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
chenchuanling(at)msn(dot)com writes:
> Centos 6.3 integrated 8.4.11 version no problem,but upgrade to version 9.3.5
> apache cgi connection denied.Must be set: setenforce 0, such ability can
> be.
That's not something the PG community can do anything about. If there's a
bug in the SELinux policy for apache, you need to complain to Red Hat to
get it fixed.
I suspect though that if you dig a little bit, you will find that this
case has been foreseen, and there's a SELinux policy boolean that you
are supposed to set to allow apache processes to do database access.
A quick browse in the output of "semanage boolean -l" suggests that
"allow_user_postgresql_connect" might be the right thing, or maybe
"httpd_can_network_connect_db" ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-09-07 21:50:56 | Re: BUG #11365: denied apache cgi connect |
| Previous Message | Alvaro Herrera | 2014-09-07 01:42:45 | Re: Re: BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes |