Sh Cache Microservice not running after installation
If the Sh Cache Microservice is not running after the installation steps, first check that bootstrap and initial 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 initital configure were successful, check the Rhino journalctl logs.
[sentinel@shcm1 ~]$ journalctl -u rhino -l
Further information can be found from the Sh Cache Microservice logs in /var/log/tas.
Rhino Alarms
Not Connected to Cassandra
Alarm 101:230435607984642 [CassandraCQLRA.ConnectToCluster]
Rhino node : 101
Level : Critical
InstanceID : cassandra-cql-ra
Source : (RA Entity) cassandra-cql-ra
Timestamp : 20190207 23:15:14 (active 8m 3s)
Message : Not connected to Cassandra. Attempting to connect each 10s-
Check that the Cassandra server is active.
-
Check the network connectivity to the Cassandra host and port. To identify the hostname check via
rhino-console> listraentityconfigproperties cassandra-cql-ra
-
For further information turn on ra tracing via
rhino-console> settracerlevel resourceadaptorentity cassandra-cql-ra root Finest
Tracing is logged in the file /var/log/tas/[shcm-release]/rhino.log.
Connection to SAS server is down
Alarm 101:230435607984641 [rhino.sas.connection.lost]
Rhino node : 101
Level : Major
InstanceID : Facility=SasFacility, host=localhost, port=6761
Source : (Subsystem) SasFacility
Timestamp : 20190207 23:15:14 (active 8m 4s)
Message : Connection to SAS server at localhost:6761 is down-
Check that SAS is active.
-
Check the network connectivity to the SAS server host and port.
Diameter Peer is down
Alarm 101:230435607984643 [diameter.peer.connectiondown]
Rhino node : 101
Level : Warning
InstanceID : diameter.peer.localhost
Source : (RA Entity) diameter-sh-ra
Timestamp : 20190207 23:15:15 (active 8m 3s)
Message : Connection to localhost:3888 is down-
Check the network connectivity to the Diameter peer host and port.
rhino-console> listraentityconfigproperties cassandra-cql-ra
-
For further information turn on ra tracing via
rhino-console> settracerlevel resourceadaptorentity diameter-sh-ra root Finest
Tracing is logged in the file /var/log/tas/[shcm-release]/rhino.log.
