Re: pgsql connection timeone

Just a wild guess, but did you check your random source? We had similar
problems in Oracle and had to switch to /dev/urandom. It can be done with a
system variable setting.

On Wed, Feb 1, 2017, 7:52 AM Vucomir Ianculov <vukomir(at)os-ux(dot)com> wrote:

> can anyone help me with my problem?
> i'm really don't know from when the problem can be.
>
>
>
> ------------------------------
> *From: *"Vucomir Ianculov" <vukomir(at)os-ux(dot)com>
> *To: *"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> *Cc: *pgsql-performance(at)postgresql(dot)org
> *Sent: *Saturday, January 28, 2017 12:03:55 PM
>
> *Subject: *Re: [PERFORM] pgsql connection timeone
>
> Hi Tom,
>
> this is the entry from pg_hba.conf
> host all all 0.0.0.0/0 md5
>
> i needed to restart postgres service to be able to accept new connection,
> witch it strange becouse there was no load on the server and it head a lot
> of free ram.
>
>
>
>
> ------------------------------
> *From: *"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> *To: *"Vucomir Ianculov" <vukomir(at)os-ux(dot)com>
> *Cc: *pgsql-performance(at)postgresql(dot)org
> *Sent: *Wednesday, January 25, 2017 3:15:28 PM
> *Subject: *Re: [PERFORM] pgsql connection timeone
>
> Vucomir Ianculov <vukomir(at)os-ux(dot)com> writes:
> > i'm seeing a lot of connection time out in postgresql log
>
> > 2017-01-25 11:09:47 EET [6897-1] XXX(at)YYY FATAL: canceling
> authentication due to timeout
> > 2017-01-25 11:10:15 EET [6901-1] XXX(at)YYY FATAL: canceling
> authentication due to timeout
> > 2017-01-25 11:10:17 EET [6902-1] xxx(at)YYY FATAL: canceling
> authentication due to timeout
>
> So ... what authentication method are you using?
>
> regards, tom lane
>
>