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

On 8/26/19 1:07 PM, Howard Wells wrote:
> On my first post, I asked the person in charge of the firewall if 5432 was open and he told me it was.   When I
checkedit myself later, I found out that it wasn't.  Before I post to this list again, I'll check all assumptions
myself.
> 
> "Only when I go to the IP address of the server with the Postgres database will the transaction complete, and it
happensquickly."
 
> 
> My best guess is that when the IP address is also the address of the Postgres server, the firewall does not
interfere.

I would have the sysadmin confirm what is actually going on, or you run 
the risk of being bitten by this again.

> 
> Howard
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, August 25, 2019 4:55 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
> 
>> 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
opened5432, 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@gmail.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.klaver@aklaver.com
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com