Am Mittwoch, 23. Oktober 2013, 12:39:35 schrieb Beo Banks: > hi, > > thanks for answer. > > the pacemaker|corosync is running on both nodes. > > [chkconfig | grep corosync > corosync 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus > chkconfig | grep pacemaker > pacemaker 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
Looks good. What does the log of the boot say? Any signs of corosync? > @ssh key > no, i created the keys without passphrase. > maybe the config is wrong but i have checked a lot times and i can´t find > any issue. Is the key readable for the user that executes the fencing command? host list correct? How does the fencing agent know to fence "host2" (see your command line). How does it know what IP address to use? Is your /etc/hosts correct? > btw. your book "clusterbau: hochverfügbarkeit mit linux version3" is very > helpfull. Thanks. If your like it, you could write a 5-star review at amazon! > btw. selinux is disabled and iptables can´t be the reason because > fence_virsh works via commandline,or? it uses the virsh communication. It depends how you did set it up, but normally you use SSH. But see your setup. Mit freundlichen Grüßen, Michael Schwartzkopff -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
