Theo, Don't know much about the tools you may have installed on Ubuntu (don't use Ubuntu), but sounds like you have something 'snapshot-ing' your dataset... And that, on restart-after-inelegant-shutdown, the PostgreSQL service is trying to attach to the 'wrong' data. Generally, yes; PostgreSQL is extremely reliable. We've found it to recover quite nicely, even from bad (human, sometimes testing-intentional!) behavior. Also doesn't sound like a version-specific problem. Lou Picciano ----- Original Message ----- From: "Theodotos Andreou" <theo@xxxxxxxxxxxxxxxx> To: pgsql-admin@xxxxxxxxxxxxxx Sent: Wednesday, February 12, 2014 12:59:22 AM Subject: Error: pid file is invalid, please manually kill the stale server process. Hi all, I am using postgres on Ubuntu 12.04 64 bit server. The version is 9.1.10 and I used the stock postgres from Ubuntu repos. I have a weird problem. Sometimes when the machine is restarted, there is no $PGDATA/postmaster.pid file. So when I try to restart postgres (service postgresql restart) I get the following error: Error: pid file is invalid, please manually kill the stale server process. An even scarier side-effect of this is that the data, when this happens, are older than the most recent data in the database. It may be important to know that postgres runs under monit non sysv init or upstart. Also postgres is installed on a customer appliance that may experience frequent reboots and even abrupt poweroffs! Is postgres in general ideal for this situation? Is there an optimal configuration for this scenario? Regards theo -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
