Skip site navigation (1) Skip section navigation (2)

Re: pg_ctl restart - behaviour based on wrong instance

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_ctl restart - behaviour based on wrong instance
Date: 2011-03-19 01:20:43
Message-ID: AANLkTikDFj+2kWNPJ+v38HWv9q_J1RXaN_QPf4vghx7M@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Mar 18, 2011 at 1:19 PM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> This is OK and expected.  But then it continues (in the logfile) with:
>
> FATAL:  lock file "postmaster.pid" already exists
> HINT:  Is another postmaster (PID 20519) running in data directory
> "/var/data1/pg_stuff/pg_installations/pgsql.vanilla_1/data"?
>
> So, complaints about the *other* instance.  It doesn't happen once a successful start (with pg_ctl
> start) has happened.

I'm guessing that leftover postmaster.pid contents might be
responsible for this?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-03-19 01:35:42
Subject: Re: pg_last_xact_replay_timestamp meaning
Previous:From: Robert HaasDate: 2011-03-19 01:18:13
Subject: Re: pgsql: Document the all-balls IPv6 address.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group