Gabriele, "No route to host" is a somewhat generic error message when we can't find anyone to fence the node. It doesn't mean there's necessarily a network routing issue at fault; no need to focus on that error message.
I agree with Ulrich about needing to know what the script does. But based on your initial message, it sounds like your custom fence agent returns 1 in response to "on" and "off" actions. Am I understanding correctly? If so, why does it behave that way? Pacemaker is trying to run a poweroff action based on the logs, so it needs your script to support an off action. On Tue, Jul 28, 2020 at 2:47 AM Ulrich Windl < [email protected]> wrote: > >>> Gabriele Bulfon <[email protected]> schrieb am 28.07.2020 um 10:56 > in > Nachricht <1330096936.11468.1595926619455@www>: > > Hi, now I have my two nodes (xstha1 and xstha2) with IPs configured by > > Corosync. > > To check how stonith would work, I turned off Corosync service on second > > node. > > First node try to attempt to stonith 2nd node and take care of its > > resources, but this fails. > > Stonith action is configured to run a custom script to run ssh commands, > > I think you should explain what that script does exactly. > > [...] > > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ > > -- Regards, Reid Wahl, RHCA Software Maintenance Engineer, Red Hat CEE - Platform Support Delivery - ClusterHA
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
