[Pacemaker] No such device, problem with setting pacemaker

Miha miha at softnet.si
Mon Nov 18 07:59:15 EST 2013


HI,

I am for the first time setting cluster with pacemaker & corosync.
Server A and server B can ping each other, I have disabled selinux and 
iptables but I can not get this going. I did step by step as is writen 
in tutorial.

Here is a error that I am getting it in messeges:

Nov 18 21:36:39 sip2 crmd[13483]:   notice: tengine_stonith_notify: Peer 
sip1.domain.com was not terminated (reboot) by sip2.domain.com for 
sip2.domain.com: No such device 
(ref=ee5d3db1-3c95-4230-8330-a279a03f5f90) by client 
stonith_admin.cman.18267
Nov 18 21:36:39 sip2 fence_pcmk[18266]: Call to fence sip1.domain.com 
(reset) failed with rc=237
Nov 18 21:36:42 sip2 fence_pcmk[18286]: Requesting Pacemaker fence 
sip1.domain.com (reset)
Nov 18 21:36:42 sip2 stonith_admin[18287]:   notice: crm_log_args: 
Invoked: stonith_admin --reboot sip1.domain.com --tolerance 5s --tag cman
Nov 18 21:36:42 sip2 stonith-ng[13479]:   notice: handle_request: Client 
stonith_admin.cman.18287.46738a96 wants to fence (reboot) 
'sip1.domain.com' with device '(any)'
Nov 18 21:36:42 sip2 stonith-ng[13479]:   notice: 
initiate_remote_stonith_op: Initiating remote operation reboot for 
sip1.domain.com: 64a4294f-059a-416f-8e9d-944db759a0e6 (0)
Nov 18 21:36:42 sip2 stonith-ng[13479]:    error: remote_op_done: 
Operation reboot of sip1.domain.com by sip2.domain.com for 
stonith_admin.cman.18287 at sip2.domain.com.64a4294f: No such device
Nov 18 21:36:42 sip2 crmd[13483]:   notice: tengine_stonith_notify: Peer 
sip1.domain.com was not terminated (reboot) by sip2.domain.com for 
sip2.domain.com: No such device 
(ref=64a4294f-059a-416f-8e9d-944db759a0e6) by client 
stonith_admin.cman.18287
Nov 18 21:36:42 sip2 fence_pcmk[18286]: Call to fence sip1.domain.com 
(reset) failed with rc=237


tnx for help!

miha

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131118/239b72af/attachment-0002.html>


More information about the Pacemaker mailing list