Troubleshoot

Note: All commands must be run in a terminal on the DMC host system.

Troubleshooting commands

To get troubleshooting tips for the DMC:

sudo datical-control troubleshoot

To tail the output of the Datical Service log file:

sudo datical-control logs datical-service --follow

To tail the output of the proxy service process log file:

sudo datical-control logs proxy --follow

Keycloak login:

username: keycloak-admin

password: datical

To view logs:

sudo datical-control logs datical-service > servicelog.txt
sudo datical-control logs keycloak > keycloaklog.txt
sudo datical-control logs proxy > proxylog.txt

To stop all services (demo mode only):

sudo datical-control service stop ALL

If you are using an external/production mode postgres database, expect to see the error below. This appears to prevent the proxy and possibly other services from restarting.

Failed to stop datical-postgresql.service: Unit datical-postgresql.service not loaded. Command Failed: Error executing shell `systemctl stop datical-postgresql.service` . See output for details

To start all services (demo mode only):

sudo datical-control service start ALL

To start all services (production mode):

sudo datical-control service start keycloak
sudo datical-control service start datical-service
sudo datical-control service start proxy

To stop all services (production mode):

sudo datical-control service stop proxy
sudo datical-control service stop datical-service
sudo datical-control service stop keycloak

To see commands:

sudo datical-control
sudo datical-control service

Display status and version information commands

To display the status of the Datical Service process and the DMC version information:

sudo datical-control service status datical-service

 

Locate datical-service* files

sudo find /etc/ -name datical-service*

Related links