Hi, On Tue, Jul 11, 2017 at 11:13 AM, ArekW <[email protected]> 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 > successfully. > After an un-succesful attempt to monitor, your settings my attempt to do next attempt. In some cases, second ssh connection may be much faster. So second attempt will success more often. > I described a active-active failover problem in separate mail. When a node > is poweroff the cluster enters UNCLEAN status and whole thing hungs. Could > it be related to stonith problem? I'm out of ideas what is wrong because I > seems to work manually but seems not to work as a fence process. > How can I increase the login_timeout (Is it for stonith?) > add login_timeout=XXs (or look at manual pages for other timeout options) m, > Thanks > Arek > > 2017-07-10 13:10 GMT+02:00 Marek Grac <[email protected]>: > >> >> >> On Fri, Jul 7, 2017 at 1:45 PM, ArekW <[email protected]> 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 >> similary new version of pcs (with the commit 7f85340b7aa4e8c016720012cf42c3 >> 04e68dd1fe) >> >> >>> >>> I have selinux disabled on both nodes: >>> [root@nfsnode1 ~]# cat /etc/sysconfig/selinux >>> SELINUX=disabled >>> >>> pcs stonith update vbox-fencing verbose=true >>> Error: resource option(s): 'verbose', are not recognized for resource >>> type: 'stonith::fence_vbox' (use --force to override) >>> >> >> It shoulbe fixed in commit b47558331ba6615aa5720484301d644cc8e973fd (Jun >> 12) >> >> >>> >>> >> >>> >>> Jul 7 13:37:49 nfsnode1 fence_vbox: Unable to connect/login to fencing >>> device >>> Jul 7 13:37:49 nfsnode1 stonith-ng[2045]: warning: fence_vbox[4765] >>> stderr: [ Running command: /usr/bin/ssh -4 [email protected] -i >>> /root/.ssh/id_rsa -p 22 -t '/bin/bash -c "PS1=\\[EXPECT\\]#\ /bin/bash >>> --noprofile --norc"' ] >>> >> >> ok, so sometimes it works and sometimes not. It looks like that our >> timeouts are set quite strict for your environment. Try to increase >> login_timeout from default 30s higher. >> >> m, >> >> _______________________________________________ >> Users mailing list: [email protected] >> http://lists.clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> >> > > _______________________________________________ > Users mailing list: [email protected] > http://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > >
_______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
