Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42425=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1WdkQ4-0007Qx-5q
 for pgsql-admin@arkaria.postgresql.org; Fri, 25 Apr 2014 18:00:16 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42425=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1WdkQ3-0008Mu-KF
 for pgsql-admin@arkaria.postgresql.org; Fri, 25 Apr 2014 18:00:15 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <payal@omniti.com>) id 1WdkQ2-0008LH-CF
 for pgsql-admin@postgresql.org; Fri, 25 Apr 2014 18:00:14 +0000
Received: from mail-qg0-f48.google.com ([209.85.192.48])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <payal@omniti.com>) id 1WdkPy-0007vu-L2
 for pgsql-admin@postgresql.org; Fri, 25 Apr 2014 18:00:14 +0000
Received: by mail-qg0-f48.google.com with SMTP id q108so4383161qgd.35
 for <pgsql-admin@postgresql.org>; Fri, 25 Apr 2014 11:00:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:references
 :mime-version:content-type:content-disposition
 :content-transfer-encoding:in-reply-to:user-agent;
 bh=jQlV0QHDgv2UyYKweYz7hN9PcQZrXiTpeOABnWckPQM=;
 b=LsGO9L0YLF4ZQT8TCUahREV0qI6EkrpzolX8UZSpJvTloegtnrg/qDEW4R8TaWweUJ
 MskJ+iFx09noWhn7ygIA10SuWea6tAPQoG/sD9IsLAjLgSLQMtHpeiiKTiXxlS5zkbPo
 LE7SK+C8+lIU9r2bM3/Ozi2ieESbzL7PHdEM945MQTFKJr+D9e+AVFbYO5Qs9fy4sNky
 Wk4nhJUqrYryHcoGKukT4/sCRTUPLGPu56Eo9GpB09ob/mmOCgm5yMrXXs2wcOKNpEJb
 /S8QqlLil9bKNr/9DOlR0nc36NfWs/Fd2cZneJ8dWuQmPDx9bsaIVty6lFZTbfX0ki9x
 DSfg==
X-Gm-Message-State: 
 ALoCoQkqzJWImaMEUYqVCTePTB1w4sL4G/M/n3KmvRLYR9ZKFcLiNu/c0jwWqddwqsmHrpHAeIpg
X-Received: by 10.140.33.181 with SMTP id j50mr12883255qgj.81.1398448808648;
 Fri, 25 Apr 2014 11:00:08 -0700 (PDT)
Received: from payal-ThinkPad-T520
 (static-108-48-124-82.washdc.fios.verizon.net. [108.48.124.82])
 by mx.google.com with ESMTPSA id c17sm10445872qge.21.2014.04.25.11.00.07
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Fri, 25 Apr 2014 11:00:07 -0700 (PDT)
Date: Fri, 25 Apr 2014 14:00:06 -0400
From: Payal Singh <payal@omniti.com>
To: Henry Korszun <henryk302@yahoo.com>
Cc: Scott Whitney <swhitney@journyx.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: 
Message-ID: <20140425180005.GA6284@payal-ThinkPad-T520>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1398448636.25048.YahooMailNeo@web162704.mail.bf1.yahoo.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Once a trigger file is touched on slave, it makes the slave standalone, but doesn't stop the old primary server automatically. You have to handle that, by either stopping the old primary altogether or pointing a virtual ip to the new slave. 
On Fri, Apr 25, 2014 at 10:57:16AM -0700, Henry Korszun wrote:
> There IS a trigger file, which does appear to have been "touch"ed.  But the problem is that a fail-over hasn't really occurred since the original read/write primary continues to be a fully functioning read/write machine. But it's no longer replicating to the erstwhile standby, which has become read/write.  Bottom line, I now have 2 read/write 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.
> >
> >I set up streaming replication for a read/write primary and a read/only 
> standby.  The replication works fine for a while, and then out of the 
> blue BOTH machines become read/write, but with no replication from the 
> original primary to the newly read/write standby. 
> >
> >The only log entry that seems relevant is as follows: 
> FATAL,57P01,"terminating walreceiver process due to administrator 
> command",,,,,,,,"ProcessWalRcvInterrupts, walreceiver.c:150",""
> >
> >Any help/guidance would be appreciated. Thanks in advance. 
> >
> >


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin