Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M44016=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Yx4P6-00043i-LK
 for pgsql-admin@arkaria.postgresql.org; Tue, 26 May 2015 02:15:40 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M44016=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Yx4P6-0007Ed-2a
 for pgsql-admin@arkaria.postgresql.org; Tue, 26 May 2015 02:15:40 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <tgl@sss.pgh.pa.us>) id 1Yx4P4-0007Dj-Ig
 for pgsql-admin@postgresql.org; Tue, 26 May 2015 02:15:38 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
 by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
 (Exim 4.84) (envelope-from <tgl@sss.pgh.pa.us>) id 1Yx4P0-0001zD-15
 for pgsql-admin@postgresql.org; Tue, 26 May 2015 02:15:37 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
 by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t4Q2FWsR027399;
 Mon, 25 May 2015 22:15:32 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Boylan, Ross" <Ross.Boylan@ucsf.edu>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: PostgreSQL 9.1 "database system was interrupted;
 last known up at"
In-reply-to: <F1F13E14A610474196571953929C02096D0E40@ex08.net.ucsf.edu>
References: <F1F13E14A610474196571953929C02096D0E40@ex08.net.ucsf.edu>
Comments: In-reply-to "Boylan, Ross" <Ross.Boylan@ucsf.edu>
 message dated "Tue, 26 May 2015 02:01:36 -0000"
Date: Mon, 25 May 2015 22:15:32 -0400
Message-ID: <27398.1432606532@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

"Boylan, Ross" <Ross.Boylan@ucsf.edu> writes:
> I had to power cycle my system because it became unresponsive.  Now PosgtreSQL will not start.  I would like advice about how to proceed; I think pg_resetxlog is my next step.  I have made a copy of the current database files.
> <log file="postgresql-9.1-main.log">
> 2015-05-25 10:44:21 PDT LOG:  database system was interrupted; last known up at 2015-05-22 09:22:25 PDT
> 2015-05-25 10:44:21 PDT LOG:  incomplete startup packet
> 2015-05-25 10:44:21 PDT FATAL:  could not open file "/etc/ssl/certs/ssl-cert-snakeoil.pem": Permission denied

You did not say, but I'm betting you recently updated to last week's
release, 9.1.16?

If so, this is an unforeseen side-effect of a patch to forcibly fsync
everything in the PG data directory after a crash, see
http://www.postgresql.org/message-id/flat/20150523172627.GA24277@msg.df7cb.de

We're debating how to fix it for real, but in the meantime the easiest
workaround is to change the permissions on that file so it's writable by
Postgres.  (Yeah, I know, ick.  Make a note to undo that after we fix
the fsync'ing logic.)

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin