| From: | rob stone <floriparob(at)gmail(dot)com> |
|---|---|
| To: | John Iliffe <john(dot)iliffe(at)iliffe(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org, Joe Conway <mail(at)joeconway(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Subject: | Re: Unable to connect to Postgresql |
| Date: | 2017-04-10 02:07:12 |
| Message-ID: | 1491790032.7940.6.camel@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2017-04-09 at 20:09 -0400, John Iliffe wrote:
>
> >
> > You have Apache, PHP, and Postgres all running on your LAN at
> > 192.168.1.6.
> >
> >
> > You are on 192.168.1.10.
> >
> > Your NOT doing "php -f testfcgi.php", so how does Apache "know" to
> run
> > that script?
>
> testfcgi.php is in the document root of the default named virtual
> server.
>
O.K.
So in sites-available, your conf file just tells Apache to run
testfcgi.php and nothing else?
There is no resolution required by obtaining the IP address from
/etc/hosts.
Are you able to put some trigger_error messages into testfcgi.php in
order to make sure Apache is running the correct program?
Cheers,
Rob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-04-10 03:21:58 | Re: Unable to connect to Postgresql |
| Previous Message | John Iliffe | 2017-04-10 00:33:59 | Re: Unable to connect to Postgresql |