Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdkNH-0007N0-JQ for pgsql-admin@arkaria.postgresql.org; Fri, 25 Apr 2014 17:57:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WdkNH-0005T8-0I for pgsql-admin@arkaria.postgresql.org; Fri, 25 Apr 2014 17:57:23 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdkNF-0005Sx-NL for pgsql-admin@postgresql.org; Fri, 25 Apr 2014 17:57:21 +0000 Received: from nm31.bullet.mail.bf1.yahoo.com ([72.30.239.198]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WdkNC-0001GC-3O for pgsql-admin@postgresql.org; Fri, 25 Apr 2014 17:57:21 +0000 Received: from [66.196.81.171] by nm31.bullet.mail.bf1.yahoo.com with NNFMP; 25 Apr 2014 17:57:17 -0000 Received: from [98.139.212.248] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 25 Apr 2014 17:57:17 -0000 Received: from [127.0.0.1] by omp1057.mail.bf1.yahoo.com with NNFMP; 25 Apr 2014 17:57:17 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 94154.46055.bm@omp1057.mail.bf1.yahoo.com Received: (qmail 56388 invoked by uid 60001); 25 Apr 2014 17:57:17 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1398448637; bh=2cRCW8RAI7kc1lP3COpjgWXDvLzs7tblJztfkBYuLpU=; 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=Z3Oj6R+Vk7iKkiDQFQv9HqjnNcNnZEtOEudIT8o+vrBLzJ2zzURIB88kHB/sCWtwZEF0/bS15UOKopADkJSZIclv+CsRbuyvJwf7woUIhPjQYjkDNb6p4vcGIb6yBVYN8/wPuvhuLTdfMBxrRzFMvytj4s9+A4lE26fztT5bkgc= X-YMail-OSG: yH.y4KoVM1mbzf4fCShuCSUUrlJhrLKA1GKSqBMVxXfSgiR MdOQBDmlXn8iEU3ayAomb24a1qlEB1sAzSYIbLmkTsyXQo3aN5oxoZsVYv9l EfkkqTcHB6JqcZXOrKKu1GT1IkCE1A0KQ0xa860bWPQ59U_kdZ1so0pV_m7e KPUYWitp.VH9eJ8dwTfUbEqqQGzx2YhmGogt.Ybcjz9_uzJ0RgnZBYyoG2FV cVQn4R2GOMrz8aG9PgojcReSeKq3Cz.BSZxKz7FoHfaJFgwlfYTCMgmStute GlK77H64QTMLNntDZZp9_NEZie6H8MtS2yTy3gHik.2DIA6cLoyU5cqRGLyp Ufcx480RAheUQOhjYtI4WYZfygo3fSEJsEjLGvucRT2LuOVaq95aq8jU9LAJ O7IcOHKj4zV6Xe0KGGdyvA7dTKRyMhJ.x8MwnJ0SYlDKBHOpTXcbFjtFBSZe Eek_XhpF_o31_kTzQXYQ2Hl6uuQxfb2FUXtgLkDNG6wuPu3plMAq_qBfxVNF I1JTCNAwZC3zLFkStHbSDkVPGRAOPxQzksJYhN3ITl0f9JHfl Received: from [198.179.137.251] by web162704.mail.bf1.yahoo.com via HTTP; Fri, 25 Apr 2014 10:57:16 PDT X-Rocket-MIMEInfo: 002.001, VGhlcmUgSVMgYSB0cmlnZ2VyIGZpbGUsIHdoaWNoIGRvZXMgYXBwZWFyIHRvIGhhdmUgYmVlbiAidG91Y2giZWQuwqAgQnV0IHRoZSBwcm9ibGVtIGlzIHRoYXQgYSBmYWlsLW92ZXIgaGFzbid0IHJlYWxseSBvY2N1cnJlZCBzaW5jZSB0aGUgb3JpZ2luYWwgcmVhZC93cml0ZSBwcmltYXJ5IGNvbnRpbnVlcyB0byBiZSBhIGZ1bGx5IGZ1bmN0aW9uaW5nIHJlYWQvd3JpdGUgbWFjaGluZS4gQnV0IGl0J3Mgbm8gbG9uZ2VyIHJlcGxpY2F0aW5nIHRvIHRoZSBlcnN0d2hpbGUgc3RhbmRieSwgd2hpY2ggaGFzIGIBMAEBAQE- 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> Message-ID: <1398448636.25048.YahooMailNeo@web162704.mail.bf1.yahoo.com> Date: Fri, 25 Apr 2014 10:57:16 -0700 (PDT) From: Henry Korszun Reply-To: Henry Korszun Subject: Re: To: Scott Whitney Cc: "pgsql-admin@postgresql.org" In-Reply-To: <712112871.331097.1398447813672.JavaMail.zimbra@mail.int.journyx.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="958549312-2033156709-1398448636=:25048" X-Pg-Spam-Score: 0.6 (/) 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 --958549312-2033156709-1398448636=:25048 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable There IS a trigger file, which does appear to have been "touch"ed.=A0 But t= he problem is that a fail-over hasn't really occurred since the original re= ad/write primary continues to be a fully functioning read/write machine. Bu= t it's no longer replicating to the erstwhile standby, which has become rea= d/write.=A0 Bottom line, I now have 2 read/write machines, but with no repl= ication between them.=0A=0AOn Friday, April 25, 2014 1:43 PM, Scott Whitney= wrote:=0A =0ASounds like you might have a "trigger_fil= e" set in your recovery.conf. Do you? That or someone is issuing a pg_ctl p= romote command.=0A=0A________________________________=0A=0AI'm using Postgr= eSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 2007011= 5 (SUSE Linux), 64-bit.=0A>=0A>I set up streaming replication for a read/wr= ite primary and a read/only =0Astandby. The replication works fine for a w= hile, and then out of the =0Ablue BOTH machines become read/write, but with= no replication from the =0Aoriginal primary to the newly read/write standb= y. =0A>=0A>The only log entry that seems relevant is as follows: =0AFATAL,5= 7P01,"terminating walreceiver process due to administrator =0Acommand",,,,,= ,,,"ProcessWalRcvInterrupts, walreceiver.c:150",""=0A>=0A>Any help/guidance= would be appreciated. Thanks in advance. =0A>=0A> --958549312-2033156709-1398448636=:25048 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
There IS a trigger file, which does appear to have= been "touch"ed.  But the problem is that a fail-over hasn't really oc= curred since the original read/write primary continues to be a fully functi= oning read/write machine. But it's no longer replicating to the erstwhile s= tandby, which has become read/write.  Bottom line, I now have 2 read/w= rite machines, but with no replication between them.
On Friday, April 25, 2014 1:43 = PM, Scott 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_ctl promote command.

I'm = using PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4= .1.2 20070115 (SUSE Linux), 64-bit.

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

=0AThe onl= y log entry that seems relevant is as follows: =0AFATAL,57P01,"terminating = walreceiver process due to administrator =0Acommand",,,,,,,,"ProcessWalRcvI= nterrupts, walreceiver.c:150",""

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




= --958549312-2033156709-1398448636=:25048--