Archived Documentation

Welcome to the developer documentation for SigOpt. If you have a question you can’t answer, feel free to contact us!
You are currently viewing archived SigOpt documentation. The newest documentation can be found here.
This feature is currently in alpha. Please contact us if you would like more information.

Debugging

When initially setting up your environment, it can be helpful to have a few debugging commands handy.

Jobs

Firstly, check to see if your Kubernetes Jobs started correctly:

orchestrate kubectl get jobs

Output:

NAME.                          COMPLETIONS   DURATION   AGE
experiment-controller-999999   0/1                      2m22s

If you see Jobs that have 0/1 Completions and no Duration, there's likely an issue with the Job.

You can then get more detailed information about the specific job:

orchestrate kubectl describe jobs/ experiment-controller-999999

This will contain a lot of information about the Job, and list any errors at the bottom.

If the Job has started successfully but you're still not getting results, next check the Pod(s) with a similar process.

Pods

orchestrate kubectl get pods

Output:

NAME                                 READY   STATUS               RESTARTS   AGE
experiment-controller-999999-xxxxx   0/1     ImagePullBackOff     0          5m

A Pod Status such as ImagePullBackOff might indicate an issue with credentials not being properly loaded into Kubernetes, or trying to access the wrong registry.

More detailed information about the Pod and any errors can be queried:

orchestrate kubectl describe pods/ experiment-controller-999999-xxxxx