![]() We can get the resource name from this message output of pcs status * reboot of centos8-2 failed: delegate=, client=pacemaker-controld.1548, origin=centos8-3, We failed reboot node centos8-2 on behalf of pacemaker-controld.1548 from centos8-3 at Sat May 2 14:37:17 2020 We failed reboot node centos8-2 on behalf of pacemaker-controld.1548 from centos8-3 at Sat May 2 14:37:16 2020 We failed reboot node centos8-2 on behalf of pacemaker-controld.1548 from centos8-3 at Sat May 2 14:36:17 2020 We failed reboot node centos8-2 on behalf of pacemaker-controld.1548 from centos8-3 at Sat May 2 14:36:37 2020 We failed reboot node centos8-2 on behalf of pacemaker-controld.1548 from centos8-3 at Sat May 2 14:36:57 2020 Now the pcs status still shows failed action messages for Fencing, so to cleanup failed action messages for fencing we will use " pcs stonith history cleanup "īut before we perform cleanup, we can check the complete history of Failed Fencing Actions using " pcs stonith history show " ~]# pcs stonith history show centos8-2 Solution: Cleanup Failed Actions for Fencing So now we don't have any Failed Resource Actions, next we will cleanup failed action messages for Fencing Last change: Sat May 2 14:39:17 2020 by hacluster via crmd on centos8-4 Similarly to cleanup failed action messages for fence-centos8-2 resource ~]# pcs resource cleanup fence-centos8-4Īfter performing cleanup, check the cluster status ~]# pcs status So to cleanup failed action messages for fence-centos8-2 resource use: ~]# pcs resource cleanup fence-centos8-2 Here the resource name is fence-centos8-2 and fence-centos8-4 which you can also check using " pcs resource status" ![]() You can get the resource name from the Failed Resource Actions message output.īelow is the output from my pcs status * fence-centos8-2_start_0 on centos8-4 'OCF_TIMEOUT' (198): call=122, status=Timed Out, exitreason='', To cleanup failed actions messages for resource under " Failed Resource Actions" use pcs resource cleanup. Solution: Cleanup Failed Actions for Resource The commands to cleanup failed actions for Resource and Fencing are different. Now my resource and fencing resource have started successfully, so I don't need to keep these failed action messages. * reboot of centos8-4 failed: delegate=, client=pacemaker-controld.1548, origin=centos8-3, * reboot of centos8-2 failed: delegate=, client=pacemaker-controld.1548, origin=centos8-3, * fence-centos8-4_start_0 on centos8-4 'OCF_TIMEOUT' (198): call=124, status=Timed Out, exitreason='', ![]() * fence-centos8-2_start_0 on centos8-4 'OCF_TIMEOUT' (198): call=122, status=Timed Out, exitreason='', Online: įence-centos8-3 (stonith:fence_xvm): Started centos8-3įence-centos8-2 (stonith:fence_xvm): Started centos8-2ĬlusterIP (ocf::heartbeat:IPaddr2): Started centos8-4įence-centos8-4 (stonith:fence_xvm): Started centos8-3 Last change: Sat May 2 14:38:23 2020 by root via cibadmin on centos8-2 To check the cluster status: ~]# pcs statusĬurrent DC: centos8-3 (version 2.0.2-3.el8_1.2-744a30d655) - partition with quorum Issue: Cleanup failed action messages from pcs statusīelow I have a sample output from pcs status on my KVM high Availability Cluster, here there are two types of " Failed Actions" So we can clean failed actions from pcs status in such case.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |