[Pacemaker] display order in crm_mon output
Bauer, Stefan (IZLBW Extern)
Stefan.Bauer at iz.bwl.de
Tue Feb 11 04:23:46 EST 2014
Hi List,
we've recovered a cluster after a failure and used a previously exported cib.xml. Everything is back to normal state.
The strange thing is, that the order in the output of crm_mon is not like before.
Can anyone bring some light into this please? What is affecting the order of the displayed ressources?
Can we rearrange it somehow?
Before the failure:
Resource Group: cluster1
p_bond0 (ocf::heartbeat:IPaddr2): Started node1
p_vlan100 (ocf::heartbeat:IPaddr2): Started node1
p_vlan200 (ocf::heartbeat:IPaddr2): Started node1
p_route (ocf::heartbeat:Route): Started node1
p_conntrackd (lsb:conntrackd-sync): Started node1
Clone Set: pingclone [p_ping]
Started: [ node1 ]
Stopped: [ p_ping:1 ]
p_vpn_B (ocf::heartbeat:anything): Started node1
p_vpn_C (ocf::heartbeat:anything): Started node1
p_vpn_H (ocf::heartbeat:anything): Started node1
p_vpn_K (ocf::heartbeat:anything): Started node1
p_vpn_L1 (ocf::heartbeat:anything): Started node1
p_vpn_LS (ocf::heartbeat:anything): Started node1
p_vpn_M (ocf::heartbeat:anything): Started node1
After the recovery:
p_vpn_H (ocf::heartbeat:anything): Started node1
p_vpn_K (ocf::heartbeat:anything): Started node1
p_vpn_L1 (ocf::heartbeat:anything): Started node1
p_vpn_LS (ocf::heartbeat:anything): Started node1
p_vpn_M (ocf::heartbeat:anything): Started node1
Resource Group: cluster1
p_bond (ocf::heartbeat:IPaddr2): Started node1
p_vlan100 (ocf::heartbeat:IPaddr2): Started node1
p_vlan200 (ocf::heartbeat:IPaddr2): Started node1
p_route (ocf::heartbeat:Route): Started node1
p_conntrackd (lsb:conntrackd-sync): Started node1
Clone Set: pingclone [p_ping]
Started: [ node1 ]
Stopped: [ p_ping:1 ]
p_vpn_B (ocf::heartbeat:anything): Started node1
p_vpn_C (ocf::heartbeat:anything): Started node1
Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140211/32b79ce1/attachment-0002.html>
More information about the Pacemaker
mailing list