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 1qCKih-0006AY-4G for pgsql-admin@arkaria.postgresql.org; Thu, 22 Jun 2023 13:51:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qCKif-0001dL-VD for pgsql-admin@arkaria.postgresql.org; Thu, 22 Jun 2023 13:51:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qCKif-0001dC-GO for pgsql-admin@lists.postgresql.org; Thu, 22 Jun 2023 13:51:29 +0000 Received: from mail-wm1-x32b.google.com ([2a00:1450:4864:20::32b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qCKic-0041c9-AC for pgsql-admin@lists.postgresql.org; Thu, 22 Jun 2023 13:51:28 +0000 Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-3f9b4a71623so38376525e9.1 for ; Thu, 22 Jun 2023 06:51:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20221208.gappssmtp.com; s=20221208; t=1687441883; x=1690033883; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=2y8B+bDYpP+dEM5xNyAcsdyk/M1h785v9kbfuinFSw8=; b=oB6E8z7cIYnfQxooCRgCdkxLO8gD8mj65GAo2+0QFAKDekfa6nIEkG2DBX2BLtSSxl z/WHFpU6H5TwEvVJHwF65E/VhRJXrhiPrCHOeFdOejWoLRNRwQ+jIzn6W0vvAzfXBkrC gpt1XaLD5vfpECFgdYF23gEC2Toxc24onMrZR4diK3CmHTvta9NRhEbGYRjbccdhpYa0 +mqwrlzULWXFxNAIrPL2ngQ+LQ6NGCZqi3F0IUbxyWtCDqgXtVhdhCAHS3SgfrUb4y4f oyLljND3yOaP9VWx+GK1ZcJo/6ipgaxjAO7KWuUnppEZMM59hRi2wj9U+1fB+hxUBVgc B14Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687441883; x=1690033883; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=2y8B+bDYpP+dEM5xNyAcsdyk/M1h785v9kbfuinFSw8=; b=EDXw3wQHC6V5c8N67IPZp7CgFAgRHEeYgHlMwbRMH5h1izecI2mF5fgMsdUz7quwTM rQgre6GQ0l5iE9OVAqoRzJO3C3MFWmCF8wB3n2HvC/dbVZTM/bxPmSqKWcpKvlXzRSi6 +84g9TOjPaSq8VAdXcIwPJkuc2cuqXpCWiBU1XOw6L1o6igSaN8VYurxOc0cwoWS52w2 frthjVkFg64dPZYbrSvAHKUoQ6K4f48+83tRqqJuiCGgLsgl1bfdidGVLNt3zjrzv/zZ lXH7jGnIy2FW2bBmG3MEETupJtBXrGJ3Xrj3Kueas8PM88vdYDsaAh4qt+TbVEZ0r5SO VbtQ== X-Gm-Message-State: AC+VfDx0YappCIaOBgntfndmdHzXaiiNDVNWU8FyZJ41TZAROHLLC0fL e8MEFPeyWE47uazA71NpB1kQBZuiAvVQDPGhnq4= X-Google-Smtp-Source: ACHHUZ6M6irs/FHJQ7Jxe/PONqfybkZMbZ/amf9bVTmot5GRuzDH0+7zy/6375sGPOHK8vrqOBw98w== X-Received: by 2002:a05:600c:203:b0:3f9:b81f:280d with SMTP id 3-20020a05600c020300b003f9b81f280dmr5431691wmi.16.1687441882956; Thu, 22 Jun 2023 06:51:22 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:3739:1e73:8ada:2f1:c5c6]) by smtp.gmail.com with ESMTPSA id u16-20020a7bc050000000b003f080b2f9f4sm18849219wmc.27.2023.06.22.06.51.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 22 Jun 2023 06:51:22 -0700 (PDT) Message-ID: Subject: Re: Error LOG: could not receive data from client: Connection reset by peer From: Laurenz Albe To: prathap vathuluru , "pgsql-admin@lists.postgresql.org" Date: Thu, 22 Jun 2023 15:51:22 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2023-06-22 at 09:56 +0000, prathap vathuluru wrote: > I am seeing the below error=C2=A0message in My PostgreSQL Error log and M= y client is unable to connect to Database . >=20 > DB Level Log : >=20 > 2023-06-22 09:30:10 UTC 192.168.0.60(22237) [29452-1] XXXXXX@XXXXXX LOG: = =C2=A0could not receive data from client: Connection reset > =C2=A0by peer. >=20 > Application level Error : >=20 > Wed Jun 21 14:53:18 CEST 2023 > SQL Error [08006]: An I/O error occurred while sending to the backend. >=20 > Could=C2=A0you=C2=A0please , Suggest relevant resolution for the Above is= sue ., We have 5 databases with enough resources in the same cluster . Usually, it is a network problem. Try to adjust the TCP keepalive settings: https://www.cybertec-postgresql.com/en/tcp-keepalive-for-a-better-postgresq= l-experience/ Yours, Laurenz Albe