Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b7Fkh-0003FS-C3 for pgsql-admin@arkaria.postgresql.org; Mon, 30 May 2016 05:28:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b7Fkg-0008Hz-BE for pgsql-admin@arkaria.postgresql.org; Mon, 30 May 2016 05:28:34 +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 1b7Fiy-0006Kf-Jy for pgsql-admin@postgresql.org; Mon, 30 May 2016 05:26:48 +0000 Received: from shopzeus.com ([87.229.70.149]) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b7Fiu-0002my-JR for pgsql-admin@postgresql.org; Mon, 30 May 2016 05:26:47 +0000 Received: from [127.127.127.127] (localhost [127.127.127.127]) (Authenticated sender: gandalf) by shopzeus.com (Postfix) with ESMTPSA id B52CE889CC40 for ; Mon, 30 May 2016 01:26:42 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shopzeus.com; s=shopzeus_com; t=1464586003; bh=+HLITLcCocvcuQkUlwYl9gvK2IKwTd5zfb9jebdnmFU=; h=To:From:Subject:Date:From; b=SIzad1m2Tei9y5RAVJOzLw5P20PbY1Nn2zhlKu9G+P7QlH6s+brt/IT+KRxrW9R5V J0MHsuXwx0uJWO3l24vfy65zMjV6NZd4ocF9QVUGME2HsvAalWigHOXfS9WpcuXzrp h1ZPPpqol60Q1L5nlmVznxoSfk3tAEEHeesICOraR3dbpjJ2vn76MRe0Xlr/RoJ8R4 UMIvw3v8UhFTV/tmrf1Nq+H9PssPNzpbyH5D0ACT+UB0GbA+knHSGpJMg1qv20vHBg Wvy7lz+1mTN+3tibjUPmcdiTzcDy3gShDcHv2glQQfuG56AeUjR89/XxYtK0ICvdKs zfsfjCLDMGByg== To: pgsql-admin@postgresql.org From: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= Subject: Could not shut down DB Message-ID: Date: Mon, 30 May 2016 07:26:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -5.7 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org I could stop it with: pg_ctl stop -i i but before that: May 30 07:21:00 appserver postgres[65202]: [5-1] FATAL: the database system is shutting down May 30 07:21:00 appserver postgres[65203]: [5-1] FATAL: the database system is shutting down May 30 07:21:00 appserver postgres[65206]: [5-1] FATAL: the database system is shutting down May 30 07:21:02 appserver postgres[65221]: [5-1] FATAL: the database system is shutting down May 30 07:21:03 appserver postgres[65222]: [5-1] FATAL: the database system is shutting down May 30 07:21:04 appserver postgres[65223]: [5-1] FATAL: the database system is shutting down May 30 07:23:25 appserver postgres[39643]: [7-1] WARNING: terminating connection because of crash of another server process May 30 07:23:25 appserver postgres[39643]: [7-2] DETAIL: 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. May 30 07:23:25 appserver postgres[39643]: [7-3] HINT: In a moment you should be able to reconnect to the database and repeat your command. May 30 07:23:25 appserver postgres[39643]: [7-4] CONTEXT: COPY sdi_manageditems, line 1 It happened in the weekend, and the server log does not contain anything except these "FATAL: shutting down" messages, so I'm not able to tell when is started. Any idea what could possible cause this error? Thanks, Laci -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin