AWS Thinkbox Discussion Forums

machine locked in eternal loop of cancel

Deprecated Deadline 6 Bug Reports
#1

Its been in this state for a couple days it seems:

2013-10-29 14:03:01: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:03:01: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:03:17: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:03:17: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:03:35: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:03:35: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:03:53: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:03:53: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:04:09: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:04:09: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:04:26: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:04:26: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:04:45: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:04:45: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.
2013-10-29 14:05:02: Scheduler Thread - Cancelling task because task “153_1178-1178” could not be found
2013-10-29 14:05:02: Scheduler Thread - The task has either been changed externally (and requeued), or the Job has been deleted.

#2

Found 100 machines like that!! SHIT

#3

What type of job were these slaves running before they ended up in this state? Anything further up the log before they entered this state that might be helpful?

Thanks!

  • Ryan
#4

They all seem to have had a crash window up as well (complaining about a command line we execute pre max startup). Once i clicked OK on those crashes, the slave shut down

#5

You can turn off those windows crash dialogs. That can help avoid blocking issues like this.
blogs.msdn.com/b/alejacma/archiv … ashes.aspx

Privacy | Site terms | Cookie preferences