From: | Bret Stern <bret_stern(at)machinemanagement(dot)com> |
---|---|
To: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: problem connecting to postgres via apache |
Date: | 2014-01-24 17:47:50 |
Message-ID: | 1390585670.2479.2.camel@developer.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Are you calling the perl from apache (assuming yes)..? Does the web
user have the rights to execute the perl code?
Try disabling SELinux..
You'll get it..
On Fri, 2014-01-24 at 09:35 -0800, Susan Cassidy wrote:
> I've already checked that. It is enabled. I am running Scientific
> Linux.
>
>
>
> On Fri, Jan 24, 2014 at 8:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Susan Cassidy <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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Susan Cassidy | 2014-01-24 19:53:49 | Re: problem connecting to postgres via apache |
Previous Message | Adrian Klaver | 2014-01-24 17:38:35 | Re: problem connecting to postgres via apache |