Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XA09x-0000x3-90 for pgsql-admin@arkaria.postgresql.org; Wed, 23 Jul 2014 17:16:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XA09w-0007G6-Ok for pgsql-admin@arkaria.postgresql.org; Wed, 23 Jul 2014 17:16:56 +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 1XA09v-0007Fz-LZ for pgsql-admin@postgresql.org; Wed, 23 Jul 2014 17:16:55 +0000 Received: from mail-yk0-x22e.google.com ([2607:f8b0:4002:c07::22e]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XA09s-0006Ll-Hg for pgsql-admin@postgresql.org; Wed, 23 Jul 2014 17:16:53 +0000 Received: by mail-yk0-f174.google.com with SMTP id q9so971346ykb.33 for ; Wed, 23 Jul 2014 10:16:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=bnJGjtOGfnd3OLn4dS0anjA1AUNxPymvYtKWpOqDppo=; b=H0aLM+noOh36//nLWRNY0JqyBRfTJIFWT74rThuX2gia5OnI9i8U7dNS9AYfK1Bw3r uSTalm8TgSqcynF9mSJ/4Rg88YIhYygLAfeGeHY8iualk8hk2EX0sefShwEA21X8sfaL tLx5wthWO3Io6bSbI5g/Y+AqXnP9H5L5n9mAxa8reM5d5gOdN6mplVTlS2JaWOpVMEyl JrhvJmsNggapN2todk2UUV6V6TD3drt4849eEimAVKjztJVaVlvDKN0iROfpr9w/5IqZ gK2C30nAKYakY2j5DVtoOVlt745h2WcX44zy0s6G9niEDSAmUxpM9eQFjP7IXfzo80Rt J1dw== X-Received: by 10.236.220.197 with SMTP id o65mr3426942yhp.125.1406135811618; Wed, 23 Jul 2014 10:16:51 -0700 (PDT) Received: from [192.168.254.6] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id c25sm8434149yhc.24.2014.07.23.10.16.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jul 2014 10:16:51 -0700 (PDT) Message-ID: <53CFEE01.4080206@gmail.com> Date: Wed, 23 Jul 2014 13:16:49 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: Can't get a standby built Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) 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 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? -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin