Re: [ClusterLabs] Cluster does not start resources
On Wed, Aug 24, 2022 at 6:29 PM Lentes, Bernd wrote: > > > - On 24 Aug, 2022, at 16:26, kwenning kwenn...@redhat.com wrote: > > >> > >> if I get Ulrich right - and my fading memory of when I really used crmsh > >> the > >> last time is telling me the same thing ... > >> > > I get the impression many people prefer pcs to crm. Is there any reason for > that ? > And can i use pcs on Suse ? If yes, how ? I guess both is possible - pcs on Suse and crmsh on Red Hat - unsupported by the distribution of course in both cases. But you'll probably be most happy using what comes with the distribution. Apologies for a potential misunderstanding I might have triggered. Me telling that I haven't been using crmsh for some time doesn't have to do anything with quality & usability of any of crmsh or pcs. It solely has to do with how my CV has developed recently ;-) Klaus > > Bernd___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 16:26, kwenning kwenn...@redhat.com wrote: >> >> if I get Ulrich right - and my fading memory of when I really used crmsh the >> last time is telling me the same thing ... >> I get the impression many people prefer pcs to crm. Is there any reason for that ? And can i use pcs on Suse ? If yes, how ? Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 16:26, kwenning kwenn...@redhat.com wrote: > > Guess the resources running now are those you tried to enable before > while they were globally stopped > No. First i set stop-all-resources to false. Then SOME resources started. Then i tried several times to start some VirtualDomains using "crm resource start" which didn't succeed. Some time later i tried it again and it succeeded ... Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On Wed, Aug 24, 2022 at 4:24 PM Klaus Wenninger wrote: > > On Wed, Aug 24, 2022 at 2:40 PM Lentes, Bernd > wrote: > > > > > > - On 24 Aug, 2022, at 07:21, Reid Wahl nw...@redhat.com wrote: > > > > > > > As a result, your command might start the virtual machines, but > > > Pacemaker will still show that the resources are "Stopped (disabled)". > > > To fix that, you'll need to enable the resources. > > > > How do i achieve that ? > > crm resource start ... > > if I get Ulrich right - and my fading memory of when I really used crmsh the > last time is telling me the same thing ... > Guess the resources running now are those you tried to enable before while they were globally stopped > Klaus > > > > Bernd___ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On Wed, Aug 24, 2022 at 2:40 PM Lentes, Bernd wrote: > > > - On 24 Aug, 2022, at 07:21, Reid Wahl nw...@redhat.com wrote: > > > > As a result, your command might start the virtual machines, but > > Pacemaker will still show that the resources are "Stopped (disabled)". > > To fix that, you'll need to enable the resources. > > How do i achieve that ? crm resource start ... if I get Ulrich right - and my fading memory of when I really used crmsh the last time is telling me the same thing ... Klaus > > Bernd___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
Hi, Now with "crm resource start" all resources started. I didn't change anything !?! Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 07:21, Reid Wahl nw...@redhat.com wrote: > As a result, your command might start the virtual machines, but > Pacemaker will still show that the resources are "Stopped (disabled)". > To fix that, you'll need to enable the resources. How do i achieve that ? Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
> > There is no resource with the name "virtual_domain" in your list. All > non-active resources in your list are either disabled or unmanaged. > Without actual commands that list resource state before "crm resource > start", "crm resource start" itself and once more resource state after > this command any answer will be just a wild guess. "crm resource start virtual_domain" is just an example, virtual_domain is a placeholder for the name of the VM. Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 07:22, Reid Wahl nw...@redhat.com wrote: > Are the VMs running after your start command? No. Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On 24.08.2022 08:13, Lentes, Bernd wrote: > > > - On 24 Aug, 2022, at 07:03, arvidjaar arvidj...@gmail.com wrote: > >> On 24.08.2022 07:34, Lentes, Bernd wrote: >>> >>> >>> - On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: >>> >>> The stop-all-resources cluster property is set to true. Is that intentional? >>> OMG. Thanks Reid ! >>> >>> But unfortunately not all virtual domains are running: >>> >> >> what exactly is not clear in this output? All these resources are >> explicitly disabled (target-role=stopped) and so will not be started. >> > That's clear. But a manual "crm resource start virtual_domain" should start > them, > but it doesn't. > There is no resource with the name "virtual_domain" in your list. All non-active resources in your list are either disabled or unmanaged. Without actual commands that list resource state before "crm resource start", "crm resource start" itself and once more resource state after this command any answer will be just a wild guess. ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On Tue, Aug 23, 2022 at 10:21 PM Reid Wahl wrote: > > On Tue, Aug 23, 2022 at 10:14 PM Lentes, Bernd > wrote: > > > > > > > > - On 24 Aug, 2022, at 07:03, arvidjaar arvidj...@gmail.com wrote: > > > > > On 24.08.2022 07:34, Lentes, Bernd wrote: > > >> > > >> > > >> - On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: > > >> > > >> > > >>> The stop-all-resources cluster property is set to true. Is that > > >>> intentional? > > >> OMG. Thanks Reid ! > > You're welcome :) > > > >> > > >> But unfortunately not all virtual domains are running: > > >> > > > > > > what exactly is not clear in this output? All these resources are > > > explicitly disabled (target-role=stopped) and so will not be started. > > > > > That's clear. But a manual "crm resource start virtual_domain" should start > > them, > > but it doesn't. > > I'm familiar with pcs and the pacemaker CLI tools but not crmsh, so > I'm not sure exactly what `crm resource start` does. However, running > a manual start command in pcs or crm_resource simply runs the resource > agent's start operation. **It does not inform Pacemaker.** I presume > crmsh behaves similarly. > > As a result, your command might start the virtual machines, but > Pacemaker will still show that the resources are "Stopped (disabled)". > To fix that, you'll need to enable the resources. Are the VMs running after your start command? > > > > > Bernd___ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ > > > > -- > Regards, > > Reid Wahl (He/Him) > Senior Software Engineer, Red Hat > RHEL High Availability - Pacemaker -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On Tue, Aug 23, 2022 at 10:14 PM Lentes, Bernd wrote: > > > > - On 24 Aug, 2022, at 07:03, arvidjaar arvidj...@gmail.com wrote: > > > On 24.08.2022 07:34, Lentes, Bernd wrote: > >> > >> > >> - On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: > >> > >> > >>> The stop-all-resources cluster property is set to true. Is that > >>> intentional? > >> OMG. Thanks Reid ! You're welcome :) > >> > >> But unfortunately not all virtual domains are running: > >> > > > > what exactly is not clear in this output? All these resources are > > explicitly disabled (target-role=stopped) and so will not be started. > > > That's clear. But a manual "crm resource start virtual_domain" should start > them, > but it doesn't. I'm familiar with pcs and the pacemaker CLI tools but not crmsh, so I'm not sure exactly what `crm resource start` does. However, running a manual start command in pcs or crm_resource simply runs the resource agent's start operation. **It does not inform Pacemaker.** I presume crmsh behaves similarly. As a result, your command might start the virtual machines, but Pacemaker will still show that the resources are "Stopped (disabled)". To fix that, you'll need to enable the resources. > > Bernd___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 07:03, arvidjaar arvidj...@gmail.com wrote: > On 24.08.2022 07:34, Lentes, Bernd wrote: >> >> >> - On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: >> >> >>> The stop-all-resources cluster property is set to true. Is that intentional? >> OMG. Thanks Reid ! >> >> But unfortunately not all virtual domains are running: >> > > what exactly is not clear in this output? All these resources are > explicitly disabled (target-role=stopped) and so will not be started. > That's clear. But a manual "crm resource start virtual_domain" should start them, but it doesn't. Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On 24.08.2022 07:34, Lentes, Bernd wrote: > > > - On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: > > >> The stop-all-resources cluster property is set to true. Is that intentional? > OMG. Thanks Reid ! > > But unfortunately not all virtual domains are running: > what exactly is not clear in this output? All these resources are explicitly disabled (target-role=stopped) and so will not be started. > Stack: corosync > Current DC: ha-idg-2 (version > 1.1.24+20210811.f5abda0ee-3.21.9-1.1.24+20210811.f5abda0ee) - partition with > quorum > Last updated: Wed Aug 24 06:14:37 2022 > Last change: Wed Aug 24 06:04:24 2022 by root via cibadmin on ha-idg-1 > > 2 nodes configured > 40 resource instances configured (21 DISABLED) > > Node ha-idg-1: online > fence_ilo_ha-idg-2 (stonith:fence_ilo2): Started fenct > ha-idg-2 mit ILO > dlm (ocf::pacemaker:controld): Started > clvmd (ocf::heartbeat:clvm): Started > vm-mausdb (ocf::lentes:VirtualDomain):Started > fs_ocfs2(ocf::lentes:Filesystem.new): Started > vm-nc-mcd (ocf::lentes:VirtualDomain):Started > fs_test_ocfs2 (ocf::lentes:Filesystem.new): Started > gfs2_snap (ocf::heartbeat:Filesystem):Started > gfs2_share (ocf::heartbeat:Filesystem):Started > Node ha-idg-2: online > fence_ilo_ha-idg-1 (stonith:fence_ilo4): Started fenct > ha-idg-1 mit ILO > clvmd (ocf::heartbeat:clvm): Started > dlm (ocf::pacemaker:controld): Started > vm-sim (ocf::lentes:VirtualDomain):Started > gfs2_snap (ocf::heartbeat:Filesystem):Started > fs_ocfs2(ocf::lentes:Filesystem.new): Started > gfs2_share (ocf::heartbeat:Filesystem):Started > vm-seneca (ocf::lentes:VirtualDomain):Started > vm-ssh (ocf::lentes:VirtualDomain):Started > > Inactive resources: > > Clone Set: ClusterMon-clone [ClusterMon-SMTP] > Stopped (disabled): [ ha-idg-1 ha-idg-2 ] > vm-geneious (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-idcc-devel (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-genetrap (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-mouseidgenes (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-greensql (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-severin (ocf::lentes:VirtualDomain):Stopped (disabled) > ping_19216810010(ocf::pacemaker:ping): Stopped (disabled) > ping_19216810020(ocf::pacemaker:ping): Stopped (disabled) > vm_crispor (ocf::heartbeat:VirtualDomain): Stopped (unmanaged) > vm-dietrich (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-pathway (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-crispor-server (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-geneious-license (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-amok (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-geneious-license-mcd (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-documents-oo (ocf::lentes:VirtualDomain):Stopped (disabled) > vm_snipanalysis (ocf::lentes:VirtualDomain):Stopped (disabled, unmanaged) > vm-photoshop(ocf::lentes:VirtualDomain):Stopped (disabled) > vm-check-mk (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-encore (ocf::lentes:VirtualDomain):Stopped (disabled) > > Migration Summary: > * Node ha-idg-1: > * Node ha-idg-2: > > Also a manual "crm resource start" wasn't successfull. > > Bernd > > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: > The stop-all-resources cluster property is set to true. Is that intentional? OMG. Thanks Reid ! But unfortunately not all virtual domains are running: Stack: corosync Current DC: ha-idg-2 (version 1.1.24+20210811.f5abda0ee-3.21.9-1.1.24+20210811.f5abda0ee) - partition with quorum Last updated: Wed Aug 24 06:14:37 2022 Last change: Wed Aug 24 06:04:24 2022 by root via cibadmin on ha-idg-1 2 nodes configured 40 resource instances configured (21 DISABLED) Node ha-idg-1: online fence_ilo_ha-idg-2 (stonith:fence_ilo2): Started fenct ha-idg-2 mit ILO dlm (ocf::pacemaker:controld): Started clvmd (ocf::heartbeat:clvm): Started vm-mausdb (ocf::lentes:VirtualDomain):Started fs_ocfs2(ocf::lentes:Filesystem.new): Started vm-nc-mcd (ocf::lentes:VirtualDomain):Started fs_test_ocfs2 (ocf::lentes:Filesystem.new): Started gfs2_snap (ocf::heartbeat:Filesystem):Started gfs2_share (ocf::heartbeat:Filesystem):Started Node ha-idg-2: online fence_ilo_ha-idg-1 (stonith:fence_ilo4): Started fenct ha-idg-1 mit ILO clvmd (ocf::heartbeat:clvm): Started dlm (ocf::pacemaker:controld): Started vm-sim (ocf::lentes:VirtualDomain):Started gfs2_snap (ocf::heartbeat:Filesystem):Started fs_ocfs2(ocf::lentes:Filesystem.new): Started gfs2_share (ocf::heartbeat:Filesystem):Started vm-seneca (ocf::lentes:VirtualDomain):Started vm-ssh (ocf::lentes:VirtualDomain):Started Inactive resources: Clone Set: ClusterMon-clone [ClusterMon-SMTP] Stopped (disabled): [ ha-idg-1 ha-idg-2 ] vm-geneious (ocf::lentes:VirtualDomain):Stopped (disabled) vm-idcc-devel (ocf::lentes:VirtualDomain):Stopped (disabled) vm-genetrap (ocf::lentes:VirtualDomain):Stopped (disabled) vm-mouseidgenes (ocf::lentes:VirtualDomain):Stopped (disabled) vm-greensql (ocf::lentes:VirtualDomain):Stopped (disabled) vm-severin (ocf::lentes:VirtualDomain):Stopped (disabled) ping_19216810010(ocf::pacemaker:ping): Stopped (disabled) ping_19216810020(ocf::pacemaker:ping): Stopped (disabled) vm_crispor (ocf::heartbeat:VirtualDomain): Stopped (unmanaged) vm-dietrich (ocf::lentes:VirtualDomain):Stopped (disabled) vm-pathway (ocf::lentes:VirtualDomain):Stopped (disabled) vm-crispor-server (ocf::lentes:VirtualDomain):Stopped (disabled) vm-geneious-license (ocf::lentes:VirtualDomain):Stopped (disabled) vm-amok (ocf::lentes:VirtualDomain):Stopped (disabled) vm-geneious-license-mcd (ocf::lentes:VirtualDomain):Stopped (disabled) vm-documents-oo (ocf::lentes:VirtualDomain):Stopped (disabled) vm_snipanalysis (ocf::lentes:VirtualDomain):Stopped (disabled, unmanaged) vm-photoshop(ocf::lentes:VirtualDomain):Stopped (disabled) vm-check-mk (ocf::lentes:VirtualDomain):Stopped (disabled) vm-encore (ocf::lentes:VirtualDomain):Stopped (disabled) Migration Summary: * Node ha-idg-1: * Node ha-idg-2: Also a manual "crm resource start" wasn't successfull. Bernd smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On Tue, Aug 23, 2022 at 7:10 PM Lentes, Bernd wrote: > > > > > - On 24 Aug, 2022, at 04:04, Reid Wahl nw...@redhat.com wrote: > > > Can you share your CIB? Not sure off hand what everything means (resource > > not > > found, IPC error, crmd failure and respawn), and pacemaker v1 logs aren't > > the > > easiest to interpret. But perhaps something in the CIB will show itself as > > an > > issue. > > Attached The stop-all-resources cluster property is set to true. Is that intentional? > > > > -- > > Regards, > > > Reid Wahl (He/Him) > > Senior Software Engineer, Red Hat > > RHEL High Availability - Pacemaker -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
- On 24 Aug, 2022, at 04:04, Reid Wahl nw...@redhat.com wrote: > Can you share your CIB? Not sure off hand what everything means (resource not > found, IPC error, crmd failure and respawn), and pacemaker v1 logs aren't the > easiest to interpret. But perhaps something in the CIB will show itself as an > issue. Attached > -- > Regards, > Reid Wahl (He/Him) > Senior Software Engineer, Red Hat > RHEL High Availability - Pacemaker cib.xml Description: XML document smime.p7s Description: S/MIME Cryptographic Signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Cluster does not start resources
On Tuesday, August 23, 2022, Lentes, Bernd < bernd.len...@helmholtz-muenchen.de> wrote: > Hi, > > currently i can't start resources on our 2-node-cluster. > Cluster seems to be ok: > > Stack: corosync > Current DC: ha-idg-1 (version 1.1.24+20210811.f5abda0ee-3.21.9-1.1.24+20210811.f5abda0ee) - partition with quorum > Last updated: Wed Aug 24 02:56:46 2022 > Last change: Wed Aug 24 02:56:41 2022 by hacluster via crmd on ha-idg-1 > > 2 nodes configured > 40 resource instances configured (26 DISABLED) > > Node ha-idg-1: online > Node ha-idg-2: online > > Inactive resources: > > fence_ilo_ha-idg-2 (stonith:fence_ilo2): Stopped > fence_ilo_ha-idg-1 (stonith:fence_ilo4): Stopped > Clone Set: cl_share [gr_share] > Stopped: [ ha-idg-1 ha-idg-2 ] > Clone Set: ClusterMon-clone [ClusterMon-SMTP] > Stopped (disabled): [ ha-idg-1 ha-idg-2 ] > vm-mausdb (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-sim (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-geneious (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-idcc-devel (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-genetrap (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-mouseidgenes (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-greensql (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-severin (ocf::lentes:VirtualDomain):Stopped (disabled) > ping_19216810010(ocf::pacemaker:ping): Stopped (disabled) > ping_19216810020(ocf::pacemaker:ping): Stopped (disabled) > vm_crispor (ocf::heartbeat:VirtualDomain): Stopped (unmanaged) > vm-dietrich (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-pathway (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-crispor-server (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-geneious-license (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-nc-mcd (ocf::lentes:VirtualDomain):Stopped (disabled, unmanaged) > vm-amok (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-geneious-license-mcd (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-documents-oo (ocf::lentes:VirtualDomain):Stopped (disabled) > fs_test_ocfs2 (ocf::lentes:Filesystem.new): Stopped > vm-ssh (ocf::lentes:VirtualDomain):Stopped (disabled) > vm_snipanalysis (ocf::lentes:VirtualDomain):Stopped (disabled, unmanaged) > vm-seneca (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-photoshop(ocf::lentes:VirtualDomain):Stopped (disabled) > vm-check-mk (ocf::lentes:VirtualDomain):Stopped (disabled) > vm-encore (ocf::lentes:VirtualDomain):Stopped (disabled) > > Migration Summary: > * Node ha-idg-1: > * Node ha-idg-2: > > Fencing History: > * Off of ha-idg-2 successful: delegate=ha-idg-1, client=crmd.27356, origin=ha-idg-1, > last-successful='Wed Aug 24 01:53:49 2022' > > Trying to start e.g. cl_share, which is a prerequisite for the virtual domains ... nothing happens. > I did a "crm resource cleanup" (although crm_mon shows no error) hoping this will help ... it didn't. > my command history: > 1471 2022-08-24 03:11:27 crm resource cleanup > 1472 2022-08-24 03:11:52 crm resource cleanup cl_share > 1473 2022-08-24 03:12:45 crm resource start cl_share > (to correlate with the log) > > I found some weird entries in the log after the "crm resource cleanup": > > Aug 24 03:11:28 [27351] ha-idg-1cib: warning: do_local_notify: A-Sync reply to crmd failed: No message of desired type > Aug 24 03:11:33 [27351] ha-idg-1cib: info: cib_process_ping: Reporting our current digest to ha-idg-1: ed5bb7d32532ebf1ce3c45d0067c55b3 for 7.28627.70 (0x15073e0 0) > Aug 24 03:11:52 [27353] ha-idg-1 lrmd: info: process_lrmd_get_rsc_info: Resource 'dlm:0' not found (0 active resources) > Aug 24 03:11:52 [27356] ha-idg-1 crmd: notice: do_lrm_invoke: Not registering resource 'dlm:0' for a delete event | get-rc=-19 (No such device) transition-key=(null) > > What does that mean "Resource not found" ? > > ... > Aug 24 03:11:57 [27351] ha-idg-1cib: info: cib_process_ping: Reporting our current digest to ha-idg-1: 0b3e9ad9ad8103ce2da3b6b8d41e6716 for 7.28628.0 (0x1352bf0 0) > Aug 24 03:11:58 [27356] ha-idg-1 crmd:error: do_pe_invoke_callback: Could not retrieve the Cluster Information Base: Timer expired | rc=-62 call=222 > Aug 24 03:11:58 [27356] ha-idg-1 crmd: info: register_fsa_error_adv: Resetting the current action list > Aug 24 03:11:58 [27356] ha-idg-1 crmd:error: do_log: Input I_ERROR received in state S_POLICY_ENGINE from do_pe_invoke_callback > Aug 24 03:11:58 [27356] ha-idg-1 crmd: warning: do_state_transition: State transition S_POLICY_ENGINE -> S_RECOVERY | input=I_ERROR cause=C_FSA_INTERNAL origin=do_pe_invoke_callback > Aug 24 03:11:58 [27356] ha-idg-1 crmd: warning: do_recover: Fast-tracking shutdown in response to errors > Aug
