Verifying a Mashery Local Cluster

  1. On the Kubernetes platform, check the running pods. 
    $ kubectl get pods
  2. Log in to the CM container. For a sample ID 5a527d7ef2ab , use the command as below: 
    $ kubectl exec -ti 5a527d7ef2ab bash
  3. Log in to the CM container and check the components and their states. 
    [root@5a527d7ef2abbuilder]#
[root@5a527d7ef2abbuilder]# alias cm=clustermanager
[root@5a527d7ef2abbuilder]# cm ls components
Using cluster [Tibco Mashery Local Reference Cluster]
Using Zone [local]
Component ID                          Component Type       Component Name       Component Status     Component Host       Component Agent Port   Component Service Port(s)
------------------------------------- -------------------- -------------------- -------------------- -------------------- ---------------------- ---------------------------
b38efc8f-bffa-4a68-bcf5-a21370434b78  cache                cache                ACTIVE               10.0.0.12908011212,11211,11213,11214,11215,11216
f1d75242-4c67-4eb9-a8b3-63195689410c  configmanager        cm                   RESOLVED             10.0.0.690807080
11261544-ef93-4d1f-8da9-af71b1593763  logservice           log                  ACTIVE               10.0.0.8908024224
66157d26-43b5-40ff-aefe-b1f52aa2f44b  nosql                nosql                ACTIVE               10.0.0.390809042
fa66dcbb-35af-4fb3-bc87-09382c0f20ef  sql                  sql                  ACTIVE               10.0.0.1090803306
84792b97-b4ba-4a28-b7f4-1b5cfbd6c76a  trafficmanager       tm                   STANDBY              10.0.0.1490808080
  4. Follow the checks described in LINK.
  5. Check the status of the overall cluster and the pending action. 
    [root@5a527d7ef2abbuilder]# cm cluster status
*** Checking the status of Cluster 'Tibco Mashery Local Reference Cluster'***
*** Checking the status of zone 'local'***
TML component [66157d26-43b5-40ff-aefe-b1f52aa2f44b] of type [nosql] found with status [ACTIVE] on Host IP [10.0.0.3]..
TML component [11261544-ef93-4d1f-8da9-af71b1593763] of type [logservice] found with status [ACTIVE] on Host IP [10.0.0.8]..
TML component [fa66dcbb-35af-4fb3-bc87-09382c0f20ef] of type [sql] found with status [ACTIVE] on Host IP [10.0.0.10]..
TML component [b38efc8f-bffa-4a68-bcf5-a21370434b78] of type [cache] found with status [ACTIVE] on Host IP [10.0.0.12]..
TML component [84792b97-b4ba-4a28-b7f4-1b5cfbd6c76a] of type [trafficmanager] found with status [STANDBY] on Host IP [10.0.0.14]. See details below
Component ID                          Component Name       Component IP         Component Status     Pending Activity     Error
------------------------------------- -------------------- -------------------- -------------------- -------------------- ------------------------------
84792b97-b4ba-4a28-b7f4-1b5cfbd6c76a  tm                   10.0.0.14Not Ready
  6. In some time, the cluster status should turn READY. You can check the last failing component for its individual status as follows. In this case the Traffic Manager running on 10.0.0.14 IP. 
    [root@5a527d7ef2abbuilder]# curl http://10.0.0.14:9080/container/status
{
  "tmgcId": "84792b97-b4ba-4a28-b7f4-1b5cfbd6c76a",
  "ip": "10.0.0.14",
  "name": "tm",
  "pending_activity": "checking component status ...",
  "status": "Ready"
}
  7. As seen above, the Traffic Manager is in ready status despite what the pending activity indicates. The pending activity was the last successful activity performed by the container agent.
  8. If the status indicates error, then please check the log-service container for corresponding errors.
    • Log in to the logservice container
    • Check the appropriate log files under the "/mnt/data" location
    • Check for errors in the CM container, as example, check the "/mnt/data/tml-cm" location.