Sh Cache Microservice not running after installation
Check that bootstrap and configuration were successful:
[sentinel@shcm1 ~]$ grep 'Bootstrap complete' ~/bootstrap/bootstrap.log 2019-10-28 13:53:54,226 INFO bootstrap.main Bootstrap complete [sentinel@shcm1 ~]$
If the bootstrap.log
does not contain that string, examine the log for any exceptions or errors.
[sentinel@shcm1 ~]$ report-initconf status status=vm_converged [sentinel@shcm1 ~]$
If the status is different, examine the output from report-initconf
for any problems.
If that is not sufficient, examine the ~/initconf/initconf.log
file for any exceptions or errors.
If bootstrap and configuration were successful, check the Rhino journalctl logs.
[sentinel@shcm1 ~]$ journalctl -u rhino -l
Further information can be found from the ShCM logs in /var/log/tas
.
In particular, the Rhino logs are found in a subdirectory of /var/log/tas
with the same
name as the Rhino directory has in the home directory, e.g. gaa-4.0.0.0-cluster-110
.
Rhino Alarms
Not Connected to Cassandra
Node: 101 Level: Critical Type: CassandraCQLRA.ConnectToCluster Message: Not connected to Cassandra. Attempting to connect each 10s
-
Check that the Cassandra server is active on the TSN nodes.
-
Check the network connectivity to the TSN nodes.
-
As TSN nodes are discovered automatically, no further configuration should be necessary. Ensure this node has been provided (as part of its configuration bundle) with the correct SDF for the TSN nodes, as the IP addresses to connect to are derived from this SDF.