Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYWhW-00048m-Ga for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Jun 2018 13:11:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fYWhU-0002u3-Rr for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Jun 2018 13:11:04 +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.89) (envelope-from ) id 1fYWhT-0002tw-Mk for pgsql-bugs@lists.postgresql.org; Thu, 28 Jun 2018 13:11:04 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYWhN-0005xD-5s for pgsql-bugs@lists.postgresql.org; Thu, 28 Jun 2018 13:11:03 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 7BDA421ECD; Thu, 28 Jun 2018 09:10:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 28 Jun 2018 09:10:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imap.cc; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=tnThMd3g7x4HYKPMsd9Nnl3nuiFJd8EtgJpPLlH0SZc=; b=nkSEQyyR 9revMjSCuvlUpgx59igbLyMG43v4uEt/iWfLo/JhkNftyC7Kr6H4ZT36MkrYRhMF mNtxGXDIXcImU1hRKvk/WdwHkOCTBeiP8klL4pBmLY7RIF4zorjZMA+qHsz3gJyO nDI/f4Ly/oLb52fC3z2nI2xefUc1LVVOej7lB0efCyttTmH1CzwuavD2pPu5EUk5 ABuUGvzmyXkgSzzjo05sYPNoqype4yIWrmXLXm6pWLCszpDC28HOpCHa8F5ryn4H L+xa7ViMkom7izK1PTSSdutfRX+Y5+DtAFvQ4nZqsjqsCeclJALGZw3EqbG5nSJj 7UEIvUomMrNZbg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=tnThMd3g7x4HYKPMsd9Nnl3nuiFJd 8EtgJpPLlH0SZc=; b=swFx1nk87AyU7eH5uMGXighPtweAHbzFL9VNhL26U3V3T MVZ73uM8uvJX5M3mXTMUIbxfsLJgQbNGLQjk+kbCEH3s4PIsHvfSHV8Ly9UbYx5G dpj6/uRXCVmyOAm44VrIU60r283+qHbOKQzTa3KTmfVjW0PZmWR8aF82uOgrFB60 KIyWt2aBmpmRqKvVXnW6ygFZizXh3zc5fvmefJ6XheQM3hu4Nu9A7b6L7HllwmhP sqEz9kFKHzeGF/Ywq8V/Zj+lLOj+i5kx5KVnn1U2lRxA09rEe5upLN0Y6fidWryg yrTs5KmavdedyElhjmb9T3QoE4CKCTdvVLZ0VB94A== X-ME-Proxy: X-ME-Sender: Received: from [10.2.33.124] (unknown [185.25.33.70]) by mail.messagingengine.com (Postfix) with ESMTPA id 413FA102E9; Thu, 28 Jun 2018 09:10:54 -0400 (EDT) Subject: Re: Server Crash To: Anjul Tyagi , Sergei Kornilov , "pgsql-bugs@lists.postgresql.org" References: <6514671530091875@web12g.yandex.ru> From: Alexey Bashtanov Message-ID: <53e106c6-1b6c-827e-7f32-1fedcaf8a524@imap.cc> Date: Thu, 28 Jun 2018 14:10:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------CFDBC2F8030AAE60626FC879" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------CFDBC2F8030AAE60626FC879 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hello Anjul, The first line of the log looks relevant. My only guess is a stored procedure written in an untrusted language may send a backend signal 14. Do you have any of these, like pl/perl? Best,  Alex On 27/06/18 11:58, Anjul Tyagi wrote: > Hi Sergei, > > thanks for your response. We have already plan to upgrade the same in > PG 10, but i am scared if we faced the same issue with upgraded > version as well. > > Regards, > > Anjul *TYAGI* > > ** > > *ü****Go Green* > > > ------ Original Message ------ > From: "Sergei Kornilov" > > To: "Anjul Tyagi" >; "pgsql-bugs@lists.postgresql.org" > > > Sent: 27-06-2018 15:01:15 > Subject: Re: Server Crash > >> Hello >>> 2018-06-21 13:43:29 EDT [22212]: [4-1] user=cmsuser,db=forte >>> ,host=10.10.1.3,port=10.10.1.3(56601),id=5b2bdea5.56c4,line=4DETAIL: >>> The postmaster has commanded this server process to roll back the >>> current transaction and exit, because another server process exited >>> abnormally and possibly corrupted shared memory. >> This is just consequence of error. Similar message is reported by >> every client connect process. Real error was before all of these >> messages. >>> Postgres - Postgres 9.1.13 >> You are using unsupported major version and even very old minor. Last >> released 9.1 was 9.1.24 (Release Date: 2016-10-27). You missed bug >> fixes for 2.5 years. >> According versioning policy [1] bug fixing ceases for EOL versions. >> I suggest upgrade to one of supported version. Postgresql 10 is good >> choice. >> If error still occurs on supported version - we need exact error >> message from failed backend. >> regards, Sergei >> [1] https://www.postgresql.org/support/versioning/ --------------CFDBC2F8030AAE60626FC879 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hello Anjul,

The first line of the log looks relevant.
My only guess is a stored procedure written in an untrusted language may send a backend signal 14.
Do you have any of these, like pl/perl?

Best,
 Alex

On 27/06/18 11:58, Anjul Tyagi wrote:
Hi Sergei,

thanks for your response. We have already plan to upgrade the same in PG 10, but i am scared if we faced the same issue with upgraded version as well. 

 
 
 

Regards,

Anjul TYAGI

 

ü Go Green


------ Original Message ------
From: "Sergei Kornilov" <sk@zsrv.org>
Sent: 27-06-2018 15:01:15
Subject: Re: Server Crash

Hello
 
2018-06-21 13:43:29 EDT [22212]: [4-1] user=cmsuser,db=forte ,host=10.10.1.3,port=10.10.1.3(56601),id=5b2bdea5.56c4,line=4DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
This is just consequence of error. Similar message is reported by every client connect process. Real error was before all of these messages.
 
Postgres - Postgres 9.1.13
You are using unsupported major version and even very old minor. Last released 9.1 was 9.1.24 (Release Date: 2016-10-27). You missed bug fixes for 2.5 years.
According versioning policy [1] bug fixing ceases for EOL versions.
 
I suggest upgrade to one of supported version. Postgresql 10 is good choice.
If error still occurs on supported version - we need exact error message from failed backend.
 
regards, Sergei
 
 

--------------CFDBC2F8030AAE60626FC879--