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

Re: aborting startup due to startup process failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "George Wilk" <gwilk(at)ellacoya(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: aborting startup due to startup process failure
Date: 2007-06-29 02:16:08
Message-ID: 3048.1183083368@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"George Wilk" <gwilk(at)ellacoya(dot)com> writes:
> I am running a warm standby server, which executes the following command in
> a recovery mode:
> [ when done: ]
>   exit 133

Did you pick that number out of a hat?  Postgres thinks it means that
the recovery command died horribly, and abandons the recovery as a
safety measure.  (Per Single Unix Spec, this exit code from a shell
script would ordinarily mean that some program the shell called
died with a signal 5.)

Use "exit 1" or some low number like that to signal ordinary failure
to find the requested xlog file.  Numbers larger than about 125 mean
catastrophic failure of the recovery command.

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: George WilkDate: 2007-06-29 10:44:40
Subject: Re: aborting startup due to startup process failure
Previous:From: Tom ArthursDate: 2007-06-28 21:46:33
Subject: Re: aborting startup due to startup process failure

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