Re: Postgres SQLSTATE[08006] [7] timeout expired

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Howard Wells <mr284(at)protonmail(dot)com>, Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: Condor <condor(at)stz-bg(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres SQLSTATE[08006] [7] timeout expired
Date: 2019-08-25 23:55:02
Message-ID: 5a2935c8-8a3b-4592-5751-3b4a49b7c4ca@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/25/19 2:59 PM, Howard Wells wrote:
> I solved this problem. All four servers are behind a firewall, but port 5432 was not open on the firewall. When I opened 5432, the problem disappeared.

Glad you solved. Confused as to how:

1) From first post:
"All four are behind the same firewall, with port 5432 open."

2) A subsequent post:

"Only when I go to the IP address of the server with the Postgres
database will the transaction complete, and it happens quickly."

>
> Thanks to Rob Sargent, Adrian Klaver and Condor for your help.
>
> Howard
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, August 25, 2019 12:20 PM, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
>
>>>>>>>
>>
>>>>>>> console.
>>>>>>> The pg_hba.conf has these lines enabled:
>>>>>>> pg_hba.conf:
>>>>>>> host all [username] 0.0.0.0/0 trust
>>>>>>> host all all 0.0.0.0/0 md5
>>>>>>> host all all ::/0 md5
>>>>>>> host all all all
>>
>> Who is encrypting the password?
>>
>>>
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Kretschmer 2019-08-26 06:49:36 Re: BDR: moving a node
Previous Message Howard Wells 2019-08-25 21:59:23 Re: Postgres SQLSTATE[08006] [7] timeout expired