Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4CFCE9FC1EB for ; Thu, 28 Jun 2007 16:55:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 24001-09 for ; Thu, 28 Jun 2007 16:55:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 47E239FB92E for ; Thu, 28 Jun 2007 16:55:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by svr4.postgresql.org (Postfix) with ESMTP id 5753E5AF899 for ; Thu, 28 Jun 2007 19:55:34 +0000 (GMT) Received: from YZANGXP ([192.168.123.13]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 15:55:32 -0400 From: "George Wilk" To: Subject: aborting startup due to startup process failure Date: Thu, 28 Jun 2007 15:55:29 -0400 Message-ID: <006101c7b9be$479dfed0$0d7ba8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0062_01C7B99C.C08C5ED0" X-Mailer: Microsoft Office Outlook 11 Thread-Index: Ace5vkdidHv3DInERwmUd8ToCV4Pmg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-OriginalArrivalTime: 28 Jun 2007 19:55:32.0044 (UTC) FILETIME=[48D8C8C0:01C7B9BE] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-3.800.1026-15266.000 X-TM-AS-Result: No--18.439700-4.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.137 tagged_above=0 required=5 tests=AWL=-0.000, BAYES_50=0.001, FORGED_RCVD_HELO=0.135, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200706/291 X-Sequence-Number: 25959 This is a multi-part message in MIME format. ------=_NextPart_000_0062_01C7B99C.C08C5ED0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I posted to this group before with the same topic but nobody replied. Please, provide some feedback if you can. I am running a warm standby server, which executes the following command in a recovery mode: triggered=false while (test ! -f /var/ipsc/WAL/$1 && ! $triggered) do echo waiting for file: $1 sleep 30 if test -f /var/ipsc/pgsql/trigger then echo --- trigger found --- echo --- exiting recovery mode --- triggered=true fi done if ( ! $triggered) then cp /var/ipsc/WAL/$1 $2 else exit 133 fi Recovery command works just fine restoring data from the WAL files scp'd from the primary server. While in the recovery mode, when I create the trigger file breaking the while loop in recovery command, postgres does not go gently into the active database mode. Here is output: waiting for file: 00000001000000000000003A --- trigger found --- --- exiting recovery mode --- FATAL: could not restore file "00000001000000000000003A" from archive: return code 34048 LOG: startup process (PID 13994) exited with exit code 1 LOG: aborting startup due to startup process failure After finding the trigger file my recovery_cmd returns non-zero code. Why am I still getting FATAL: could not restore file ? Both my primary and standby servers run on Solaris 10 under SMF. When the standby server is attempting to change mode from recovery to regular database mode, there might be a race condition there between SMF trying to restart the server and the server trying to restart itself. or am I just hallucinating. Thanks in advance for your comments. Cheers, ~george ------=_NextPart_000_0062_01C7B99C.C08C5ED0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I posted to this group before with the same topic but = nobody replied.  Please, provide some feedback if you = can…

I am running a warm standby server, which executes = the following command in a recovery mode:

 

triggered=3Dfalse

while (test ! -f /var/ipsc/WAL/$1 && ! $triggered)

do

    echo waiting for = file: $1

 

    sleep = 30

 

    if test -f /var/ipsc/pgsql/trigger

    = then

  =        echo --- trigger found         = ---

      &= nbsp;  echo --- exiting recovery mode ---

      &= nbsp;  triggered=3Dtrue

    = fi

 

done

=

 

if ( ! = $triggered)

then

=

  cp /var/ipsc/WAL/$1 = $2

else

=

  exit = 133

fi

 

Recovery command works just fine restoring data from = the WAL files scp’d from the primary server.  While in the recovery = mode, when I create the trigger file breaking the while loop in recovery command, = postgres does not go gently into the active database mode.  Here is = output:

 

waiting for file: = 00000001000000000000003A

--- trigger found = ---

--- exiting recovery mode = ---

FATAL:  could not restore file "00000001000000000000003A" from archive: return code = 34048

LOG:  startup process (PID = 13994) exited with exit code 1

LOG:  aborting startup due to = startup process failure

 

After finding the trigger file my recovery_cmd = returns non-zero code.  Why am I still getting FATAL: = could not restore file ?

Both my primary and standby servers run on Solaris 10 = under SMF.  When the standby server is attempting to change mode from recovery to = regular database mode, there might be a race condition there between SMF trying = to restart the server and the server trying to restart itself… or am = I just hallucinating…

 

Thanks in advance for your = comments.

 

Cheers,

~george

------=_NextPart_000_0062_01C7B99C.C08C5ED0--