Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1emUIK-0001JT-2S for pgsql-admin@arkaria.postgresql.org; Fri, 16 Feb 2018 00:54:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1emUII-0004VJ-BD for pgsql-admin@arkaria.postgresql.org; Fri, 16 Feb 2018 00:54:30 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1emUIH-0004V5-UJ; Fri, 16 Feb 2018 00:54:30 +0000 Received: from athena.simkin.ca ([2607:f040:1001:2::ff:2]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1emUID-0002GU-1a; Fri, 16 Feb 2018 00:54:28 +0000 Received: from skynet.simkin.ca (unknown [IPv6:2607:f040:1001:103::1002]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by athena.simkin.ca (Postfix) with ESMTPSA id 19C31DC696F2; Thu, 15 Feb 2018 16:54:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.simkin.ca; s=athena; t=1518742462; bh=jXc4c4W9iTCOsw21XlJX6yHLQw1iMYeLPR4f08yePoM=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References: Content-Type:X-PGP-Key:Mime-Version:Sender:From:To:Subject:Date: Reply-To; b=GtremV5eD6QDYV5U05anBakCVU8kWD2JprEY/DhSnQ+oXBgwMywqojE+RxGvY0s99 wwsHctfL+vYCRolgdPAJbAyFlpDzgd4FBl+/hcQJsRvpVFS0L7Pjf2YDdjo1CuQMJ8 GIq8ThLb/DcrN7+Ny5jFOYYWuAHQVs2O12A+7F/4NrQdVRvXJlSE4URRlsAfVptrJq QXE2A+N4su90GWbuSHG6aZdINzd2GnDGSC3kZDcfgaJQ6M2anfZ8ICJJaFbQfcY1yt iNIBPYOyMjB/dCLcnl0mzfjAoOhxiCH/WRnOPHjrQNTIXX7vu/KdAGPXA8EevaqD3a GS2KUr0M1ojjg== Received: from skynet.simkin.ca (skynet.simkin.ca [IPv6:::1]) by skynet.simkin.ca (Postfix) with ESMTP id 98FDB21A5CC58; Thu, 15 Feb 2018 16:54:20 -0800 (PST) Message-ID: <1518742460.11219.15.camel@lists.simkin.ca> Subject: Re: postgres not starting From: Alan Hodgson To: Postgres General , pgsql-admin@postgresql.org Date: Thu, 15 Feb 2018 16:54:20 -0800 In-Reply-To: References: Content-Type: multipart/alternative; boundary="=-CDqfs/w1zo0QORIxNM4M" X-PGP-Key: fp="EF82 6F8D A3BA A096 FFA3 05F2 A7A0 40A5 34E5 AA0B"; id="0x34E5AA0B"; get=; get= X-Mailer: Evolution 3.24.6 Mime-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --=-CDqfs/w1zo0QORIxNM4M Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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. --=-CDqfs/w1zo0QORIxNM4M Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
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 runni= ng on port 5432, if not wait a few seconds and retry"
I check= ed 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 ho= lding 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 th= e old one.
--=-CDqfs/w1zo0QORIxNM4M--