}}

DC/OS offers several tools to debug your services when they are stuck in deployment or are not behaving as you expect. This topic discusses how to debug your services using both the DC/OS CLI and the DC/OS web interface.

Stuck Deployments

How Offer Matching Works DC/OS services or pods may fail to deploy because the Mesos resource offers are unable to match the resources requests coming from the service or pods Mara...

Granting Access to dcos task exec

You can grant users access to containers for debugging sessions. Prerequisites: You must have the DC/OS CLI installed and be logged in as a superuser. A user account to assign perm...

Debugging from the DC/OS CLI

The DC/OS CLI provides commands to debug services that are not deploying or behaving as expected. To see full logs, append --log-level=debug to any DC/OS CLI command. For example, ...

Using dcos task exec

The dcos task exec command allows you to execute an arbitrary command inside of a task’s container and stream its output back to your local terminal to learn more about how a...

Debugging from the DC/OS Web Interface

You can debug your service or pod from the DC/OS web interface. Service and Pod Health and Status Summaries If you have added a Marathon health check to your service or pod, the Se...