AWS Thinkbox Discussion Forums

Jobs queued but not completed

We are porting database from old server to new server. Before porting, submission of job worked fine. But after porting database, job is only getting submitted. I get job id, but after that it gets queued never completed. Any insight please. Are their any considerations when porting database.

Hello @Nishith_Singhai

If the Workers suddenly stop picking the jobs up I would do the following:

  1. If it is urgent, create a ticket with the word URGENT: at the front if the time is outside of our hotline operational hours else reach out on +1-866-419-028 from 9am – 5pm CST. we will be very happy to help you.
  2. So if the jobs are not dequeued by Worker: first thing to check is if the Worker is allowed to render the job:
  3. Right click the job in question> find render candidates> if there are Workers in able to render list then we need to check the Worker logs
  4. Worker logs can be streamed from the Monitor but if you are looking for verbose information you will need to look at the local application logs found here: The application logs sit here: Logs — Deadline 10.2.1.0 documentation (deadlineslave.log), check if the Worker is idling or has the job but throwing any exceptions.
  5. You can also enable verbose Worker logs: To enable verbose logging of Deadline application configure it from Deadline Monitor> Tools> Configure Repo Options> Application Data (left pane)> check option for verbose logging (bottom right pane)> restart the
Privacy | Site terms | Cookie preferences