Reference Guide

Troubleshooting
This section provides troubleshooting information for Wyse Management Suite version 1.x for the cluster set up.
• Problem: Where is the Wyse Management Suite log le located to check server installation issues.
Workaround: The log le is in the %temp% WMSInstall.logfolder.
• Problem: Where is the Tomcat service related log le located to check the application related issues.
Workaround: If any of the node/server in the cluster does not work and fails to be part of the MySQL cluster do the following:
a Reboot the cluster node and run the command var cluster = dba.rebootClusterFromCompleteOutage(); in the shell prompt.
b Recongure the local instance using the command dba.congureLocalInstance('root@ Server_IPAddress:3306').
c Add the instnce back to the cluster using the command cluster.addInstance('root@Server_IPAddress:3306').
• Problem: If any of the server or node in the cluster stops working and is not part of the MySQL InnoDB cluster.
Workaround: Perform the following steps at the command prompt:
var cluster = dba.rebootClusterFromCompleteOutage(); #Reboot the cluster instance
dba.configureLocalInstance('root@Server_IPAddress:3306') #Reconfigure the local instance
cluster.addInstance('root@Server_IPAddress:3306')#Add the cluster instance back to the network
My-SQL JS> cluster.rejoinInstance(“root@Server_IPAddress”)
• Problem: If the server IDs are same in all the nodes, and if we try adding instances in the Cluster, an error message ERROR: Error
joining instance to cluster is displayed.
Figure 72. Error message
11
78 Troubleshooting