On 5 October 2010 22:12, Mike A Meyer <mme...@cds-global.com> wrote: > We are setup in a two node active/passive cluster using pacemaker/corosync. > We shutdown the pacemaker/corosync on both nodes and changed the uname -n > on our nodes to show the short name instead of the FQDN. Started up > pacemaker/corosync and ever since we done that, when we run the crm_mon > command, we see this below. > > ============ > Last updated: Tue Oct 5 13:28:16 2010 > Stack: openais > Current DC: e-magdb2 - partition with quorum > Version: 1.0.9-89bd754939df5150de7cd76835f98fe90851b677 > 4 Nodes configured, 2 expected votes > 2 Resources configured. > ============ > > Online: [ e-magdb2 e-magdb1 ] > OFFLINE: [ e-magdb1.testingpcmk.com e-magdb2.testingpcmkr.com ] > > We did edit the crm configuration file to use short names for both nodes. > We can ping both the short name and the FQDN on our internal network and > both come back with the right IP address. We are running on RHEL 5. > Anybody have any ideas why the FQDN shows offline since this change since > we configured pacemaker/corosync to use short names? Is it grabbing it from > internal DNS from the IP address we have in the /etc/corosync.conf file? > Everything seems to be working correctly and failing over correctly. > Should this be something to worry about though or is it a display bug > maybe? Below is the corosync.conf file. >
Did you follow this[1] procedure? Changing the names on the conf file of corosync it not enough. [1] http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-node-delete.html
_______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker