Re: authentication failure

From: armand pirvu <armand(dot)pirvu(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: authentication failure
Date: 2018-04-12 14:37:43
Message-ID: 4CF15AC7-6D2B-43B8-8838-0F429240905E@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> On Apr 12, 2018, at 9:28 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> On 04/12/2018 07:15 AM, armand pirvu wrote:
>
>>>
>>>
>> Sorry for the double posting but could it be from
>> #authentication_timeout = 1min# 1s-600s
>
> From you previous post:
>
> "It is almost like the authnetication stops working for whatever reason"
>
> So to be clear the initial connections in the process go through, but at some point they start failing. Is that correct?
>
> The timeout could be an issue. It would helpful to also see what max_connections setting is.
>
>> So if the server gets a bit oveloaded this could play a role ?
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com

Yes correct initially they go through but at some point they start failing
Max_connections is set to 200 on the postgres server, but I did not notice any message about being maxed out connections wise
As a workaround for this very specific set of processes, until things get back in line so to speak, do you think from the devweb2004 (where processing is done) to devdb2004 (where the postgres database resides), should I just go from md5 to trusted ?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-04-12 14:48:36 Re: authentication failure
Previous Message Adrian Klaver 2018-04-12 14:28:32 Re: authentication failure