got "Failed to get OS information: ssh host down" error when Import Galera Cluster

Follow

Richard

• August 09, 2019 16:40
• Edited

having a Galera Cluster setup on Ubuntu 16.04 , when try to import into clustercontrol, it failed on last step - getting OS information, anyone has same issue?

0

• 

  Richard

  • August 13, 2019 14:37

  anyone has any idea on this issue? here is the job log:

  •  [16:58:56]:
    Adding existing cluster has failed.
  •  [16:58:56]:
    172.24.21.52: Failed to get OS information: ssh host down: .
  •  [16:58:55]:
    172.24.21.52: Checking OS information.
  •  [16:58:55]:
    172.24.21.52:3306: The datadir is /var/lib/mysql/.
  •  [16:58:55]:
    Connected succesfully: 'cmon@172.24.21.191' -> '172.24.21.52:3306'.
  •  [16:58:55]:
    172.24.21.52:3307: The datadir is /var/lib/mysql2/.
  •  [16:58:55]:
    Connected succesfully: 'cmon@172.24.21.191' -> '172.24.21.52:3307'.
  •  [16:58:55]:
    Determining data directories.
  •  [16:58:50]:
    172.24.21.52: Granting cmon.
  •  [16:58:45]:
    172.24.21.52: Granting cmon.
  •  [16:58:45]:
    172.24.21.52:3306: Node is synced.
  •  [16:58:44]:
    172.24.21.52:3307: Node is synced.
  •  [16:58:43]:
    Granting controller (172.24.21.191,hq-dev-64.planetpinnacle.com).
  •  [16:58:43]:
    Controller '172.24.21.191' resolves to 'hq-dev-64.planetpinnacle.com'
  •  [16:58:43]:
    Checking if resolve of '172.24.21.191' is needed, and attempting to resolve to a hostname
  •  [16:58:40]:
    Detected that skip_name_resolve is not used on the target server(s).
  •  [16:58:40]:
    172.24.21.52:3307: skip_name_resolve=mysql: [Warning] Using a password on the command line interface can be insecure.
    skip_name_resolve OFF
  •  [16:58:37]:
    Check SELinux statuses.
  •  [16:58:37]:
    All 2 hosts are accessible by SSH.
  •  [16:58:37]:
    Using sudo password for further communication.
  •  [16:58:37]:
    172.24.21.52: Access with ssh/sudo granted.
  •  [16:58:36]:
    172.24.21.52: Access with ssh/sudo granted.
  •  [16:58:36]:
    Checking ssh/sudo on 2 hosts.
  •  [16:58:36]:
    Checking that nodes are not in another cluster.
  •  [16:58:36]:
    Found in total 2 nodes.
  •  [16:58:36]:
    Found node: '172.24.21.52'
  •  [16:58:36]:
    Found node: '172.24.21.52'
  •  [16:58:36]:
    172.24.21.52: Got empty wsrep_node_address status variable.
  •  [16:58:35]:
    172.24.21.52: Checking wsrep_node_address.
  •  [16:58:35]:
    172.24.21.52: Got empty wsrep_node_address status variable.
  •  [16:58:33]:
    172.24.21.52: Checking wsrep_node_address.
  •  [16:58:32]:
    172.24.21.52:3306: Getting node list from the MySQL server.
  •  [16:58:31]:
    172.24.21.52:3306: Verifying the MySQL user/password.
  •  [16:58:30]:
    Using sudo password for further communication.
  •  [16:58:30]:
    172.24.21.52: Access with ssh/sudo granted.
  •  [16:58:30]:
    172.24.21.52: Checking ssh/sudo.
  •  [16:58:30]:
    Adding existing MySQL cluster.
  •  [16:58:30]:
    Generating configuration for cluster MysqlGaleraCluster.
  •  [16:58:29]:
    Adding cluster with type 'galera', vendor 'percona'.

  0

  Comment actions Permalink
• 

  Sebastian Insausti

  • August 13, 2019 19:17

  Hi Richard,

  The best option here is to create a Support Request and attach an error report to check the issue.

  To generate an error report, on the ClusterControl node, please run the following command:
  $ s9s_error_reporter -i 0

  Then, attach the generated tarball in the new ticket. 

  Thank you.

  Regards,

  Sebastian.

  0

  Comment actions Permalink

Please sign in to leave a comment.