Control: severity -1 grave Re: Sebastian Hofmann 2015-05-26 <20150526104258.27769.10402.reportbug@protector.sourcepark.local> > The PostgreSQL server failed to start. Please check the log output: > 2015-05-26 12:26:58 CEST LOG: > Datenbanksystem wurde unterbrochen; letzte bekannte Aktion am 2015-05-22 > 17:39:05 CEST 2015-05-26 > 12:26:58 CEST FATAL: konnte Datei >>/etc/ssl/certs/ssl-cert-snakeoil.pem<< > nicht ?ffnen: Keine Berechtigu > [FAIL15-05-26 12:26:58 CEST LOG: Startprozess (PID 28437) beendete mit Status > 1 > 2015-05-26 12:26:58 CEST LOG: Serverstart abgebrochen wegen Startprozessfehler
Hi, this is a regression in the latest round of security updates. The problem is actually a fix for a data loss issue, but now the server tries to fsync() files it didn't touch before during recovery. Non-recovery startup is not affected. > As a workaround I set ssl=false and had to remove the certificate, the key > and the links from /var/lib/postgresql/9.1/main/. > So postgres now starts without SSL support. > > We have some postgres instance with the same configuration here. The problem > occoured on two maschines, all other work fine... Upstream is working on a fix, we will push out an updated package asap. Until then, the above is the one of the possible workarounds. Once the server successfully started, you can reenable SSL. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
