Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

Adding login_timeout=30 solved the stonith problem. Thank you very much! Pozdrawiam, Arek 2017-07-11 13:06 GMT+02:00 Marek Grac : > Hi, > > On Tue, Jul 11, 2017 at 11:13 AM, ArekW wrote: > >> Hi, >> I may be wrong but it doesn't seem to be timeout problem

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

Hi, On Tue, Jul 11, 2017 at 11:13 AM, ArekW wrote: > Hi, > I may be wrong but it doesn't seem to be timeout problem because the log > repeats the same way every few minutes and it contains "Unable to connect" > and just after that there is list of vms etc so It has connected

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

Hi, I may be wrong but it doesn't seem to be timeout problem because the log repeats the same way every few minutes and it contains "Unable to connect" and just after that there is list of vms etc so It has connected successfully. I described a active-active failover problem in separate mail. When

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

On Fri, Jul 7, 2017 at 1:45 PM, ArekW wrote: > The reason for --force is: > Error: missing required option(s): 'ipaddr, login, plug' for resource > type: stonith:fence_vbox (use --force to override) > It looks like you use unreleased upstream of fence agents without a

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

The reason for --force is: Error: missing required option(s): 'ipaddr, login, plug' for resource type: stonith:fence_vbox (use --force to override) I have selinux disabled on both nodes: [root@nfsnode1 ~]# cat /etc/sysconfig/selinux SELINUX=disabled pcs stonith update vbox-fencing verbose=true

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

On 07/07/17 10:07 +0200, Marek Grac wrote: Hi, On Fri, Jul 7, 2017 at 8:02 AM, ArekW wrote: Hi, I did a small research on the scripts /usr/sbin/fence_vbox def main(): ... conn = fence_login(options) The fence_loging is scripted in the fencing.py and it should invoke

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

Hi, On Fri, Jul 7, 2017 at 8:02 AM, ArekW wrote: > Hi, > I did a small research on the scripts > > /usr/sbin/fence_vbox > def main(): > ... > conn = fence_login(options) > > The fence_loging is scripted in the fencing.py and it should invoke > function:

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

Hi, I did a small research on the scripts /usr/sbin/fence_vbox def main(): ... conn = fence_login(options) The fence_loging is scripted in the fencing.py and it should invoke function: _login_ssh_with_identity_file /usr/share/fence/fencing.py def _login_ssh_with_identity_file: ... command = '%s

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

On 07/06/2017 10:29 AM, Ken Gaillot wrote: > On 07/06/2017 10:13 AM, ArekW wrote: >> Hi, >> >> It seems that my the fence_vbox is running but there are errors in >> logs every few minutes like: >> >> Jul 6 12:51:12 nfsnode1 fence_vbox: Unable to connect/login to fencing >> device >> Jul 6

Re: [ClusterLabs] fence_vbox Unable to connect/login to fencing device

On 07/06/2017 10:13 AM, ArekW wrote: > Hi, > > It seems that my the fence_vbox is running but there are errors in > logs every few minutes like: > > Jul 6 12:51:12 nfsnode1 fence_vbox: Unable to connect/login to fencing device > Jul 6 12:51:13 nfsnode1 stonith-ng[7899]: warning:

[ClusterLabs] fence_vbox Unable to connect/login to fencing device

Hi, It seems that my the fence_vbox is running but there are errors in logs every few minutes like: Jul 6 12:51:12 nfsnode1 fence_vbox: Unable to connect/login to fencing device Jul 6 12:51:13 nfsnode1 stonith-ng[7899]: warning: fence_vbox[30220] stderr: [ Unable to connect/login to fencing