Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jR4mA-00057L-Rg for pgsql-admin@arkaria.postgresql.org; Wed, 22 Apr 2020 02:06:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jR4ld-0006ca-QG for pgsql-admin@arkaria.postgresql.org; Wed, 22 Apr 2020 02:05:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jR4ld-0006ZE-5Z for pgsql-admin@lists.postgresql.org; Wed, 22 Apr 2020 02:05:37 +0000 Received: from resqmta-ch2-02v.sys.comcast.net ([2001:558:fe21:29:69:252:207:34]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jR4la-0002o9-F8 for pgsql-admin@lists.postgresql.org; Wed, 22 Apr 2020 02:05:35 +0000 Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-02v.sys.comcast.net with ESMTP id R4ZSjzceLGF45R4lXjY1ZD; Wed, 22 Apr 2020 02:05:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1587521131; bh=Urx1YZMgPDlbxY3FSFUAQ+5dnWQ4nDMWyQiOHb2whaw=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=BD5IcFHbNfN0xGHVqmhVtmYbK5xjK1ArT3cCP7lCZCPCUY8zNjQmKCoaF0g0NgijQ pZlNgZpI8YtF0UndsS6I4nW09Ne0iex3FCWi6WBicMDCMqWqq6SoQVBpQ7elDMEvTC BFeobLUl2v5GTuSl3d8YW+oKGQ+EPY3s7dim1JMugQd+Ll3fbKZviGEjUUcrOR7e+w aNf8X2VUfnGXev2U6o/SMpQJ/N/uc1kNgQUDtB3RjRhgX6cFAc3JBpYvHUfbCRmy8e 5lD+leUog0PK4xWyJ2z0iTtJiMPdyA8ZrU3D4Ys6ZBme6EjabFZUNQDy2jtF08LnxE 68nSjO8J7XhZA== Received: from jsievers.comcast.net ([12.30.159.20]) by resomta-ch2-17v.sys.comcast.net with ESMTPA id R4lNjNQQrmZ6hR4lOjwxia; Wed, 22 Apr 2020 02:05:29 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduhedrgeeigdehgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufhfffgjkfgfgggtgfesthhqredttderjeenucfhrhhomheplfgvrhhrhicuufhivghvvghrshcuoehgshhivghvvghrshduleestghomhgtrghsthdrnhgvtheqnecukfhppeduvddrfedtrdduheelrddvtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopehjshhivghvvghrshdrtghomhgtrghsthdrnhgvthdpihhnvghtpeduvddrfedtrdduheelrddvtddpmhgrihhlfhhrohhmpehgshhivghvvghrshduleestghomhgtrghsthdrnhgvthdprhgtphhtthhopehprghvrghnrdgusggrvdejsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqrggumhhinheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-Xfinity-VMeta: sc=0.00;st=legit Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 1191F26005A; Tue, 21 Apr 2020 21:05:21 -0500 (CDT) From: Jerry Sievers To: Pavan Kumar Cc: Pgsql-admin Subject: Re: Application outage with XX000: could not receive data from client: Connection timed out References: Date: Tue, 21 Apr 2020 21:05:21 -0500 In-Reply-To: (Pavan Kumar's message of "Tue, 21 Apr 2020 19:11:43 -0500") Message-ID: <87tv1cqnq6.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Pavan Kumar writes: > Hello Experts, > > one of our application=C2=A0is getting intermittent outage=C2=A0and they > are=C2=A0saying database=C2=A0issue. we can=C2=A0only see=C2=A0below mess= age from the > postgreSQL log file. Apart from this No "FATAL|ERROR|WARNING" > message.=C2=A0 I'd suspect firewall and/other network gear idle socket timeouts. Check for and verify tcp keepalive is enabled at both ends and aggressive enough to overcome the above, if applicable. HTH > > =C2=A0 2020-04-21 04:26:58.066 GMT [119043] [PostgreSQL JDBC Driver] > [(51724)] [idle] LOG: =C2=A0XX000: could not receive data from client: > Connection timed out > 2020-04-21 04:26:58.066 GMT [119043]=C2=A0 [PostgreSQL JDBC Driver] > (51724)] [idle] LOCATION: =C2=A0pq_recvbuf, pqcomm.c:978 > > based on the error message connecting is timing out. i am not sure > which is triggering time out.=C2=A0 > there is no fire wall between app to database and database side we > are not keeping any time out. > > Any one ran into same issue ? if yes please help us narrow down the > problem and the possible solution. > > > > > > -- > Regards, > > #!=C2=A0 Pavan Kumar > ----------------------------------------------- > Sr. Database Administrator..! > NEXT GENERATION PROFESSIONALS, LLC > Cell =C2=A0 =C2=A0#=C2=A0 267-799-3182 #=C2=A0 pavan.dba27 (Gtalk)=C2=A0= =C2=A0 > India =C2=A0 # 9000459083 > > > Take Risks; if you win, you will be very happy. If you lose you > will be Wise =C2=A0 > > > --=20 Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net