Validating a Mashery Local Cluster

You can check the progress of the deployment using the following steps:

  1. Check the running Docker containers by running the following: 
    $ docker ps
  2. Log in to the CM container and check the components and their states. 
    $ docker exec -ti 5a527d7ef2ab bash
  3. Check the status of the overall cluster and see what action is pending. 
    [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
  4. After 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"
}
  5. As seen above, the Traffic Manager has a Ready status despite what the pending activity indicates. The pending activity was the last successful activity performed by the container agent.
  6. If the status indicates error, check the log-service container for corresponding errors.
    1. Log in to the log-service container.
    2. Check the appropriate log files in the folders under the /mnt/data folder.

      For example, to check any errors in the CM container, check the files in the /mnt/data/tml-cm folder.