Re: [ClusterLabs] NFS mount fails to stop if NFS server is lost

and it displayed error umount.nfs4: /folder: device is busy 3. Executed umount -f -l /folder and all fine Reference: https://askubuntu.com/questions/292043/how-to-unmount-nfs-when-server-is-gone Is it possible to add the lazy -l option to the umount ? From: Miro Igov Sent: 11

Re: [ClusterLabs] NFS mount fails to stop if NFS server is lost

ount -f -l ?From: Users <users-bounces@cluste= rlabs.org> on behalf of Andrei Borzenkov <arvidj...@gmail.com>= Sent: Tuesday, April 11, 2023, 20:26To: users@clusterlabs.org <users@clusterlabs.org>Subject:<= /strong> Re: [ClusterLabs] NFS mount fails to stop if NFS server is lostO

Re: [ClusterLabs] Location not working [FIXED]

= nd just specify it as "ne 1".> > > > Fro= m: Users <users-boun...@clusterlabs.org> On Behalf Of Miro Igov&g= t; Sent: 10 April 2023 14:19> To: users@clusterlabs.org> Subj= ect: [ClusterLabs] Location not working> > Hello,> I = have a reso

[ClusterLabs] NFS mount fails to stop if NFS server is lost

Hello, I have a node nas-sync-test1 with NFS server and NFS export running and another node intranet-test1 with data_1 fs mount: primitive data_1 Filesystem \ params device="nas-sync-test1:/home/pharmya/NAS" fstype=nfs options=v4 directory="/data/synology/pharmya_office/NAS_Sync/NAS"

Re: [ClusterLabs] Location not working [FIXED]

\ rule opa-nginx_2_active eq 1 Now it works fine and shows the constraint with: crm res constraint intranet-ip From: Users On Behalf Of Miro Igov Sent: 10 April 2023 14:19 To: users@clusterlabs.org Subject: [ClusterLabs] Location not working Hello, I have a resource

Re: [ClusterLabs] Location not working

tering welcomed Subject: Re: [ClusterLabs] Location not working On Mon, 2023-04-10 at 16:33 +0300, Andrei Borzenkov wrote: > On Mon, Apr 10, 2023 at 4:26 PM Ken Gaillot > wrote: > > On Mon, 2023-04-10 at 14:18 +0300, Miro Igov wrote: > > > Hello, > > > I ha

Re: [ClusterLabs] Location not working

Mon, Apr 10, 2023 at 2:19 PM Miro Igov mailto:miro.i...@pharmya.com> > wrote: Hello, I have a resource with location constraint set to: location intranet-ip_on_any_nginx intranet-ip \ rule -inf: opa-nginx_1_active eq 0 \ rule -inf: opa-nginx_2_active eq 0 In syslog

[ClusterLabs] Location not working

Hello, I have a resource with location constraint set to: location intranet-ip_on_any_nginx intranet-ip \ rule -inf: opa-nginx_1_active eq 0 \ rule -inf: opa-nginx_2_active eq 0 In syslog I see the attribute transition: Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511

Re: [ClusterLabs] Start resource only if another resource is stopped

Sent: Thursday, August 18, 2022 21:26 To: users@clusterlabs.org Subject: Re: [ClusterLabs] Start resource only if another resource is stopped On 17.08.2022 16:58, Miro Igov wrote: > As you guessed i am using crm res stop nfs_export_1. > I tried the solution with attribute and it does no

Re: [ClusterLabs] Start resource only if another resource is stopped

Aug 17 15:24:52 intranet-test1 pacemaker-attrd[1040]: notice: Setting opa-data_2_active[intranet-test2]: 0 -> 1 Aug 17 15:25:42 intranet-test1 pacemaker-fenced[1038]: notice: Watchdog will be used via SBD if fencing is required and stonith-watchdog-timeout is nonzero On 11.08.2022 17:34,

[ClusterLabs] Start resource only if another resource is stopped

Hello, I am trying to create failover resource that would start if another resource is stopped and stop when the resource is started back. It is 4 node cluster (with qdevice) where nodes are virtual machines and two of them are hosted in a datacenter and the other 2 VMs in another datacenter. Na

[ClusterLabs] PAF recover master after crash

Hello, I have a 2 node cluster with pgsqlms and sbd fencing. I tested the failover by resetting the VM running the postgresql master, it promoted the other node. When i started pacemaker on fenced node i get this error: Instance "pgsqld" controldata indicates a running primary instance, the