Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v3tmT-005K3N-RV for pgsql-admin@arkaria.postgresql.org; Wed, 01 Oct 2025 10:09:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v3tmR-000Fly-SC for pgsql-admin@arkaria.postgresql.org; Wed, 01 Oct 2025 10:09:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v3tmR-000Flq-FH for pgsql-admin@lists.postgresql.org; Wed, 01 Oct 2025 10:09:52 +0000 Received: from mail-yx1-xb135.google.com ([2607:f8b0:4864:20::b135]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v3tmQ-0013fP-04 for pgsql-admin@postgresql.org; Wed, 01 Oct 2025 10:09:51 +0000 Received: by mail-yx1-xb135.google.com with SMTP id 956f58d0204a3-6352c8b683eso8030218d50.2 for ; Wed, 01 Oct 2025 03:09:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759313388; x=1759918188; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=r8zUTpCoFFA/KNLnU2juXlGjvRM3KxqJupOTULr+uNo=; b=NS8cs4ysh8s+z2QPi8tS1QAlv1vTPEdxiekiz6upkH5GPVYZ2cmoy24GEiwEUxaIpd Wel37hOJNEubzBhZfsnSznBXDBwamOQKDnNOwRVNJQfvgqLF0m+lVxekOpKloOyncfBD NnkLRc6ODOIlk4RANyKnAJmoBe4SfWXIhwJCi1tL1ZQChoapdqvfWpM0AL7/gEVGMcQH 5YQxG7BboM7yjy00ihM5G5fGHNYw3Dr/PlmgCOD9cgGVumYds+fotbDsQ3YjFMjNl/Qd R7gHZ1SoUp3cs8VeyU+5i8CUsGeuc3uqlcSKLMr8jtQ2MWKNo47wN+kuTo4bwfKdSWzX Lblw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759313388; x=1759918188; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=r8zUTpCoFFA/KNLnU2juXlGjvRM3KxqJupOTULr+uNo=; b=FVOWVdekfYH2Sgn6l5tB4vi/dGBXjJmOosOTdvX2SKvqJ9sZSFd+DLTxc8zWqprSar 4UnmESrrwoT8UK6lzvPjYMaH8RN/nXXjwzTl7Cs3tWNQP2uwZumLEhmmxj6eVcDlQ0VP /rj4iAdFom3cD1bzaEpDuPOG+P1VTB9KjOmKoGtMa3REH3lTIA0JXYHZF5m7JYfaCIrQ b0NC61Vrc0YF+gF5kXALJUJDfVvwiN6//ViAzg5/WHR4N5rv1Z47C80usoKXI/hEozUE Jzy0LeAk63vkqIopKhbGohH1QwwTSVm2MIC0mlX3mMxNJKO6695dhUGswXHbHDjZmUmh QBPA== X-Gm-Message-State: AOJu0YyyZD4vCOq+Y53lDDwDDKL264HhdQB1B0fBdO7OSxel556EEB5H FVU2YGqV7ObnseJe6FXX338TRqa5gpIk2KpP485VAFkktlDaZJb1QKMt+9+9KU9t/PtBFfwjunY dn90FtMSrwJCCyj2GxR+nggmR1l1QRjtCD+vOcBxyFA2A X-Gm-Gg: ASbGncvprTJnwFLopXcAtoEsJ4l90p0eZGq1Op1vjh2CiN5pUF17j5rxhKvuGRfZ4iL GM94HPxy1xtWX2d7OdWzElUVjQAbCYz3xbTyim9/7E9pAYfdXE9RJftouxr6BBLlnj4xLiaqHJU s5bmA/hWElCEnEZYXIscCldg7Yc4ku993yN+xBJDbbBT+vCtnQQLaDiU4LJc1uSH9AOltw0Jsmx lP6EaNYQiJaTlOjBZY12fr8dlrYlrU= X-Google-Smtp-Source: AGHT+IEo7u6f7zIdV+NvycNyVIFnfW9a7XKbCrvcxiObMf+AIf8H7MxoNHH+ATNqDO3ZR6a3g8Bv+vY4MnaPC6JnK/I= X-Received: by 2002:a05:690e:4287:20b0:62c:204:5dfa with SMTP id 956f58d0204a3-63b6ff7ea54mr2973598d50.29.1759313388433; Wed, 01 Oct 2025 03:09:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tayyab Fayyaz Date: Wed, 1 Oct 2025 15:09:37 +0500 X-Gm-Features: AS18NWAnzJ0LBZTdByr5LBFRUUoncaC0XredOcIVuWqUGE7sDJec9p2avGalGI8 Message-ID: Subject: Re: repmgr cannot bring up the standby database after switchover manaully To: Chris Lee Cc: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary="00000000000090f6060640161109" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000090f6060640161109 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Chris, I faced this issue it will not add automatically as standby you have to add it manually. But I wrote a script which perform to add old primary as standby once it's back online. Tayyab On Wed, 1 Oct 2025, 3:02=E2=80=AFpm Chris Lee, wrote: > Hi all, > > I have 2 postgresql servers. One is the primary and another one is the > standby. I am trying to setup repmgr to do the switchover manually. > Passwordless ssh have been setup for postgres ID on both servers. > > I use this command "repmgr standby switchover --log-level=3DDEBUG > --verbose". The standy database is able to promote to be the primary. For > the previous primary database, it was shutdown. It was not able to bring = up > as standby by repmgr. > > Does anyone encounter this issue before? Thanks a lot for any suggestions= . > > Here is my OS and DB versions: > > OS version: CentOS Stream release 8 > Postgres DB version: 15.12 > rempmgr version: 5.5.0 > > Here is the repmgr conf files: > >>>>> > node_id=3D1 # Use 2 on standby > node_name=3D'primary' > conninfo=3D'host=3Dcentos804 user=3Drepmgr dbname=3Drepmgr password=3Dxxx > connect_timeout=3D15' > use_primary_conninfo_password=3Dtrue > data_directory=3D'/var/lib/pgsql/15/data' # Adjust for your setup > pg_bindir=3D'/usr/pgsql-15/bin' > service_start_command =3D 'sudo systemctl start postgresql-15' > service_stop_command =3D 'sudo systemctl stop postgresql-15' > <<<<< > > >>>>> > node_id=3D2 # Use 2 on standby > node_name=3D'standby' > conninfo=3D'host=3Dcentos803 user=3Drepmgr dbname=3Drepmgr password=3Dxxx > connect_timeout=3D15' > use_primary_conninfo_password=3Dtrue > data_directory=3D'/var/lib/pgsql/15/data' # Adjust for your setup > pg_bindir=3D'/usr/pgsql-15/bin' > service_start_command =3D 'sudo systemctl start postgresql-15' > service_stop_command =3D 'sudo systemctl stop postgresql-15' > <<<<< > > Regards, > Chris > --00000000000090f6060640161109 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Chris,

I faced this issue it will not add automatically as standby you have = to add it manually.

But = I wrote a script which perform to add old primary as standby once it's = back online.

Tayyab

On Wed, 1 Oct 2025, 3:02=E2=80=AFpm Chris Lee, <clee.hk@gmail.com> wrote:
Hi all,

I have 2 po= stgresql servers. One is the primary and another one is the standby. I am t= rying to setup repmgr to do the switchover manually. Passwordless ssh have = been setup for postgres ID on both servers.

I use this command "= ;repmgr standby switchover --log-level=3DDEBUG --verbose". The standy = database is able to promote to be the primary. For the previous primary dat= abase, it was shutdown. It was not able to bring up as standby by repmgr. = =C2=A0

Does anyone encounter this issue before? Thanks a lot for any= suggestions.

Here is my OS and DB versions:

OS version: Cent= OS Stream release 8
Postgres DB version: =C2=A015.12
rempmgr version:= 5.5.0

Here is the repmgr conf files:
>>>>>
nod= e_id=3D1 =C2=A0# Use 2 on standby
node_name=3D'primary'
conni= nfo=3D'host=3Dcentos804 user=3Drepmgr dbname=3Drepmgr password=3Dxxx co= nnect_timeout=3D15'
use_primary_conninfo_password=3Dtrue
data_dir= ectory=3D'/var/lib/pgsql/15/data' =C2=A0# Adjust for your setup
= pg_bindir=3D'/usr/pgsql-15/bin'
service_start_command =3D 's= udo systemctl start postgresql-15'
service_stop_command =C2=A0=3D &#= 39;sudo systemctl stop postgresql-15'
<<<<<

&g= t;>>>>
node_id=3D2 =C2=A0# Use 2 on standby
node_name=3D&= #39;standby'
conninfo=3D'host=3Dcentos803 user=3Drepmgr dbname= =3Drepmgr password=3Dxxx connect_timeout=3D15'
use_primary_conninfo_= password=3Dtrue
data_directory=3D'/var/lib/pgsql/15/data' =C2=A0= # Adjust for your setup
pg_bindir=3D'/usr/pgsql-15/bin'
servi= ce_start_command =3D 'sudo systemctl start postgresql-15'
servic= e_stop_command =C2=A0=3D 'sudo systemctl stop postgresql-15'
<= ;<<<<

Regards,
Chris
--00000000000090f6060640161109--