From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | John Iliffe <john(dot)iliffe(at)iliffe(dot)ca> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unable to connect to Postgresql |
Date: | 2017-04-08 00:39:55 |
Message-ID: | 60bb48f5-2491-b26b-6d11-e3711755b874@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/07/2017 05:10 PM, John Iliffe wrote:
Actually Ccing list this time
> On Friday 07 April 2017 19:51:57 you wrote:
>> On 04/07/2017 04:57 PM, John Iliffe wrote:
>>> Hi Adrian:
>>
> Well, it ain't that simple! I am trying to take advantage of having a new
> server that doesn't have to be in production until month end to update
> everything to the latest and greatest. Everything runs properly on the
> existing server which is on Postgresql 9.2.1, using mod_php to connect.
>
> Changes that I have made are: update Postgresql, PHP, and Apache, change
> to fcgi from mod_php (which should not get involved here, but I backed out
> that change and still doesn't work) and the addition of SELinux for
> security (none on present server).
Aah, so a lot changed.
Do you have a way of trying to connect using PHP that does not involve
going through Apache?
>
> Also, using the on board firewall (firewalld) to provide a secondary domain
> where the actual business processes run.
>
> So, I guess the answer is that the current arrangement has never run
> correctly.
>
>>> Regards,
>>>
>>> John
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | John Iliffe | 2017-04-08 00:56:02 | Re: Unable to connect to Postgresql |
Previous Message | Adrian Klaver | 2017-04-08 00:35:40 | Re: Unable to connect to Postgresql |