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 1r8yZE-00D3Rl-Ma for pgsql-general@arkaria.postgresql.org; Fri, 01 Dec 2023 08:08:08 +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 1r8yZC-006Cod-SY for pgsql-general@arkaria.postgresql.org; Fri, 01 Dec 2023 08:08:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8yZC-006CoV-Fs for pgsql-general@lists.postgresql.org; Fri, 01 Dec 2023 08:08:06 +0000 Received: from mail1.dalibo.net ([51.159.93.128] helo=mail.dalibo.com) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8yZ5-008EtO-GZ for pgsql-general@lists.postgresql.org; Fri, 01 Dec 2023 08:08:05 +0000 Received: from karst (82-65-23-130.subs.proxad.net [82.65.23.130]) by mail.dalibo.com (Postfix) with ESMTPSA id A368C1FAD1; Fri, 1 Dec 2023 09:07:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1701418076; bh=WKU4ZRqP5VrxZq52fHDxfPxR3kEyv3jdC/9X5OwSR+Q=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=HSKo7XTCRnDjF2vbjeOOmRUD+9dtsNpBMPVRmeFZn+jN5USDgr7V7yVowfEvV5GlT Ff/o8A0p9EPJlMxb2d7Vnn+Gq6Yc8/mXHzOFK24PxOAlnSaQRbgkEfRAlHNbhbmf6i OQOFFUR7itsYdnMkYw1VjHZyAeA8kOSXtSFQJe/w= Date: Fri, 1 Dec 2023 09:07:51 +0100 From: Jehan-Guillaume de Rorthais To: Vijaykumar Patil Cc: "pgsql-general@lists.postgresql.org" Subject: Re: PAF with Pacemaker Message-ID: <20231201090751.06453597@karst> In-Reply-To: References: Organization: Dalibo MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Thu, 30 Nov 2023 19:07:34 +0000 Vijaykumar Patil wrote: > I have two postgres server one is primary and other one replica, I have setup > replication and configured pacemaker and corosync. > > But still I'm facing issue while creating resource. It is showing invalid > parameters. > > [root@scrbtrheldbaas001 heartbeat]# pcs status > Cluster name: pg_cluster > Cluster Summary: > * Stack: corosync (Pacemaker is running) > * Current DC: scrbtrheldbaas001 (version 2.1.6-8.el8-6fdc9deea29) - > partition with quorum > * Last updated: Thu Nov 30 19:04:29 2023 on scrbtrheldbaas001 > * Last change: Thu Nov 30 13:41:53 2023 by root via cibadmin on > scrbtrheldbaas002 > * 2 nodes configured > * 2 resource instances configured > > Node List: > * Online: [ scrbtrheldbaas001 scrbtrheldbaas002 ] > > Full List of Resources: > * Clone Set: pgsqld-clone [pgsqld] (promotable): > * Stopped (invalid parameter): [ scrbtrheldbaas001 scrbtrheldbaas002 ] Side note: make sure to setup fencing and/or watchdog. > My postgres version is 15.3 but still is searching recover.conf . please > find below log. It does not search for the recovery.conf for v15. In fact, if you setup a recovery.conf with postgres v15, PAF errors immediately with the appropriate error message: https://github.com/ClusterLabs/PAF/blob/master/script/pgsqlms#L1350 > ... > Nov 30 13:43:32 scrbtrheldbaas002.crb.apmoller.net > pacemaker-controld[1114133]: notice: Result of probe operation for pgsqld on > scrbtrheldbaas002: invalid parameter (Recovery template file must contain > "standby_mode = on") This is the real error. But this error is only checked for v11 and before. So now I wonder what version of PAF you are actually using? Is it up to date or a very old one? Or maybe the agent failed to parse correctly your actual version from $PGDATA/PG_VERSION ? https://github.com/ClusterLabs/PAF/blob/master/script/pgsqlms#L637 ++