I encountered the same behaviour on a small ARM server running Jessie (PostgreSQL-9.4, version 159).
I noticed it after investigating why bacula-director did not start anymore. It was in fact due to postgreSQL not having started beforehand. Starting postgreSQL manually by running "systemctl start postgresql" does work. The postgresql.service appears as "active (exited)" after the start, and the postgresql@9.4-main.service appears as "active (running)" at the same time. Everything runs fine afterwards. best regards, Luc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
