Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOjLa-0005o0-PQ for pgsql-performance@arkaria.postgresql.org; Wed, 04 Jan 2017 11:03:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cOjLa-0001q6-CN for pgsql-performance@arkaria.postgresql.org; Wed, 04 Jan 2017 11:03:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOjLZ-0001pd-KK for pgsql-performance@postgresql.org; Wed, 04 Jan 2017 11:03:09 +0000 Received: from webmail.os-ux.com ([78.46.104.104]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOjLU-0001Vx-F9 for pgsql-performance@postgresql.org; Wed, 04 Jan 2017 11:03:08 +0000 Received: from localhost (localhost [127.0.0.1]) by webmail.os-ux.com (Postfix) with ESMTP id EEE403BDBC1; Wed, 4 Jan 2017 12:03:00 +0100 (CET) Received: from webmail.os-ux.com ([127.0.0.1]) by localhost (webmail.os-ux.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ZCyxS4NaV6hG; Wed, 4 Jan 2017 12:03:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by webmail.os-ux.com (Postfix) with ESMTP id A3AB23BDBC2; Wed, 4 Jan 2017 12:03:00 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.9.2 webmail.os-ux.com A3AB23BDBC2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=os-ux.com; s=8262FE2E-C2B5-11E2-BC5C-8AEC8B26ED38; t=1483527780; bh=a0srEaq6LAM52pxQ6fs4RgsXitX77rznkfhSfq69Ki0=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; b=mPNjVRk9He18320iLtAd+b/qVBABy1MRoHBfenZvvwL6KHQ6UmDNp6HHrOWhC2BGi UuLCYfyYK9YWefPKJCHl0d67uo4t6tqxarzMCsseE0FRWJQZ2znV8IJFoSTfHCoQSA H3+/8n9a2miPmrc54Mn8y7J5yoBotK15uxgZ8TyQ= X-Virus-Scanned: amavisd-new at os-ux.com Received: from webmail.os-ux.com ([127.0.0.1]) by localhost (webmail.os-ux.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rwgOhW_MVHow; Wed, 4 Jan 2017 12:03:00 +0100 (CET) Received: from webmail.os-ux.com (localhost [127.0.0.1]) by webmail.os-ux.com (Postfix) with ESMTP id 6CB583BDBC1; Wed, 4 Jan 2017 12:03:00 +0100 (CET) Date: Wed, 4 Jan 2017 12:03:00 +0100 (CET) From: Vucomir Ianculov To: Andreas Kretschmer Cc: pgsql-performance@postgresql.org Message-ID: <1772714872.854.1483527774431.JavaMail.vukomir@DESKTOP-9I7P6HN> In-Reply-To: <20170104091223.GA5751@tux> References: <1587952740.561.1483437295901.JavaMail.vukomir@DESKTOP-9I7P6HN> <1796991063.571.1483437640199.JavaMail.vukomir@DESKTOP-9I7P6HN> <20170104091223.GA5751@tux> Subject: Re: Unable to connect to server MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_853_442946271.1483527774430" X-Originating-IP: [78.46.104.104] X-Mailer: Zimbra 8.6.0_GA_1153 (Zimbra Desktop/7.2.8_12102_Windows) Thread-Topic: Unable to connect to server Thread-Index: kSBI0UDGrbOF8P+ba+AcohwqJQxA0A== X-Pg-Spam-Score: -5.2 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org ------=_Part_853_442946271.1483527774430 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit HI Andreas, thanks for your replay, i have checked connection number for the last 3 mouths and maximum number of connection was 300, so i can reduce this is it's cousin the issue. during this error server was 99% idle, the only thing is that there was a pg_dump running on one of the DB, can this cause this error, also i have restarted pg server 2 days before because of server cert update. Thanks. ----- Original Message ----- From: "Andreas Kretschmer" To: pgsql-performance@postgresql.org Sent: Wednesday, January 4, 2017 11:12:23 AM Subject: Re: [PERFORM] Unable to connect to server Vucomir Ianculov wrote: > Hi, > > today i head a issue with pgsql 9.3, a lot of clients complained that they are > unable to connect to the server. > when i have checked the logs i sow a lot of > FATAL: canceling authentication due to timeout you can increase authentication_timeout, default is 1 minute. How many clients do you have, do you really needs 1000 connections? If yes, please consider a connection pooler like pgbouncer. Regards, Andreas Kretschmer -- Andreas Kretschmer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance ------=_Part_853_442946271.1483527774430 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <= div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo= r: #000000'>HI Andreas,

thanks for your replay, i have checked conne= ction number for the last 3 mouths and maximum number of connection was 300= , so i can reduce this is it's cousin the issue.
during this error serve= r was 99% idle, the only thing is that there was a pg_dump running on one o= f the DB, can this cause this error, also i have restarted pg server 2 days= before because of server cert update.

Thanks.



From: "Andreas= Kretschmer" <akretschmer@spamfence.net>
To: pgsql-performa= nce@postgresql.org
Sent: Wednesday, January 4, 2017 11:12:23 AMSubject: Re: [PERFORM] Unable to connect to server

Vucomir = Ianculov <vukomir@os-ux.com> wrote:

> Hi,
>
> = today i head a issue with pgsql 9.3, a lot of clients complained that they = are
> unable to connect to the server.
> when i have checked th= e logs i sow a lot of
> FATAL:  canceling authentication due to = timeout

you can increase authentication_timeout, default is 1 minute= . How many
clients do you have, do you really needs 1000 connections? If= yes,
please consider a connection pooler like pgbouncer.


Regards, Andreas Kretschmer
--
Andreas Kretschmer
http://www.2nd= Quadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training= & Services


--
Sent via pgsql-performance mailing list (= pgsql-performance@postgresql.org)
To make changes to your subscription:<= br>http://www.postgresql.org/mailpref/pgsql-performance

= ------=_Part_853_442946271.1483527774430--