From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | armand pirvu <armand(dot)pirvu(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: authentication failure |
Date: | 2018-04-12 14:55:19 |
Message-ID: | c16e4101-78af-24db-b06c-4cf288f79a5a@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/12/2018 07:50 AM, armand pirvu wrote:
>
>> I would be inclined to raise the authentication_timeout first before setting the auth method to trust.
>>
>> I would also set the below.:
>>
>> https://www.postgresql.org/docs/10/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT
>>
>> log_connections (boolean)
>> Causes each attempted connection to the server to be logged, as well as successful completion of client authentication. Only superusers can change this parameter at session start, and it cannot be changed at all within a session. The default is off.
>>
>> log_disconnections (boolean)
>>
>> That will give you a better idea of what is going on connection wise.
>>
>>
>>
>> --
>> Adrian Klaver
>> adrian(dot)klaver(at)aklaver(dot)com
>
>
> Will do so and report back
Also, in a previous post you mentioned:
"Yes and worked fine until two days ago"
Is the code under version control so you can see if anything changed two
days ago?
If not, any recollections of significant events from that time period?
>
> Many thanks
> Armand
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | armand pirvu | 2018-04-12 15:07:29 | Re: authentication failure |
Previous Message | armand pirvu | 2018-04-12 14:50:35 | Re: authentication failure |