Troubleshooting Deadline Cloud jobs
For information about common problems with jobs in AWS Deadline Cloud, see the following topics.
Topics
Why did creating my job fail?
Some possible reasons that a job can fail validation checks include the following:
-
The job template doesn't follow the OpenJD specification.
-
The job contains too many steps.
-
The job contains too many total tasks.
-
There was an internal service error that prevents the job from being created.
To see the quotas for the maximum number of steps and tasks in a job, use the Service Quotas console. For more information, see Quotas for Deadline Cloud.
Why is my job not compatible?
Common reasons that jobs are not compatible with queues include the following:
-
No fleets are associated with the queue that the job was submitted to. Open the Deadline Cloud monitor, and check that the queue has associated fleets. For more information about how to view queues, see View queue and fleet details in Deadline Cloud.
-
The job has host requirements that are not satisfied by any of the fleets associated with the queue. To check, compare the
hostRequirementsentry in the job template with the configuration of the fleets in your farm. Make sure that one of the fleets satisfies the host requirements. For more information about fleet compatibility, see Determine fleet compatibility. To view fleet configuration, see View queue and fleet details in Deadline Cloud.
Why is my job stuck in ready?
Possible reasons for your job appearing to be stuck in the READY state
include the following:
-
The maximum worker count for fleets associated with the queue is set to zero. To check, see View queue and fleet details in Deadline Cloud.
-
There is a higher priority job in the queue. To check, see View queue and fleet details in Deadline Cloud.
-
For customer-managed fleets, check the auto scaling configuration. For more information, see Auto scale your Amazon EC2 fleet with Deadline Cloud scale recommendation feature.
Why did my job fail?
A job can fail for many reasons. To search for the issue, open the Deadline Cloud monitor and choose the failing job. Choose a task that failed and then view the logs for the task. For instructions, see View logs in Deadline Cloud.
-
If you see license errors or if you get a watermark that occurs because the software doesn't have a valid license, make sure that the worker can connect to the required license server. For more information, see Connect customer-managed fleets to a license endpoint.
Why is my step pending?
Steps may stay in the PENDING state when one or more of their dependencies
are not complete. You can check the state of dependencies using the Deadline Cloud monitor. For
instructions, see View a step in Deadline Cloud.
