Troubleshooting procedure

This page’s purpose is to give some basic recommendations to troubleshoot frequently encountered issues with Cyberwatch.

The application is not starting

This procedure can be useful if the application is not starting after the execution of cyberwatch configure or cyberwatch restart:

Check if the services are running:
```
sudo cyberwatch status
```
Check if the images are present:
```
docker images
```
Check the docker pull:
```
docker pull harbor.cyberwatch.fr/cbw-on-premise/olympe:latest
```
Any problem during the docker pull can result from:
- invalid authentication on harbor.cyberwatch.fr
- no space left on device
- no flow to harbor.cyberwatch.fr
Check the applied configuration:
```
sudo cyberwatch show-config
```
An error indicates an invalid override file in the /etc/cyberwatch/configs-enabled directory, for example an override targeting a service that is not present on the node.

Since version 5.32 of the orchestrator base, if downloading the new images fails, the cyberwatch restart command displays a warning and restarts the application with the images already present on the node. The application is then not updated. Fix the cause of the problem, then run sudo cyberwatch restart again.

Kibana is broken

For serious problems with elastic or kibana it is possible to erase all data and restart from scratch.

sudo cyberwatch stop
docker volume rm cbwonpremise_esdata
sudo cyberwatch restart

The job in charge of populating the data will be triggered after restart.