On 19/05/17 05:30 PM, Ken Gaillot wrote:
> On 05/19/2017 03:47 PM, Andrew Kerber wrote:
>> What I am trying to say here is when I get one of the virtual machines
>> in a bad state, I can still log in and reboot it with the reboot
>> command. But I need my fencing resource to handle that reboot.
>>
On 05/19/2017 03:47 PM, Andrew Kerber wrote:
> What I am trying to say here is when I get one of the virtual machines
> in a bad state, I can still log in and reboot it with the reboot
> command. But I need my fencing resource to handle that reboot.
>
> On Fri, May 19, 2017 at 1:32 PM, Andrew
Hi,
I have some more information regarding this issue (pacemaker debug logs).
Firstly, I have not mentioned probably important facts:
1) this happen rarely
2) this happen only on first boot
3) turning on debug in corosync/pacemaker significantly reduced frequency
of this happening, i.e. without
Thanks for the answer, but thats not the problem. I dont have access to
the console, its a security issue. I only have access within the virtual
machines, so I want to send the reboot command within the virtual machine,
not to the console. Typically our hangups are such that the reboot command
On 19/05/17 12:59 PM, Andrew Kerber wrote:
> I have been setting up a cluster on virtual machines with some shared
> resources. The only fencing tool I have found designed for that
> configuration is fence virsh, but I have not been able to figure out
> from the documentation how to get
I have been setting up a cluster on virtual machines with some shared
resources. The only fencing tool I have found designed for that
configuration is fence virsh, but I have not been able to figure out from
the documentation how to get fence-virsh to issue the reboot command. Does
anyone have a
On 05/19/2017 04:14 AM, Anu Pillai wrote:
> Hi Ken,
>
> Did you get any chance to go through the logs?
sorry, not yet
> Do you need any more details ?
>
> Regards,
> Aswathi
>
> On Tue, May 16, 2017 at 3:04 PM, Anu Pillai
>