Host already in another Cluster

Follow

Comments

4 comments

  • Avatar
    Colby Adkins

    @rainbow obby You may need to repeat the deleting process for each hostname/IP of the cluster you are attempting to add.

    0
    Comment actions Permalink
  • Avatar
    Richard Hayes

    In the scenario where the "Add Existing Cluster" job encounters an error stating, "Host 1.2.3.4:nnnn is already in another cluster," several steps can be taken to resolve the issue. First, check for the existence of the /etc/cmon.d/cmon_X.cnf file containing the hostname and remove it if found. Next, delete the host from the server_node, mysql_server, and hosts tables in the cmon database. Afterward, restart cmon using the command "service cmon restart." It's essential to replace '1.2.3.4' with the actual IP address, and exercise caution not to delete the wrong cmon_X.cnf file. Execute deletions multiple times if needed. For an equally seamless experience, explore Bitstarz for online gaming

    0
    Comment actions Permalink
  • Avatar
    Richard Andrews

    In order to address the common issue of a host already being part of another cluster, as outlined in Severalnines' detailed guide, users may also explore alternative software solutions such as the Remini Mod APK for enhancing their system management experience.

    0
    Comment actions Permalink
  • Avatar
    dryfirewood

    YOU ARE ALWAYS LIKE THIS!

    try it  -> https://fnfunkin.onl/

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk