Re: problem connecting to postgres via apache

I tried:
setsebool -P httpd_can_network_connect 1

But I get:

Cannot set persistent booleans without managed policy.
Could not change policy booleans

I don't know what that means.

Susan

On Fri, Jan 24, 2014 at 9:38 AM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:

> On 01/24/2014 09:35 AM, Susan Cassidy wrote:
>
>> I've already checked that. It is enabled. I am running Scientific Linux.
>>
>
> SELinux is enabled?
> The database connection value is enabled to allow or disallow webserver
> connections?
>
>
>>
>> On Fri, Jan 24, 2014 at 8:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
>> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>>
>> Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com
>> <mailto:susan(dot)cassidy(at)decisionsciencescorp(dot)com>> writes:
>> > $dbh =
>> DBI->connect("dbi:Pg:dbname=$dbname;host=${dbserver};port=$dbport;",
>> > $dbuser, $dbpasswd) or
>> > errexit( "Unable to connect to dbname $dbname, err:
>> $DBI::errstr");
>>
>> > The exact same connection string works fine in a standalone perl
>> program.
>>
>> Given the permissions errors you mentioned upthread, I'm wondering
>> whether
>> you're running on Red Hat/CentOS, and if so whether SELinux is
>> preventing
>> apache from connecting to unexpected port numbers. I seem to recall
>> that there's a SELinux boolean specifically intended to allow or
>> disallow
>> database connections from webservers, but I couldn't tell you the name
>> offhand.
>>
>> regards, tom lane
>>
>>
>>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>