Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XAsDC-0002tD-OC for pgsql-admin@arkaria.postgresql.org; Sat, 26 Jul 2014 02:59:54 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XAsDB-0000dV-P7 for pgsql-admin@arkaria.postgresql.org; Sat, 26 Jul 2014 02:59:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XAsDA-0000b9-Oe for pgsql-admin@postgresql.org; Sat, 26 Jul 2014 02:59:52 +0000 Received: from mout.gmx.net ([212.227.15.19]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XAsD7-0003Yx-F2 for pgsql-admin@postgresql.org; Sat, 26 Jul 2014 02:59:50 +0000 Received: from [10.0.0.9] ([67.165.8.132]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LvVUR-1WSICH3x0F-010gOE; Sat, 26 Jul 2014 04:59:47 +0200 Message-ID: <1406343584.17451.0.camel@vanquo.pezone.net> Subject: Re: Can't get a standby built From: Peter Eisentraut To: John Scalia Cc: "pgsql-admin@postgresql.org" Date: Fri, 25 Jul 2014 22:59:44 -0400 In-Reply-To: <53CFEE01.4080206@gmail.com> References: <53CFEE01.4080206@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5-2+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:kpY30eNhokoPCPGrHHj2Ygu7QP5V6EPOMPx6U+VqWwYKQ+O/172 9SV9WMS7D/2ubKh1Nr6pdTT6tyvEWCa7XKS+3nX+sHOk4LzZR54t3kp1NcMtbTqmvJ6gdzR NLGCwVub4/7mNGOnEM1FICC8qxb71FlS78pJ9qtAQ6nPpnWjvj29zHUwYGBJET7lUrVhISm WNK/Ynk5e+vbN8pCeSuog== X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Wed, 2014-07-23 at 13:16 -0400, John Scalia wrote: > Trying to rebuild my standby server (several times now). I know repeating something over and over while expecting a different result is the definition of insanity. But, I've always > started with: > > /usr/pgsql-9.3/bin/pg_basebackup -h -D /var/lib/pgsql/9.3/data -X s -c fast > > I then copy my recovery.conf file into the data directory, check that everything looks correct, and try to start the standby. The log consistently says something like: > > LOG: entering standby mode > LOG: restored log file "00000006.history" from archive > cp: cannot stat '/mnt/wallogs/archive/000000060000001200000059': No such file or directory > LOG: restored log file "000000060000001200000059" from archive > FATAL: requested timeline 6 is not a child of this server's history > DETAIL: Latest checkpoint is at 12/5B000060 on timeline 5, but in the history of the requested timeline, the server forked off from that timeline at 12/47000000. > LOG: startup process (PID 60870) exited with exit code 1 > LOG: Aborting startup due to startup process failure > > This routine has worked for me in the past and I don't understand why it won't work now. This is supposed to be a streaming replication standby server. So, do I have the wrong > flags for pg_basebackup? Or is something else going on? Could you show your recovery.conf file? It looks like the mistake is in there. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin