From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | dmigowski(at)ikoffice(dot)de, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Need clarification on "another server might be running; trying to start server anyway" |
Date: | 2016-08-02 23:25:51 |
Message-ID: | 536e78d4-0766-89e6-e0b4-ada25111660b@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 7/6/16 4:11 AM, dmigowski(at)ikoffice(dot)de wrote:
> I am currently facing an issue on Servers that are running PostgreSQL 9.5
> started from systemd, and in the case when the Servers power offs the hard
> way, and I restart it, I get an error "another server might be running;
> trying to start server anyway"
>
> The Documentation section "17.3.1. Server Start-up Failures" should maybe
> mention that error and explain, in which cases postgresql thinks that it is
> still running, because neither the port is already taken, or are there
> logfiles on the server.
>
> I also tried to remove postmaster.pid before starting postgres, but this
> strangely doesn't help either.
You get this error from pg_ctl if it finds an existing postmaster.pid
file. So if you deleted it and still get the error, something went
wrong. Please provide more details if it's reproducible.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-08-03 02:37:00 | Re: pg_prepared_statements |
Previous Message | Peter Eisentraut | 2016-08-02 17:57:15 | Re: max_worker_processes default not documented |