From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Dhruv Ahuja <dhruvahuja(at)gmail(dot)com> |
Cc: | pgsql-cluster-hackers(at)postgresql(dot)org |
Subject: | Re: "pg_ctl promote" exit status |
Date: | 2012-10-22 21:02:13 |
Message-ID: | CA+Tgmoaw5EURzBHyqDKoZYEMJzNukSeX63orji368ZS8i0qw5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
On Wed, Oct 17, 2012 at 5:33 AM, Dhruv Ahuja <dhruvahuja(at)gmail(dot)com> wrote:
> Hello
>
> The "pg_ctl promote" command returns an exit code of 1 when the server
> is not in standby mode, and the same exit code of 1 when the server
> isn't started at all. The only difference at the time being is the
> string output at the time, which FYI are...
>
> pg_ctl: cannot promote server; server is not in standby mode
>
> ...and...
>
> pg_ctl: PID file "/var/lib/pgsql/9.1/data/postmaster.pid" does not exist
> Is server running?
>
> ...respectively.
>
> I am in the process of developing a clustering solution around luci
> and rgmanager (in Red Hat EL 6) and for the time being, am basing it
> off the string output. Maybe each different exit reason should have a
> unique exit code, whatever my logic and approach to solving this
> problem be?
I suggest reposting this on pgsql-hackers. This mailing list is mostly dead.[1]
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
[1] with apologies to S. Morgenstern
From | Date | Subject | |
---|---|---|---|
Next Message | Henning Mälzer | 2012-11-23 14:17:59 | Question: Can i cut NON-HOT chain Pointers if there are no concurrent updates? |
Previous Message | Dhruv Ahuja | 2012-10-17 09:33:51 | "pg_ctl promote" exit status |