[Pacemaker] Resource "ping" fails on passive node after upgrading to second nic

Senftleben, Stefan (itsc) Stefan.Senftleben at ITSC.de
Mon Jan 9 08:01:33 EST 2012

Hello Florian,

okay, I will try to improve in giving better error reports.
That is an error in the corosync log on the active node:
Jan 09 13:49:51 lxds07 crmd: [1360]: info: te_rsc_command: Initiating action 2: stop pri_ping:1_stop_0 on lxds05

"corosync-objctl | grep member" brings no output on the nodes

Here is the dump:

The dump with "cibadmin -Q" does not work on the passive node.
root at lxds05:~# cibadmin -Q
Call cib_query failed (-41): Remote node did not respond

This is the cibadmin dump of the active one:

Last updated: Mon Jan  9 13:57:14 2012
Stack: openais
Current DC: lxds07 - partition with quorum
Version: 1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd
2 Nodes configured, 2 expected votes
6 Resources configured.

Online: [ lxds05 lxds07 ]

 Resource Group: group_omd
     pri_fs_omd (ocf::heartbeat:Filesystem):    Started lxds07
     pri_apache2        (ocf::heartbeat:apache):        Started lxds07
     pri_nagiosIP       (ocf::heartbeat:IPaddr2):       Started lxds07
 Master/Slave Set: ms_drbd_omd
     Masters: [ lxds07 ]
     Slaves: [ lxds05 ]
 Clone Set: clone_ping
     Started: [ lxds07 ]
     Stopped: [ pri_ping:1 ]
omd_main        (ocf::omd:omdnagios):   Started lxds07
res_MailTo_omd_main     (ocf::heartbeat:MailTo):        Started lxds07
res_MailTo_omd_group    (ocf::heartbeat:MailTo):        Started lxds07

Migration summary:
* Node lxds05:
* Node lxds07:  pingd=3000

Thanks for all tips.


More information about the Pacemaker mailing list