Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdkZa-0007ny-IO for pgsql-admin@arkaria.postgresql.org; Fri, 25 Apr 2014 18:10:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WdkZa-0004CB-1n for pgsql-admin@arkaria.postgresql.org; Fri, 25 Apr 2014 18:10:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdkZY-0004C4-RK for pgsql-admin@postgresql.org; Fri, 25 Apr 2014 18:10:04 +0000 Received: from nm4.bullet.mail.bf1.yahoo.com ([98.139.212.163]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdkZV-00085w-2H for pgsql-admin@postgresql.org; Fri, 25 Apr 2014 18:10:04 +0000 Received: from [66.196.81.173] by nm4.bullet.mail.bf1.yahoo.com with NNFMP; 25 Apr 2014 18:09:59 -0000 Received: from [98.139.212.249] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 25 Apr 2014 18:09:59 -0000 Received: from [127.0.0.1] by omp1058.mail.bf1.yahoo.com with NNFMP; 25 Apr 2014 18:09:59 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 377660.55154.bm@omp1058.mail.bf1.yahoo.com Received: (qmail 17976 invoked by uid 60001); 25 Apr 2014 18:09:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1398449399; bh=RkOj22UsnjaAU19jqWwZsMXlW124/2mrUWLPQGJUK5g=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=OHQcVmJhjY3TUgviofecuGP4iA0LUzRNpE0PTauoTUcTcmrVA6h8fb8x1g/Kc1Zsr7SCdseq1b9lAPiQ68Qam2HGWCqpcRgOVsZLpCU5sLxqqRDSnSyDpMAGCEt6gvxcnkaiiJbQQPsgrYtcZ1TY25cK5NuRO4U5u7FDJihQgwY= X-YMail-OSG: .C.MVWUVM1lSgiDCjYuoIhcjiqOQo_wj3zvXj4YsJ0OUKBd zvJYUtxMdg5A9Py1YIRbl4Ox_X5O_.mxTASl_lhWPEP65rXt59bXMMbq_nj6 GdXEzp2y3pYkjKokPuRhD1ao6mhwbpyR2OttX6pq413wr2WzCcsBGvP5tzqD GiGPxkevBzqZyRVTZ5wuJRKPP7UPafzWZZj49TKfty0J_jNkdwj8WcPUrNA8 kwe6N3R5Wzn8.Zi7wrVtRIx0OxhMMfqj9VDIM_zQ4DSVrbC0xGpbiEhhpBwv .J3NbcYK2ICr0flcDJFP29qnMsEZtUi2WXduo2mqdJA.Au9ZAehRl7ITHVo6 rTBcNPMfE32MnAkogGY0UjSMbMm9Bj97Zwr3RYKNq33Eftp5zDWW7CUz8vMr dQpxkXmT1IMUbKXVze0c7DWhH4vFMqWjD6nCzfhKTAKa_Q4e_iP4DISDRcGW xZhqSiXpeAszZEHKa2b4Hsqo0eSqkKLf5o_YZrWhGP7LcXXCvjfDoR8zWhgb ubs2t7gDoASg7.XwQZnMydmrFfGITXAv7VxOCrHJ1NCoHXn1OAP.jRg-- Received: from [198.179.137.251] by web162701.mail.bf1.yahoo.com via HTTP; Fri, 25 Apr 2014 11:09:59 PDT X-Rocket-MIMEInfo: 002.001, SSB1bmRlcnN0YW5kIHdoYXQgeW91J3JlIHNheWluZywgYnV0IEkgZG9uJ3Qga25vdyB3aGF0J3MgY2F1c2luZyB0aGUgInRvdWNoIiBpbiB0aGUgZmlyc3QgcGxhY2UuwqAgSSBndWVzcyBJIG5lZWQgdG8gZnVydGhlciBleGFtaW5lL2RlYnVnLiBUaGFua3MgZm9yIHlvdXIgaGVscC4KCk9uIEZyaWRheSwgQXByaWwgMjUsIDIwMTQgMjowMCBQTSwgU2NvdHQgV2hpdG5leSA8c2NvdHRAam91cm55eC5jb20.IHdyb3RlOgogClRoZSBzbGF2ZSBkb2Vzbid0ICJ0dXJuIG9mZiIgdGhlIG1hc3Rlci4gVGhlIHRyaWcBMAEBAQE- X-Mailer: YahooMailWebService/0.8.185.657 References: <1398447433.8578.YahooMailNeo@web162701.mail.bf1.yahoo.com> <712112871.331097.1398447813672.JavaMail.zimbra@mail.int.journyx.com> <1398448636.25048.YahooMailNeo@web162704.mail.bf1.yahoo.com> <2131729726.331419.1398448843621.JavaMail.zimbra@mail.int.journyx.com> Message-ID: <1398449399.70260.YahooMailNeo@web162701.mail.bf1.yahoo.com> Date: Fri, 25 Apr 2014 11:09:59 -0700 (PDT) From: Henry Korszun Reply-To: Henry Korszun Subject: Re: To: Scott Whitney Cc: "pgsql-admin@postgresql.org" In-Reply-To: <2131729726.331419.1398448843621.JavaMail.zimbra@mail.int.journyx.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-350752386-163461983-1398449399=:70260" X-Pg-Spam-Score: -2.1 (--) 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 ---350752386-163461983-1398449399=:70260 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I understand what you're saying, but I don't know what's causing the "touch= " in the first place.=A0 I guess I need to further examine/debug. Thanks fo= r your help.=0A=0AOn Friday, April 25, 2014 2:00 PM, Scott Whitney wrote:=0A =0AThe slave doesn't "turn off" the master. The trigg= er file is intended to be touched _when the master is down_.=0A=0ASince the= master never WENT down (or came back up) and the trigger file was touched,= the slave got promoted.=0A=0AYou'll need to stop the slave, run your selec= t pg_startbackup(), rsync, etc to get your slave back to slave mode.=0A=0A= =0A=0A________________________________=0A=0AThere IS a trigger file, which = does appear to have been "touch"ed.=A0 But the problem is that a fail-over = hasn't really occurred since the original read/write primary continues to b= e a fully functioning read/write machine. But it's no longer replicating to= the erstwhile standby, which has become read/write.=A0 Bottom line, I now = have 2 read/write machines, but with no replication between them.=0A>=0A>On= Friday, April 25, 2014 1:43 PM, Scott Whitney wrote:= =0A> =0A>Sounds like you might have a "trigger_file" set in your recovery.c= onf. Do you? That or someone is issuing a pg_ctl promote command.=0A>=0A>= =0A>________________________________=0A>=0A>I'm using PostgreSQL 9.2.4 on x= 86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20070115 (SUSE Linux),= 64-bit.=0A>>=0A>>I set up streaming replication for a read/write primary a= nd a read/only =0Astandby. The replication works fine for a while, and the= n out of the =0Ablue BOTH machines become read/write, but with no replicati= on from the =0Aoriginal primary to the newly read/write standby. =0A>>=0A>>= The only log entry that seems relevant is as follows: =0AFATAL,57P01,"termi= nating walreceiver process due to administrator =0Acommand",,,,,,,,"Process= WalRcvInterrupts, walreceiver.c:150",""=0A>>=0A>>Any help/guidance would be= appreciated. Thanks in advance. =0A>>=0A>>=0A>=0A>=0A>=0A>=0A> ---350752386-163461983-1398449399=:70260 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I understand what you're saying, but I don't know = what's causing the "touch" in the first place.  I guess I need to furt= her examine/debug. Thanks for your help.
<= font face=3D"Arial" size=3D"2"> On Friday, April 25, 2014 2:00 PM, Scott Wh= itney <scott@journyx.com> wrote:
Th= e slave doesn't "turn off" the master. The trigger file is intended to be touched _when th= e master is down_.

Since the master= never WENT down (or came back up) and the trigger file was touched, the sl= ave got promoted.

You'll need to st= op the slave, run your select pg_startbackup(), rsync, etc to get your slav= e back to slave mode.



There IS = a trigger file, which does appear to have been "touch"ed.  But the problem is t= hat a fail-over hasn't really occurred since the original read/write primar= y continues to be a fully functioning read/write machine. But it's no longe= r replicating to the erstwhile standby, which has become read/write.  = Bottom line, I now have 2 read/write machines, but with no replication betw= een them.
On Friday, April 25, 2014 1:43 PM,= Scott=0A Whitney <scott@journyx.com> wrote:
Sounds like you might have a "trigger= _file" set in your recovery.conf. Do you? That or someone is issuing a pg_c= tl promote command.

I'm using PostgreSQL 9.2.4 on x86_64-unkno= wn-linux-gnu, compiled by gcc (GCC) 4.1.2 20070115=0A (SUSE Linux), 64-bit.

=0AI set up streaming replication for a read/write primary and a = read/only =0Astandby. The replication works fine for a while, and then out= of the =0Ablue BOTH machines become read/write, but with no replication fr= om the =0Aoriginal primary to the newly read/write standby.

=0AThe only log entry that seems relevant is as follow= s: =0AFATAL,57P01,"terminating walreceiver process due to administrator =0A= command",,,,,,,,"ProcessWalRcvInterrupts, walreceiver.c:150",""

=0AAny help/guidance would be appreciated. Thanks in = advance.=0A=09=09=0A=0A =0A=0A=0A=0A=0A = =0A = =0A=09=09=09=09

=





---350752386-163461983-1398449399=:70260--