>>> Andrei Borzenkov <arvidj...@gmail.com> schrieb am 03.08.2019 um 18:17 in Nachricht <35a226a8-115b-4dc0-f505-dbd78cdd7...@gmail.com>: > I'm using sbd watchdog and stonith‑watchdog‑timeout without explicit > stonith agents (shared nothing cluster). How can I clean up failed > fencing action? > > Current DC: ha1 (version > 2.0.1+20190408.1b68da8e8‑1.3‑2.0.1+20190408.1b68da8e8) ‑ partition with > quorum > Last updated: Sat Aug 3 19:10:12 2019 > Last change: Sat Aug 3 19:04:56 2019 by hacluster via crmd on ha1 > > 2 nodes configured > 7 resources configured > > Online: [ ha1 ha2 ] > > Active resources: > > A (ocf::heartbeat:Dummy): Started ha1 > B (ocf::heartbeat:Dummy): Started ha1 > C (ocf::heartbeat:Dummy): Started ha1 > D (ocf::heartbeat:Dummy): Started ha1 > E (ocf::heartbeat:Dummy): Started ha1 > F (ocf::heartbeat:Dummy): Started ha1 > > Failed Fencing Actions: > * reboot of ha2 failed: delegate=, client=pacemaker‑controld.1910, > origin=ha1, > last‑failed='Sat Aug 3 18:54:13 2019' > > crm_resource requires resource which does not exist.
I'd say manual reboot of ha2 should clean up the situation ;-) But why did fenciong fail? > _______________________________________________ > 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/