Skip to main content
๐Ÿ““ Tibero Online Manual Click here ๐Ÿ““

Search

Welcome to Tibero GTS!

Start Failed Issue After Registering CM Cluster

Document Type | Troubleshooting 

Category | Installation

Applicable Product Versions | 6FS07, 6FS07PS, 7FS02, 7FS02PS

Document Number | TINTS005

 

Issue

After registering the CM Cluster, the cluster start fails due to inability to communicate with the master node.
The CM2 log shows a "No route to host" error, indicating that the master node cannot be accessed.
 

(Issue where start fails due to inability to communicate with the master node after adding cluster to cm on nodes other than the master node)

  • When checking the cm2 log, [ERROR] connect error: No route to host occurs, and logs show that connection to cm1 (Master node) is not possible. 
    (This can be confirmed in the trace_cm.log file located at the path specified by the CM_LOG_DEST parameter in the cm tip file)
 
2025/04/11 11:16:44.005 [1] cm_actio:8961(04) [cls] Cluster `cls` init start
2025/04/11 11:16:44.024 [1] cm_file.:1681(04) [cls] Try to check cluster activity...
2025/04/11 11:16:44.024 [3] cm_netwo:0252(04) [cls] socket fd:16 is set with the priority 2 (conn)
2025/04/11 11:16:44.025 [1] cm_netwo:0300(04) [cls] [ERROR] connect error: No route to host
2025/04/11 11:16:44.025 [1] cm_netwo:0829(04) [cls] [ERROR] Connect to 'cm1(192.168.xx.xx:portno)' failed. No route to host
2025/04/11 11:16:44.025 [1] cm_file.:1302(04) [cls] Cannot connect to master node...
2025/04/11 11:16:44.025 [1] cm_file.:1327(04) [cls] Check CM file heartbeat area...
2025/04/11 11:16:46.054 [1] cm_file.:1681(04) [cls] Try to check cluster activity...
2025/04/11 11:16:46.054 [3] cm_netwo:0252(04) [cls] socket fd:16 is set with the priority 2 (conn)
2025/04/11 11:16:46.056 [1] cm_netwo:0300(04) [cls] [ERROR] connect error: No route to host
2025/04/11 11:16:46.056 [1] cm_netwo:0829(04) [cls] [ERROR] Connect to 'cm1(192.168.xx.xx:portno)' failed. No route to host
2025/04/11 11:16:46.056 [1] cm_file.:1302(04) [cls] Cannot connect to master node...
2025/04/11 11:16:46.056 [1] cm_file.:1327(04) [cls] Check CM file heartbeat area...
2025/04/11 11:16:47.063 [1] cm_file.:1510(04) [cls] [ERROR] check interconnect network interface
2025/04/11 11:16:47.063 [1] cm_actio:9186(04) [cls] [ERROR] Failed to init CM files
2025/04/11 11:16:47.063 [1] cm_actio:7682(04) [cls] all cluster resource down
2025/04/11 11:16:47.063 [1] cm_actio:9475(04) [cls] Cluster 'cls' down

 

Cause

The start failure occurs due to inability to communicate with the master node over the interconnect network.

 

Solutions

  • Check the firewall and access control solutions on the master node server.
  • Verify that interconnect network communication between the two nodes is functioning properly.
Note
Even if ping is successful, this issue may still occur, so it is necessary to verify the ports using telnet.
 
 
 

Related to