...
The main areas that you might need to troubleshoot are the Custos services and Databases. Troubleshooting Custos services are straightforward, you can check the logs from the Kibana server for the Custos namespace, or you can directly log into the particular Pod and check for console logs.
Troubleshooting Services
- check all services are up and running by login to linkered service mesh.
- login to custos master VM
- check all nodes are in ready state.
- kubectl get all nodes
- check all services are up and running
- kubectl get all -n custos
- if not try to redeploy services
- helm delete --purge <<service_name>>
- helm install --name service_name artifacts/<<artifacts_name>> -n custos
Troubleshooting Databases
First, check logs from the Kibana dashboard, or login into the Master and the Slave pods and check for console logs. Most probably it should print errors.
...