Debug

Edit online

The following are some scenarios on how you may debug an issue while deploying SevOne Data Insight.

  Question Description / Commands
1. Are you logged in as root or sevone user? All commands must be run as sevone user.
2. If you are performing a fresh deployment, have you checked that there are no IP-range conflicts. Please refer to SevOne Data Insight Pre-Installation Guide > section Private IP Address Ranges for details on IP address ranges.
3. How can SevOne Data Insight, Kubernetes, Helm, SOA, and SevOne NMS application versions be obtained? Execute the following command(s).
On SevOne Data Insight machine, 

$ kubectl exec -it deploy/di-ui -- cat /GITINFO.json
 
$ kubectl version o --short
 
$ helm version

On SevOne NMS appliance,

$ docker ps | grep soa
4. Is the Kubernetes cluster healthy? Execute the following commands. 

$ kubectl get nodes
 
$ kubectl get pods
 
$ kubectl get pods -n=kube-system
5. How can the application logs for a suspected pod be obtained? Execute the following command(s).
On SevOne Data Insight machine, 

$ kubectl logs deploy/di-graphql --tail 100

On SevOne NMS appliance, 

# Using a text editor of your choice, you can find the logs in /var/log/soa.log
 
$ vi /var/log/soa.log
6. How can traces for the request be obtained if it involves retrieving data from SevOne NMS? Execute the following command(s). On SevOne NMS appliance, 

$ supervisorctl start jaeger
 
<Trigger the event to happen in SevOne Data Insight>
 
$ /usr/local/bin/jaeger
7. If an issue can be reproduced in the User Interface, how can the HAR output of the network responses be captured? The HTTP Archive format (HAR) output of the network responses can be found in the Network tab of Chrome inspector. 

$ kubectl logs deploy/di-printer
 
$ kubectl logs deploy/di-scheduler
 
$ kubectl logs deploy/di-graphql
8. What should you do if an issue is related to the User Interface? You must collect the console logs from your browser.
9. What should you do if issues are related to the PDF files? You must collect the logs from the printer, scheduler, and GraphQL containers.