My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

ha-cluster-join fails on syncing configuration files

This document (7020256) is provided subject to the disclaimer at the end of this document.

Environment


SUSE Linux Enterprise High Availability Extension 12
SUSE Linux Enterprise High Availability Extension 11 Service Pack 4
SUSE Linux Enterprise High Availability Extension 11 Service Pack 3
SUSE Linux Enterprise High Availability Extension 11 Service Pack 2

Situation

Building a new Pacemaker cluster with ha-cluster-init/sleha-init succeeds to set up the first node, however adding a new node with ha-cluster-join/sleha-join fails with a csync2 error:

n2:~ # ha-cluster-join
[...]
  IP address or hostname of existing node (e.g.: 192.168.1.1) [] 10.10.1.10
[...]
WARNING: csync2 run failed - some files may not be sync'd
  Merging known_hosts
WARNING: known_hosts collection may be incomplete
WARNING: known_hosts merge may be incomplete
  Probing for new partitions......done
ERROR: /etc/corosync/corosync.conf is not readable. Please ensure that hostnames are resolvable.

Resolution

To resolve this error either add the hostname of the nodes to your DNS server or add them into /etc/hosts on both/all nodes as follows:

cat /etc/hosts
10.10.1.10    n1.example.com    n1
10.10.1.11    n2.example.com    n2

and then re-run the ha-cluster-join script.

Cause

The ha-cluster-join script uses the csync2 tool to sync configuration files across the nodes which uses hostnames instead of IP
addresses:

n1:~ # cat /etc/csync2/csync2.cfg 
group ha_group
{
    key /etc/csync2/key_hagroup;
    host n2;
    host n1;
    include /etc/booth;
    include /etc/corosync/corosync.conf;
    include /etc/corosync/authkey;
    include /etc/csync2/csync2.cfg;
    include /etc/csync2/key_hagroup;
    include /etc/ctdb/nodes;
    include /etc/drbd.conf;
    include /etc/drbd.d;
    include /etc/ha.d/ldirectord.cf;
    include /etc/lvm/lvm.conf;
    include /etc/multipath.conf;
    include /etc/samba/smb.conf;
    include /etc/sysconfig/pacemaker;
    include /etc/sysconfig/sbd;
}

Because it can not resolve hostnames, it fails to sync the cluster configuration files which in turn then leads to the error when
Pacemaker attempts to start corosync.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7020256
  • Creation Date:05-JUN-17
  • Modified Date:06-JUN-17
    • SUSESUSE Linux Enterprise High Availability Extension
< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center