Mashery local configuration problem

[Roberto Perini]

Hi Guru,

I'm running the installation of mashery local 5.1.0 with the following software versions:

VMWARE workstation player 15

docker version 18.09.6

CentOS Linux release 7.5.1804

Type Installation: onpremise swarm on my two VM server centos 7.5, the host is windows 10.

I built the images with the tml-build-docker job as described in the installation guide.

Attached the file manifest-onprem-swarm.json used for service deployment.

The following is the output of the swarm cluster and service list:

[root@master swarm]# docker node ls

ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS ENGINE VERSION

5jjqcj90jtvjso1n68bq4vxtu * master.localdomain Ready Active Leader 18.09.6

v9f9nun6n0waghgz81krc8iyl worker.localdomain Ready Active 18.09.6

[root@master swarm]# docker service ls

ID NAME MODE REPLICAS IMAGE PORTS

nfj9dbvy47qh cachestack_cache replicated 1/1 tml-cache:v5.1.0.3

yime70b4uor8 cmstack_tmlapi replicated 1/1 tml-api:v5.1.0.3 *:7443->7443/tcp

7sbhn86t0o8b cmstack_tmlcm replicated 0/1 tml-cm:v5.1.0.3 *:8080->8080/tcp, *:8443->8443/tcp

v4f7i37cgpw7 logstack_log replicated 1/1 tml-log:v5.1.0.3

wbamcu102k5u nosqlnonseedstack_nosql_nonseed replicated 0/1 tml-nosql:v5.1.0.3

inkly7t62spw nosqlstack_nosql_seed replicated 1/1 tml-nosql:v5.1.0.3

kjtgtmu8hivd sqlstack_sql replicated 1/1 tml-sql:v5.1.0.3

r1menduh04to tmstack_tm replicated 1/1 tml-tm:v5.1.0.3 *:80->80/tcp, *:443->443/tcp, *:8083->8083/tcp

I deployed the services as indicated by the guide, the services all start correctly except cmstack_tmlcm which remains in starting, the log file clustermanager.log has the following message:

time="2019-05-23T12:02:56Z" level=error msg="Cassandra is not ready, Internal Error: {"errorCode":"CASS_NOT_READY","errorMsg":"Cassandra is not ready"}" POD_IP=61beeae9c967 TML_CLUSTER_NAME="Tibco Mashery Local Reference Cluster" TML_ZONE_NAME=local function=clustermanager process=clustermanager

The cassandra service is up and listening on port 7000 on docker nosqlstack_nosql_seed.

 

Can you help me solve this problem

[Ankit Golwalkar]

Try restarting the jetty service and cassandra service inside the nosql container. Hope this will help.