Message-ID: <1518757204.2909.7.camel@cybertec.at>
Subject: Re: postgres not starting
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Alan Hodgson <ahodgson@lists.simkin.ca>, pgsql-admin@postgresql.org
Date: Fri, 16 Feb 2018 06:00:04 +0100
In-Reply-To: <1518756706.2909.4.camel@cybertec.at>
References: 
	<CAKUuFd7qfEmH9zBDJEYb8zgyfiAob0XdvL+cm73MbUseHzHpyA@mail.gmail.com>
	 <1518742460.11219.15.camel@lists.simkin.ca>
	 <1518756706.2909.4.camel@cybertec.at>
Organization: Cybertec
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

I wrote:
> Alan Hodgson wrote:
> > On Thu, 2018-02-15 at 18:21 -0600, Azimuddin Mohammed wrote:
> > > Hello, 
> > > I am unable to start postgres on one of the server 
> > > I am getting below error "HINT: is another postmaster already running on port 5432, if not wait a few seconds and retry"
> > > I checked the processes nothing is running with postgres 
> > > 
> > >  I think the error caused because I removed everything under /data directory before stopping the server. 
> > > Can someone help.
> > 
> > kill -9 the old processes. The old postmaster is holding onto the port.
> > And probably some of the old file handles, too, so you might want to re-init the new database
> > cluster after really cleaning up the old one.
> 
> This seems excessive - maybe the server he wants to start is already
> running and there is no need to crash or wipe it.

Apologies - I didn't see the part that "nothing is running".

To find the process that is blocking the port, you can run the following:

lsof -i TCP:5432

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com