CAST IMAGING – V3 – SSO - Error. SSO is not reachable – CAST

SSO failed to start and the error “Error. SSO is not reachable” is seen.

Action Plan

Check disk space.
1. If this has happened after the re-installation of SSO, to recover from another error, then check whether Neo4j has crashed.
  
  When Neo4j crashes, the Java Virtual Machine automatically create a hs_err_pidxxxx.mdmp crash file in the Neo4j_data location. These .mdmp files can be extremely large and can consume the remaining disk space. Neo4j then cannot write further transaction logs, checkpoints and lock files once disk space becomes exhausted. This makes Neo4j to detect unsafe conditions and to enter database quarantine mode. Neo4j stops responding and Imaging cannot connect and as Neo4j is a backend dependency SSO fails.
  1. delete the .mdmp files to free the space,
  2. restart Neo4j using
```
CALL dbms.quarantineDatabase('neo4j',false)
```
  3. restart all the imaging Viewer service
2. Neo4j can also crash due to, memory issue, corrupted transaction logs etc. Please refer Optimize Neo4j disk usage - cleanup and disable JVM crash dumps for the management of Neo4j crash dumps.
Check SSO Logs for Errors.
1. Check if there is any java.io.EOFException error. Check for corrupt installation or realm files, If there are then clean ProgramData/SSO data folder and reinstall SSO.
2. Check if there are any Out of Memory error. If there are then check if heap size in neo4j.conf / Keycloak env variables need to be increased.
3. Check if there is any conflict with another service for sharing the port.
4. Check if there is any issue with initializing SSL context. If there is then check for Invalid certificates, SSL misconfiguration in key paths, proxy settings etc.