Verifying a Local Edition Cluster

  1. On the Kubernetes platform, check the running pods. 
    $ kubectl get pods
  2. Log into the CM container. Use the following command (using a sample ID of 5a527d7ef2ab): 
    $ 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                          Type            Name      Status      Last Heartbeat Received      Host        Service Port(s)            
------------------------------------- --------------- ------ ----------- ----------------------------  ------------ ---------------------------
b38efc8f-bffa-4a68-bcf5-a21370434b78  cache           cache    ACTIVE      Mar 12 2020 08:59:09 +0000  10.0.0.12     11212,11211,11213,11214,11215,11216
f1d75242-4c67-4eb9-a8b3-63195689410c  configmanager   cm       RESOLVED    Mar 12 2020 08:59:25 +0000  10.0.0.6      7080
11261544-ef93-4d1f-8da9-af71b1593763  logservice      log      ACTIVE      Mar 12 2020 08:59:30 +0000  10.0.0.8      24224
66157d26-43b5-40ff-aefe-b1f52aa2f44b  nosql           nosql    ACTIVE      Mar 12 2020 08:59:09 +0000  10.0.0.3      9042
fa66dcbb-35af-4fb3-bc87-09382c0f20ef  sql             sql      ACTIVE      Mar 12 2020 08:59:34 +0000  10.0.0.10     3306
84792b97-b4ba-4a28-b7f4-1b5cfbd6c76a  trafficmanager  tm       STANDBY     Mar 12 2020 08:59:28 +0000  10.0.0.14     8080
  4. 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
  5. 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 is 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"
}
  6. 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.
  7. If the status indicates an error, 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, for example, check the /mnt/data/tml-cm.