Re: problem connecting to postgres via apache - Mailing list pgsql-general

From Adrian Klaver
Subject Re: problem connecting to postgres via apache
Date
Msg-id 52E2A51B.2000209@gmail.com
Whole thread Raw
In response to Re: problem connecting to postgres via apache  (Susan Cassidy <susan.cassidy@decisionsciencescorp.com>)
Responses Re: problem connecting to postgres via apache  (Susan Cassidy <susan.cassidy@decisionsciencescorp.com>)
Re: problem connecting to postgres via apache  (Susan Cassidy <susan.cassidy@decisionsciencescorp.com>)
List pgsql-general
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@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>     Susan Cassidy <susan.cassidy@decisionsciencescorp.com
>     <mailto:susan.cassidy@decisionsciencescorp.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.klaver@gmail.com


pgsql-general by date:

Previous
From: Susan Cassidy
Date:
Subject: Re: problem connecting to postgres via apache
Next
From: Bret Stern
Date:
Subject: Re: problem connecting to postgres via apache