Depending on the error message, the next steps should be quite clear, here are a few examples:

"Resource download failed: Invalid credentials given for docker registry": check the ![constant](constant) DOCKER_REPO is properly filled, and if it is a private repository, check that your povided correct credentials. More information in #[/choosing-your-software/bring-your-software-with-docker/off-the-shelf-docker-images](the Off the shelf Docker images section) and in #[/how-to/docker-how-to/custom-docker-images](the Custom Docker images section). We recommend using #[/how-to/docker-how-to/push-image-to-qarnot-registry](Qarnot Containers Registry) to store Container Images
"You ran out of credits": add credits to your ![account](account).
"Internal error" refers to an error inside the computation, if this is your error code, you should follow the next points.

3. Check the computation logs

On Tasq, click on your task and go through the STDOUT and STDERR tabs to find the source of the error.

Tasq - STDOUT

If your logs are not precise enough and you are the developer of the script, you must increase the quantity of logs in order to know exactly the root cause of the error and to fix it.

If your logs are not precise enough and you are not the developer of the script:

if it is a famous software, try to find similar errors on the internet.
otherwise, try to get in touch directly with the developers of the project.

Here are a few basic errors to be careful with:

your inputs are not in the path you expect. By default, in Qarnot, your input bucket will be available in /job.
your connection is not the one you expect. In order to optimize security, some profiles don't have access to the internet. That's the case for docker-batch and many others. Check the profile you chose has the right accesses: more information in the #[/how-to/sdk-how-to/choosing-the-right-profile](Choosing the right profile) guide or the #(choosing-your-software/bring-your-software-with-docker/docker)[Docker profile description] article

{{alert type="info" content="The STDOUT and STDERR are fetched as best effort. If you want to get all the logs of your computation, you must take care of writing them in an output file and to upload this output file: check our example in the #[/monitoring-debugging/debug-your-payloads/fetching-logs](Fetching logs section)."}}

4. Step by step tests

Logs always give a good idea of what the error is, but testing in a simpler environment can complement this information. The best practice in this case is to remove layers of complexity: start with the simplest environment and add layers until the error appears, it will give you important clues to understand where the error comes from:

Launch your computation on your local laptop.
Launch your computation on a container with access to the terminal.
1. If your local input files are in an inputs/ folder, it will look like this:
  docker run -it --rm -v inputs:/job <<<MY-DOCKER-REPO>>> /bin/bash
2. you can then launch manually your computation, from within the container:
  python3 my_script.py for instance
Launch your computation in a container:
docker run --rm -v inputs:/job <<<MY-DOCKER-REPO>>> python3 my_script.py
Launch your computation on Qarnot.

If you still cannot solve your problem, send an email to our support team: support-compute@qarnot-computing.com.

Related Article

For more information on Monitoring and debugging please consult the following articles

#[/core-concepts/tasks](Tasks Core Concept): which describes how tasks behave and their status
#[/how-to/sdk-how-to/monitoring-resources](Monitoring Resources)
#[monitoring-debugging/monitor-computations/with-the-web-ui](Monitor your computations with the Web UI)
#[monitoring-debugging/monitor-computations/with-a-sdk](Monitor your computations with a SDK)
#[/monitoring-debugging/debug-your-payloads/fetching-logs](Fetching logs)
#[/monitoring-debugging/debug-your-payloads/error-codes](Error Codes)

Troubleshooting

Any feedback on this page ?