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 1tFpDA-00GOpF-B2 for pgsql-general@arkaria.postgresql.org; Tue, 26 Nov 2024 06:38:12 +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 1tFpCA-004cjZ-Hp for pgsql-general@arkaria.postgresql.org; Tue, 26 Nov 2024 06:37:10 +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 1tFpCA-004cj5-5q for pgsql-general@lists.postgresql.org; Tue, 26 Nov 2024 06:37:10 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFpC6-003zY3-Kz for pgsql-general@lists.postgresql.org; Tue, 26 Nov 2024 06:37:09 +0000 Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2ffb0bbe9c8so34036421fa.0 for ; Mon, 25 Nov 2024 22:37:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732603025; x=1733207825; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=IEeTcSSc69XlN5blvFY3qoMEq6qm2UGhL+25cYpeoNY=; b=GA/7rarFLTNcOa9wOtWkwAtvFY6aImI5EUfyc85nfPUlwEeaeazFREnTK2RXQmrZF+ irxkPTDGMeNWKYKc+6cPx+UFfRrVcbrYjwb+57DjK2Fhw12mu6n1+72yHF/0C9+qO31x zsyXQMlEOuYqUk2zjhgEX/cKeOJUOZuHeyDOSWDwFV3MMo9SkOHtQhlQNV73zRHZ56Gx RKXPLdLhd8TgjkYc+pBllBZ59dTJsOodgo1mTL6voXml3J4WeLBYhfUXZpMJxxu7j2K2 XgZULLZUZwT+Duu1s3j7z6doMU2L0ZXWg1nkX3JzhDg2q6TswMAKh+KGYBo7JCvApnAj PO5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732603025; x=1733207825; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=IEeTcSSc69XlN5blvFY3qoMEq6qm2UGhL+25cYpeoNY=; b=aqBjMcSmskTTc7rbnpuQiowCs7sVNO98w/vdrvAUF4/Ahtpevcv8we6aZpMNXzZDcI MOHhhHX1mfXRFuhUDgr06etX2g8lahTImqHsfBv7mB7K0lXgJNCD6oNPP+UA+wrifvEe 8ry/WTKWWmEkDnGJLpQeXQtoOgZ9sONx+zCG5GMgXtJ5rfaIfYZPYfiHeeXiLY9yrB3k Llcy7Uu6iXHE+Wmm3NLOWqZRs34NFvbDUt/y/L3nlBFMzAwzU0Zc0nBsTsJ4okUWFlt3 f6s2/GTHyYUySJ1UtA08a99JtE1zekRYQO4Pj0UVFimMZ66EqJzQhffPTDSopX92QG+y 96Pg== X-Gm-Message-State: AOJu0YxkaMJUmZaAnT1JMbx+kdjTqhzgRhLmPfPbD49GxK9UP8XIPYch zjYfv7SRdiz9uWnEFJUOvGDAhZWOiIrJBnGuzCGfdnvrsqvtJzjC9jRT+2/hR6fk7mpMxLUMK62 lm9sQtcWDq+8QtVSUGS1lTUe6fv8xEC4uib0= X-Gm-Gg: ASbGnct6p2FCH9jCXPTM8/V6bHn0IB7fo4qY5QhWmARyQ+gHnQoIaBq3zGF6S+2QvTk 6wlL6MLG5j8SaXzTYVRRQrJwl9RI3hqnhKyI14goLuFxP6v0oh4Yn23ZU+QLfQAk= X-Google-Smtp-Source: AGHT+IEnV6SXettz2VXI7FXtrN4zhTefDrsreCeoGRTVPxozFw21ucrZIqJH2zy9Mll8RF/6I93zOB/2ZaCJn80EgNo= X-Received: by 2002:a2e:a916:0:b0:2ff:c69c:db0f with SMTP id 38308e7fff4ca-2ffc69cde8emr30287031fa.34.1732603025005; Mon, 25 Nov 2024 22:37:05 -0800 (PST) MIME-Version: 1.0 From: jayakumar s Date: Tue, 26 Nov 2024 12:06:52 +0530 Message-ID: Subject: DB Switchover using repmgr--Error To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000d7a7950627cb13df" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d7a7950627cb13df Content-Type: text/plain; charset="UTF-8" Hi Team, I have tried to configure DB switch over using repmgr. Post updated repmgr file then tried to register in primary db but getting the below error. Kindly check and let me know to fix the issue. *Error:* [postgres@post1 bin]$ ./repmgr -f /var/lib/pgsql/repmgr.conf primary register ERROR: following errors were found in the configuration file: syntax error in file "/var/lib/pgsql/repmgr.conf" line 3, near token "data_directory" syntax error in file "/var/lib/pgsql/repmgr.conf" line 6, near token "log_file" [postgres@post1 bin]$ *Conf file:* [postgres@post1 data]$ cat /var/lib/pgsql/repmgr.conf node_id=1 node_name=primary conninfo='host=192.168.29.193 user=repmgr dbname=repmgr connect_timeout=2' data_directory='/application/pgsql/data' failover=automatic promote_command='/usr/pgsql-16/bin/repmgr standby promote -f /var/lib/pgsql/repmgr.conf --log-to-file' follow_command='/usr/pgsql-16/bin/repmgr standby follow -f /var/lib/pgsql/repmgr.conf --log-to-file --upstream-node-id=%n' pg_bindir='/usr/pgsql-16/bin' log_file='/usr/pgsql-16/repmgr.log' [postgres@post1 data]$ --000000000000d7a7950627cb13df Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

I have tried to con= figure DB switch over using repmgr. Post updated repmgr file then tried to = register in primary db but getting the below error.

Kindly check and let=C2=A0me know to fix the issue.

Error:

[postgres@post1 bin]$ ./repm= gr -f /var/lib/pgsql/repmgr.conf primary register
ERROR: following error= s were found in the configuration file:
=C2=A0 syntax error in file &quo= t;/var/lib/pgsql/repmgr.conf" line 3, near token "data_directory&= quot;
=C2=A0 syntax error in file "/var/lib/pgsql/repmgr.conf"= line 6, near token "log_file"
[postgres@post1 bin]$

Conf file:

[postgres@post1 = data]$ cat /var/lib/pgsql/repmgr.conf
node_id=3D1
node_name=3Dprimary=
conninfo=3D'host=3D192.168.29.193 user=3Drepmgr dbname=3Drepmgr con= nect_timeout=3D2' data_directory=3D'/application/pgsql/data' fa= ilover=3Dautomatic
promote_command=3D'/usr/pgsql-16/bin/repmgr stand= by promote -f /var/lib/pgsql/repmgr.conf --log-to-file'
follow_comma= nd=3D'/usr/pgsql-16/bin/repmgr standby follow -f /var/lib/pgsql/repmgr.= conf --log-to-file --upstream-node-id=3D%n'
pg_bindir=3D'/usr/pg= sql-16/bin' log_file=3D'/usr/pgsql-16/repmgr.log'
[postgres@= post1 data]$
--000000000000d7a7950627cb13df--