Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cdNJo-0008UK-0B for pgsql-admin@arkaria.postgresql.org; Mon, 13 Feb 2017 20:33:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cdNJn-0002KF-JH for pgsql-admin@arkaria.postgresql.org; Mon, 13 Feb 2017 20:33:51 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cdNI5-000878-3u for pgsql-admin@postgresql.org; Mon, 13 Feb 2017 20:32:05 +0000 Received: from mail-it0-x241.google.com ([2607:f8b0:4001:c0b::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cdNI2-0004O8-GN for pgsql-admin@postgresql.org; Mon, 13 Feb 2017 20:32:03 +0000 Received: by mail-it0-x241.google.com with SMTP id f200so292913itf.3 for ; Mon, 13 Feb 2017 12:32:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=Gc7rBhItaOBCrR3ib01zbAoIusTIrPyzQ0q/qHrQkOc=; b=n9mU5bAjhmQw/h4YkRsm7MgOMU+Pr5HlT/bCSi5EbUIjfcAve0Vrv3duCrR6N/6P2M eo4Gt1r+IP4UNKbsC6cVM6DBPeb48O+ql07SwmXbwx8oiPs17A2U6+e0VCb8T1IyVt6A c3bYWJBXsNJTVjWFhqtF6h0k627aSjZDfIM/qVxzTOVqlriufMlTopFvT7ihayF3NFOP fWOrjs1GtpCzh9uh5UZuUdFbzXBzGoLR1S0vNCS6TzobsLgEFoaMS9hZV/sEmVlXLE5c 55RSmbiKRddblmLSNA3U9lqIagA3B9uV8jjDb384BB/EakEcg44T0ia7r/c5Q8bSgRVN iwzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=Gc7rBhItaOBCrR3ib01zbAoIusTIrPyzQ0q/qHrQkOc=; b=NXnEHnsyIW8hCOKsHiihJ4CHUNfp31OWRMAOM1WS05S84jFkCKYNHv5nV73RkwOfAz 0Vi8uAs8yuRd6IuPV5byloQs/4Wt1oB+doII9QnoaRctDTzilAKho2dBb6q8nKmog8u5 o1J+IbosGbhRUhUfQIxvo9DN6K4IXq8dEs1uKGJLGGIOH03YHVRelLCniGZPqrMP+WbU OK+C3ZxV//vcVSv2SeGfI4EQtZBeoefDifNV+ZBiG9thACv61C4zx6CdaQBjA9RQhoAf R7nxK/Iu3JGUvke3GVMCe6h6qKA4CQ8XXpqukxVw0/aAvGAVuV88NcrbPQagDmL3/SO6 SkPg== X-Gm-Message-State: AMke39ncDm4Px8ggkMaVxPJ7j5SqFiqqGmolW3SVMHi0EtEpUIb+cTI+0hTd05Ztk4JL5g== X-Received: by 10.107.170.157 with SMTP id g29mr25820438ioj.148.1487017921422; Mon, 13 Feb 2017 12:32:01 -0800 (PST) Received: from irylachi ([200.55.161.75]) by smtp.gmail.com with ESMTPSA id r20sm5496346ioi.10.2017.02.13.12.31.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 13 Feb 2017 12:32:00 -0800 (PST) From: "Lazaro Garcia" To: Subject: repmgr error with automated failover Date: Mon, 13 Feb 2017 15:32:05 +0100 Message-ID: <005201d28605$f4204640$dc60d2c0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0053_01D2860E.55E598A0" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdKGBcsDVDokG2JDQNmsKiJSsAe3/g== Content-Language: es-mx X-Pg-Spam-Score: -0.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 This is a multipart message in MIME format. ------=_NextPart_000_0053_01D2860E.55E598A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello every one in the list. First thanks to repmgr. I took several days testing repmgr but I can't execute an automated failover properly. I have 2 nodes, a master(node1) and a slave(nodo2). The repmgrd service is running on both servers. When node1 goes down an automated failover take place and node2 is promounted as master, at this point all is ok, the problems comes when node2 is attached again to the cluster, for incorporating this node to the cluster I run this commands: 1. executes a clone command on node1 su -c 'repmgr -h node2 -U repmgr -d repmgr -D /var/lib/postgresql/9.6/main/ -f /etc/postgresql/9.6/main/repmgr.conf --rsync-only --force standby clone' postgres 2. start up the postgres service on node1 3. Register this node su -c 'repmgr -f /etc/postgresql/9.6/main/repmgr.conf --force standby register' postgres Then stops node2 but node1 is never promoted as master. Why node1 is not promoted? Is there something wrong? Regards. ------=_NextPart_000_0053_01D2860E.55E598A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello every one in the list. First thanks to = repmgr.

 

I took several days testing repmgr but I can't execute = an automated failover properly.

 

I have 2 = nodes, a master(node1) and a slave(nodo2). The repmgrd service is = running on both servers. When node1 goes down an automated failover take = place and node2 is promounted as master, at this point all is ok, the = problems comes when node2 is attached again to the cluster, for = incorporating this node to the cluster I run this = commands:

 

1. executes a clone command on node1

su -c 'repmgr -h node2 -U repmgr -d repmgr -D = /var/lib/postgresql/9.6/main/ -f /etc/postgresql/9.6/main/repmgr.conf = --rsync-only --force standby clone' postgres

 

2. start up = the postgres service on node1

 

3. Register = this node

su -c 'repmgr -f = /etc/postgresql/9.6/main/repmgr.conf --force standby register' = postgres

 

Then stops node2 but node1 is never promoted as = master.

 

Why node1 is not promoted? Is there something = wrong?

 

Regards.

------=_NextPart_000_0053_01D2860E.55E598A0--