Deadlin 8 - Stalled Slave...always...

hi

this is the slave report:

[code]STALLED SLAVE REPORT

Current House Cleaner Information
Machine Performing Cleanup: CROSSHAIR5-PC
Version: v8.0.1.0 Release (a63b4ba06)

Stalled Slave: CROSSHAIR5-PC
Slave Version: v8.0.1.0 Release (a63b4ba06)
Last Slave Update: 2016-06-02 16:03:31
Current Time: 2016-06-02 16:03:49
Time Difference: 18.257 s
Maximum Time Allowed Between Updates: 0.000 s

Current Job Name: test
Current Job ID: 574fe0e9ef6c700eac939343
Current Job User: asus
Current Task Names: 8
Current Task Ids: 8

Searching for job with id “574fe0e9ef6c700eac939343”
Found possible job: test
Searching for task with id “8”
Found possible task: 8:[8-8]
Task’s current slave: CROSSHAIR5-PC
Slave machine names match, stopping search
Associated Job Found: test
Job User: asus
Submission Machine: ASUS-PC
Submit Time: 06/02/2016 09:31:53
Associated Task Found: 8:[8-8]
Task’s current slave: CROSSHAIR5-PC
Task is still rendering, attempting to fix situation.
Requeuing task
Setting slave’s status to Stalled.
Setting last update time to now.

Slave state updated.[/code]

why “Maximum Time Allowed Between Updates” is set to 0.000 s ???
The time of the machine are in syncro and I have set “number of minute before an unresponsive slave is marked on stalled” to 20 minutes…

I have seen thet all the people in this forum in your slave report have “Maximum Time Allowed Between Updates” set to 10 or 20 minutes

for your information I use windows 7 and try to render a sequence of .vrscene with vrayRT standalone 3.30 for 3dsMax
no problem with render process or sending tasks, but very often the slave is stalled during the render of a frame, so the process stop and task is requeued.

I hope you can halp me

regards

up

please…

Can someone help me?

Sorry for the delay here Zac!

The problem here seems to be either that the Slave is crashing, or there are multiple Slaves on the same machine. When the time shows as set to zero, it’s usually because the Slave is stalling itself:

Machine Performing Cleanup: CROSSHAIR5-PC
Stalled Slave: CROSSHAIR5-PC

We should have fixed the multiple Slaves situation, but can you check the process list and see if two are running? Also, check the Slave log folder and check if there are multiple. If it did crash, we’d have created a new one around the time that stalled Slave report was generated. You can find them using this handy page:
docs.thinkboxsoftware.com/produc … ation-logs

hi

thank you for your answer, i hope you can help me to fix this issue

Im testing Deadline 8, for now with one master and one slave

the master, wher is the main repository and the render vraystandalone plugin is named asus-pc and the slave where are GPU cards for render is named crosshair5-pc, the idea is to test workflow for add more slave with gpu

yes, I haved created for error two slave istance on crosshair5-pc but only one istace was running

but now I have erese all slve.ini on C:\ProgramData\Thinkbox\Deadline8\slaves and launced a new slave…same situation, the slave is still stalled randomly whit the same “Maximum Time Allowed Between Updates: 0.000 s”

if there is a slave crush and why I don’t know, and I don’t know how to see this but however I have never seen deadline slave panel shutdown like it was crush

is possible that the Deadline monitor, on master pc, issue?
what about Pulse? Must pulse run on every slave pc? I need pulse to read slave report right?

many many thanks

this is deadlineslave-CROSSHAIR5-PC-2016-06-03-0000.log before to launch any task to render, only open a slave session on crosshair5-pc

2016-06-03 22:17:31: BEGIN - CROSSHAIR5-PC\CROSSHAIR5 2016-06-03 22:17:31: Deadline Slave 8.0 [v8.0.1.0 Release (a63b4ba06)] 2016-06-03 22:17:35: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration 2016-06-03 22:17:36: Plugin sandboxing will not be used because it is disabled in the Repository Options. 2016-06-03 22:17:36: Info Thread - Created. 2016-06-03 22:17:38: Auto Configuration: Picking configuration based on: CROSSHAIR5-PC / 192.168.1.3 2016-06-03 22:17:38: Auto Configuration: No auto configuration could be detected, using local configuration 2016-06-03 22:17:38: Scheduler Thread - Slave initialization complete. 2016-06-03 22:17:38: Scheduler Thread - Performing pending job scan... 2016-06-03 22:17:38: Skipping pending job scan because it is not required at this time 2016-06-03 22:17:38: Scheduler Thread - Performing repository repair... 2016-06-03 22:17:38: Skipping repository repair because it is not required at this time 2016-06-03 22:17:38: Scheduler Thread - Performing house cleaning... 2016-06-03 22:17:38: Skipping house cleaning because it is not required at this time 2016-06-03 22:17:38: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:17:38: Scheduler - Job chooser found no jobs. 2016-06-03 22:17:38: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:17:38: Scheduler - Job chooser found no jobs. 2016-06-03 22:17:39: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:17:46: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:17:46: Scheduler - Job chooser found no jobs. 2016-06-03 22:17:46: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:17:46: Scheduler - Job chooser found no jobs. 2016-06-03 22:17:47: Scheduler Thread - Seconds before next job scan: 6 2016-06-03 22:17:53: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:17:53: Scheduler - Job chooser found no jobs. 2016-06-03 22:17:53: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:17:53: Scheduler - Job chooser found no jobs. 2016-06-03 22:17:54: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:18:01: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:01: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:01: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:01: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:02: Scheduler Thread - Seconds before next job scan: 6 2016-06-03 22:18:08: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:08: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:08: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:08: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:09: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:18:16: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:16: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:16: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:16: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:17: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:18:24: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:24: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:24: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:24: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:25: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:18:32: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:32: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:32: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:32: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:33: Scheduler Thread - Seconds before next job scan: 5 2016-06-03 22:18:38: Scheduler Thread - Performing pending job scan... 2016-06-03 22:18:38: Performing pending job scan 2016-06-03 22:18:38: Pending Job Scan - Loading pending and active jobs 2016-06-03 22:18:38: Pending Job Scan - Loaded 0 pending and active jobs in 10.000 ms 2016-06-03 22:18:38: Pending Job Scan - Done. 2016-06-03 22:18:38: Processing Pending Job Events 2016-06-03 22:18:38: Pending Job Events - Checking for pending job events 2016-06-03 22:18:38: Pending Job Events - Processing 0 job events 2016-06-03 22:18:39: Pending Job Events - No more job events to process 2016-06-03 22:18:39: Pending Job Events - Done. 2016-06-03 22:18:39: Scheduler Thread - Performing repository repair... 2016-06-03 22:18:39: Performing repository repair 2016-06-03 22:18:39: Performing Orphaned Task Scan... 2016-06-03 22:18:39: Orphaned Task Scan - Loading rendering jobs 2016-06-03 22:18:39: Orphaned Task Scan - Loaded 0 rendering jobs in 1.000 ms 2016-06-03 22:18:39: Orphaned Task Scan - Done. 2016-06-03 22:18:39: Performing Orphaned Limit Stub Scan... 2016-06-03 22:18:39: Orphaned Limit Stub Scan - Loading limits 2016-06-03 22:18:39: Orphaned Limit Stub Scan - Loaded 1 limits in 3.000 ms 2016-06-03 22:18:39: Orphaned Limit Stub Scan - Loading slave states 2016-06-03 22:18:39: Orphaned Limit Stub Scan - Loaded 1 slave states in 2.000 ms 2016-06-03 22:18:39: Orphaned Limit Stub Scan - Returned 0 orphaned limit stubs in 5.000 ms 2016-06-03 22:18:39: Orphaned Limit Stub Scan - Done. 2016-06-03 22:18:39: Checking Available Database Connections 2016-06-03 22:18:39: Available Database Connections - Skipping because there are no Low Database Connection notification email addresses set in the Repository Options 2016-06-03 22:18:39: Performing Stalled Slave Scan... 2016-06-03 22:18:39: Stalled Slave Scan - Loading slave states 2016-06-03 22:18:39: Stalled Slave Scan - Loaded 1 slave states in 1.000 ms 2016-06-03 22:18:39: Stalled Slave Scan - Scanning slave states 2016-06-03 22:18:39: Stalled Slave Scan - Cleaned up 0 stalled slaves in 0.000 s 2016-06-03 22:18:39: Stalled Slave Scan - Done. 2016-06-03 22:18:39: Performing Stalled Pulse Scan... 2016-06-03 22:18:39: Stalled Pulse Scan - Loading pulse states 2016-06-03 22:18:39: Stalled Pulse Scan - Loaded 2 pulse states in 1.000 ms 2016-06-03 22:18:39: Stalled Pulse Scan - Scanning pulse states 2016-06-03 22:18:39: Stalled Pulse Scan - Cleaned up 0 stalled pulses in 3.000 ms 2016-06-03 22:18:39: Stalled Pulse Scan - Done. 2016-06-03 22:18:39: Performing Stalled Balancer Scan... 2016-06-03 22:18:39: Stalled Balancer Scan - Loading balancer states 2016-06-03 22:18:39: Stalled Balancer Scan - Loaded 1 balancer states in 7.000 ms 2016-06-03 22:18:39: Stalled Balancer Scan - Scanning balancer states 2016-06-03 22:18:39: Stalled Balancer Scan - Cleaned up 0 stalled balancers in 3.000 ms 2016-06-03 22:18:39: Stalled Balancer Scan - Done. 2016-06-03 22:18:39: Performing Stalled Proxy Server Scan... 2016-06-03 22:18:39: Stalled Proxy Server Scan - Loading Proxy Server states 2016-06-03 22:18:39: Stalled Proxy Server Scan - Loaded 0 Proxy Server states in 2.000 ms 2016-06-03 22:18:39: Stalled Proxy Server Scan - Done. 2016-06-03 22:18:39: Triggering Repository Repair Events 2016-06-03 22:18:39: Scheduler Thread - Performing house cleaning... 2016-06-03 22:18:39: Performing house cleaning 2016-06-03 22:18:39: Performing Job Cleanup Scan... 2016-06-03 22:18:39: Job Cleanup Scan - Loading completed jobs 2016-06-03 22:18:39: Job Cleanup Scan - Loaded 0 completed and 0 active/pending jobs in 2.000 ms 2016-06-03 22:18:39: Job Cleanup Scan - Done. 2016-06-03 22:18:39: Purging Unsubmitted Jobs 2016-06-03 22:18:39: Unsubmitted Job Scan - Loading unsubmitted jobs 2016-06-03 22:18:39: Unsubmitted Job Scan - Loaded 0 unsubmitted jobs in 2.000 ms 2016-06-03 22:18:39: Unsubmitted Job Scan - Done. 2016-06-03 22:18:39: Purging Deleted Jobs 2016-06-03 22:18:39: Deleted Job Scan - Loading deleted jobs 2016-06-03 22:18:39: Deleted Job Scan - Loaded 0 deleted jobs in 2.000 ms 2016-06-03 22:18:39: Deleted Job Scan - Done. 2016-06-03 22:18:39: Purging Old Job Auxiliary Files 2016-06-03 22:18:39: Auxiliary File Scan - Scanning for auxiliary directories 2016-06-03 22:18:39: Auxiliary File Scan - Purged 0 auxiliary folders in 17.001 ms 2016-06-03 22:18:39: Auxiliary File Scan - Done. 2016-06-03 22:18:39: Purging Old Job Reports 2016-06-03 22:18:39: Job Report Scan - Loading job report collections 2016-06-03 22:18:39: Job Report Scan - Found 1 report collections in 7.000 ms 2016-06-03 22:18:39: Job Report Scan - Loading job IDs 2016-06-03 22:18:39: Job Report Scan - Loaded 1 job IDs in 2.000 ms 2016-06-03 22:18:39: Job Report Scan - Purged 0 report collections in 0.000 s 2016-06-03 22:18:39: Job Report Scan - Purging old job report files 2016-06-03 22:18:39: Job Report Scan - Purged 0 report files in 4.000 ms 2016-06-03 22:18:39: Job Report Scan - Done. 2016-06-03 22:18:39: Purging Obsolete Slaves 2016-06-03 22:18:39: Obsolete Slave Scan - Skipping because it is disabled in the Repository Options 2016-06-03 22:18:39: Purging Old Slave Reports 2016-06-03 22:18:39: Slave Report Scan - Loading slave report collections 2016-06-03 22:18:39: Slave Report Scan - Found 1 report collections and 0 job state objects in 5.000 ms 2016-06-03 22:18:39: Slave Report Scan - Loading slave IDs 2016-06-03 22:18:39: Slave Report Scan - Loaded 1 slave IDs in 1.000 ms 2016-06-03 22:18:39: Slave Report Scan - Purged 0 report collections, 0 job state objects, and 0 rendering Slave stubs in 0 2016-06-03 22:18:39: Slave Report Scan - Done. 2016-06-03 22:18:39: Purging Timed Out Slaves in Throttle Queue 2016-06-03 22:18:39: Purging Old Limits 2016-06-03 22:18:39: Old Limit Scan - Loading machine limits 2016-06-03 22:18:39: Old Limit Scan - Found 1 machine limits in 2.000 ms 2016-06-03 22:18:39: Old Limit Scan - Loading job IDs 2016-06-03 22:18:39: Old Limit Scan - Loaded 1 job IDs in 1.000 ms 2016-06-03 22:18:39: Old Limit Scan - Purged 0 machine limits in 0.000 s 2016-06-03 22:18:39: Old Limit Scan - Done. 2016-06-03 22:18:39: Purging Temporary Repository Files 2016-06-03 22:18:39: Temporary File Scan - Scanning for 'connectReadWriteTest' files 2016-06-03 22:18:39: Temporary File Scan - Deleted 0 temporary files in 2.000 ms 2016-06-03 22:18:39: Temporary File Scan - Done. 2016-06-03 22:18:39: Purging Old Statistics 2016-06-03 22:18:39: Old Statistics - Skipping job statistics because the option to purge them is disabled in the Repository Options 2016-06-03 22:18:39: Old Statistics - Purging slave statistics that are older than Feb 04/16 22:18:38 2016-06-03 22:18:39: Old Statistics - Purged old slave statistics in 3.000 ms 2016-06-03 22:18:39: Old Statistics - Purging repository statistics that are older than Feb 04/16 22:18:38 2016-06-03 22:18:39: Old Statistics - Purged old repository statistics in 1.000 ms 2016-06-03 22:18:39: Purging Deleted Document Stubs From Database 2016-06-03 22:18:39: Deleted Document Stubs - Deleting stubs that are older than 3 days 2016-06-03 22:18:39: Deleted Document Stubs - Deleted 0 stubs in 1.000 ms 2016-06-03 22:18:39: Triggering House Cleaning Events 2016-06-03 22:18:39: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:39: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:39: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:39: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:40: Scheduler Thread - Seconds before next job scan: 6 2016-06-03 22:18:46: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:46: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:46: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:46: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:47: Scheduler Thread - Seconds before next job scan: 5 2016-06-03 22:18:52: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:52: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:52: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:52: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:53: Scheduler Thread - Seconds before next job scan: 5 2016-06-03 22:18:58: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:58: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:58: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:18:58: Scheduler - Job chooser found no jobs. 2016-06-03 22:18:59: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:19:06: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:06: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:06: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:06: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:07: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:19:14: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:14: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:14: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:14: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:15: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:19:22: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:22: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:22: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:22: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:23: Scheduler Thread - Seconds before next job scan: 5 2016-06-03 22:19:28: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:28: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:28: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:28: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:29: Scheduler Thread - Seconds before next job scan: 5 2016-06-03 22:19:31: Slave 'CROSSHAIR5-PC' has stalled because it has not updated its state in 4.710 s. Performing house cleaning... 2016-06-03 22:19:31: Could not find associated job for this slave. 2016-06-03 22:19:31: Cannot send notification because the Primary SMTP Server has not been configured in the Repository Options. 2016-06-03 22:19:34: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:34: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:34: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:34: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:35: Scheduler Thread - Seconds before next job scan: 7 2016-06-03 22:19:42: Scheduler Thread - Performing pending job scan... 2016-06-03 22:19:42: Performing pending job scan 2016-06-03 22:19:42: Pending Job Scan - Loading pending and active jobs 2016-06-03 22:19:42: Pending Job Scan - Loaded 0 pending and active jobs in 1.000 ms 2016-06-03 22:19:42: Pending Job Scan - Done. 2016-06-03 22:19:42: Processing Pending Job Events 2016-06-03 22:19:42: Pending Job Events - Checking for pending job events 2016-06-03 22:19:42: Pending Job Events - Processing 0 job events 2016-06-03 22:19:42: Pending Job Events - No more job events to process 2016-06-03 22:19:42: Pending Job Events - Done. 2016-06-03 22:19:42: Scheduler Thread - Performing repository repair... 2016-06-03 22:19:42: Performing repository repair 2016-06-03 22:19:42: Performing Orphaned Task Scan... 2016-06-03 22:19:42: Orphaned Task Scan - Loading rendering jobs 2016-06-03 22:19:42: Orphaned Task Scan - Loaded 0 rendering jobs in 1.000 ms 2016-06-03 22:19:42: Orphaned Task Scan - Done. 2016-06-03 22:19:42: Performing Orphaned Limit Stub Scan... 2016-06-03 22:19:42: Orphaned Limit Stub Scan - Loading limits 2016-06-03 22:19:42: Orphaned Limit Stub Scan - Loaded 1 limits in 0.000 s 2016-06-03 22:19:42: Orphaned Limit Stub Scan - Loading slave states 2016-06-03 22:19:42: Orphaned Limit Stub Scan - Loaded 1 slave states in 1.000 ms 2016-06-03 22:19:42: Orphaned Limit Stub Scan - Returned 0 orphaned limit stubs in 0.000 s 2016-06-03 22:19:42: Orphaned Limit Stub Scan - Done. 2016-06-03 22:19:42: Checking Available Database Connections 2016-06-03 22:19:42: Available Database Connections - Skipping because there are no Low Database Connection notification email addresses set in the Repository Options 2016-06-03 22:19:42: Performing Stalled Slave Scan... 2016-06-03 22:19:42: Stalled Slave Scan - Loading slave states 2016-06-03 22:19:42: Stalled Slave Scan - Loaded 1 slave states in 1.000 ms 2016-06-03 22:19:42: Stalled Slave Scan - Scanning slave states 2016-06-03 22:19:42: Stalled Slave Scan - Cleaned up 0 stalled slaves in 0.000 s 2016-06-03 22:19:42: Stalled Slave Scan - Done. 2016-06-03 22:19:42: Performing Stalled Pulse Scan... 2016-06-03 22:19:42: Stalled Pulse Scan - Loading pulse states 2016-06-03 22:19:42: Stalled Pulse Scan - Loaded 2 pulse states in 1.000 ms 2016-06-03 22:19:42: Stalled Pulse Scan - Scanning pulse states 2016-06-03 22:19:42: Stalled Pulse Scan - Cleaned up 0 stalled pulses in 0.000 s 2016-06-03 22:19:42: Stalled Pulse Scan - Done. 2016-06-03 22:19:42: Performing Stalled Balancer Scan... 2016-06-03 22:19:42: Stalled Balancer Scan - Loading balancer states 2016-06-03 22:19:42: Stalled Balancer Scan - Loaded 1 balancer states in 2.000 ms 2016-06-03 22:19:42: Stalled Balancer Scan - Scanning balancer states 2016-06-03 22:19:42: Stalled Balancer Scan - Cleaned up 0 stalled balancers in 0.000 s 2016-06-03 22:19:42: Stalled Balancer Scan - Done. 2016-06-03 22:19:42: Performing Stalled Proxy Server Scan... 2016-06-03 22:19:42: Stalled Proxy Server Scan - Loading Proxy Server states 2016-06-03 22:19:42: Stalled Proxy Server Scan - Loaded 0 Proxy Server states in 1.000 ms 2016-06-03 22:19:42: Stalled Proxy Server Scan - Done. 2016-06-03 22:19:42: Triggering Repository Repair Events 2016-06-03 22:19:42: Scheduler Thread - Performing house cleaning... 2016-06-03 22:19:42: Performing house cleaning 2016-06-03 22:19:42: Performing Job Cleanup Scan... 2016-06-03 22:19:42: Job Cleanup Scan - Loading completed jobs 2016-06-03 22:19:42: Job Cleanup Scan - Loaded 0 completed and 0 active/pending jobs in 3.000 ms 2016-06-03 22:19:42: Job Cleanup Scan - Done. 2016-06-03 22:19:42: Purging Unsubmitted Jobs 2016-06-03 22:19:42: Unsubmitted Job Scan - Loading unsubmitted jobs 2016-06-03 22:19:42: Unsubmitted Job Scan - Loaded 0 unsubmitted jobs in 0.000 s 2016-06-03 22:19:42: Unsubmitted Job Scan - Done. 2016-06-03 22:19:42: Purging Deleted Jobs 2016-06-03 22:19:42: Deleted Job Scan - Loading deleted jobs 2016-06-03 22:19:42: Deleted Job Scan - Loaded 0 deleted jobs in 1.000 ms 2016-06-03 22:19:42: Deleted Job Scan - Done. 2016-06-03 22:19:42: Purging Old Job Auxiliary Files 2016-06-03 22:19:42: Auxiliary File Scan - Scanning for auxiliary directories 2016-06-03 22:19:42: Auxiliary File Scan - Purged 0 auxiliary folders in 5.000 ms 2016-06-03 22:19:42: Auxiliary File Scan - Done. 2016-06-03 22:19:42: Purging Old Job Reports 2016-06-03 22:19:42: Job Report Scan - Loading job report collections 2016-06-03 22:19:42: Job Report Scan - Found 1 report collections in 1.000 ms 2016-06-03 22:19:42: Job Report Scan - Loading job IDs 2016-06-03 22:19:42: Job Report Scan - Loaded 1 job IDs in 1.000 ms 2016-06-03 22:19:42: Job Report Scan - Purged 0 report collections in 0.000 s 2016-06-03 22:19:42: Job Report Scan - Purging old job report files 2016-06-03 22:19:42: Job Report Scan - Purged 0 report files in 1.000 ms 2016-06-03 22:19:42: Job Report Scan - Done. 2016-06-03 22:19:42: Purging Obsolete Slaves 2016-06-03 22:19:42: Obsolete Slave Scan - Skipping because it is disabled in the Repository Options 2016-06-03 22:19:42: Purging Old Slave Reports 2016-06-03 22:19:42: Slave Report Scan - Loading slave report collections 2016-06-03 22:19:42: Slave Report Scan - Found 1 report collections and 0 job state objects in 1.000 ms 2016-06-03 22:19:42: Slave Report Scan - Loading slave IDs 2016-06-03 22:19:42: Slave Report Scan - Loaded 1 slave IDs in 0.000 s 2016-06-03 22:19:42: Slave Report Scan - Purged 0 report collections, 0 job state objects, and 0 rendering Slave stubs in 0 2016-06-03 22:19:42: Slave Report Scan - Done. 2016-06-03 22:19:42: Purging Timed Out Slaves in Throttle Queue 2016-06-03 22:19:42: Purging Old Limits 2016-06-03 22:19:42: Old Limit Scan - Loading machine limits 2016-06-03 22:19:42: Old Limit Scan - Found 1 machine limits in 1.000 ms 2016-06-03 22:19:42: Old Limit Scan - Loading job IDs 2016-06-03 22:19:42: Old Limit Scan - Loaded 1 job IDs in 1.000 ms 2016-06-03 22:19:42: Old Limit Scan - Purged 0 machine limits in 0.000 s 2016-06-03 22:19:42: Old Limit Scan - Done. 2016-06-03 22:19:42: Purging Temporary Repository Files 2016-06-03 22:19:42: Temporary File Scan - Scanning for 'connectReadWriteTest' files 2016-06-03 22:19:42: Temporary File Scan - Deleted 0 temporary files in 3.000 ms 2016-06-03 22:19:42: Temporary File Scan - Done. 2016-06-03 22:19:42: Purging Old Statistics 2016-06-03 22:19:42: Old Statistics - Skipping job statistics because the option to purge them is disabled in the Repository Options 2016-06-03 22:19:42: Old Statistics - Purging slave statistics that are older than Feb 04/16 22:19:42 2016-06-03 22:19:42: Old Statistics - Purged old slave statistics in 1.000 ms 2016-06-03 22:19:42: Old Statistics - Purging repository statistics that are older than Feb 04/16 22:19:42 2016-06-03 22:19:42: Old Statistics - Purged old repository statistics in 0.000 s 2016-06-03 22:19:42: Purging Deleted Document Stubs From Database 2016-06-03 22:19:42: Deleted Document Stubs - Deleting stubs that are older than 3 days 2016-06-03 22:19:42: Deleted Document Stubs - Deleted 0 stubs in 0.000 s 2016-06-03 22:19:42: Triggering House Cleaning Events 2016-06-03 22:19:43: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:43: Scheduler - Job chooser found no jobs. 2016-06-03 22:19:43: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-06-03 22:19:43: Scheduler - Job chooser found no jobs.

how you can see at this line:

2016-06-03 22:19:31:  Slave 'CROSSHAIR5-PC' has stalled because it has not updated its state in 4.710 s. Performing house cleaning...

if you means that it wase generated a new deadlineslave-CROSSHAIR5-PC-2016-06-03-0000.log when i see a stalled slave report in deadline monitor then no, no new log for stalled slave report…

up…

please…

can I have mongodb issue with windows 7?

Up please…

Samone help me please…

Zac, where are you in the world? Can I maybe give you a call and we can try to sort this out?

I’m in Central time here in North America (GMT-5) and I’m usually around from 9:00am to 5:00pm. You can call me any time at the number in my signature here. Is there one that would work for you?

thanks for your patience, I have 45 still machine, which will remain so if the test on this machine will not work, we are in Italy and unfortunately none of us speak fluent English … you can not understand what could be the problem, based on data I have provided?

I’m going crazy, it seems that the only problem is that, for some reason, the slave can not communicate their status within a certain time limit, but from the slaves report seems to be maximum 0.000 s … ???

we’re even currently testing slave and repository on the same machine. seems to work and start the rendering process, but with the same stall problem…

I appreciate your help

Hey Zac, it seems like there might be a bug with Slaves running housecleaning and thinking they themselves are stalled.

Can you try running Deadline Pulse on one of your machines? It should take sole responsibility for the House Cleaning and Repository Repair processes, which seem to be the source of the bug. I’m hoping this will work around your issue while we try to reproduce and get a fix in on our end.

Cheers,
Jon

I ran pulse , but same error for me
I dont think it will help you zac but you can try anyway
I think problem is in IP address it says 192.168.0.3 for me
but when I’m pinging that address It wont respond

my pc name is T1000 , when I’m pinging T1000 it gives the response
I dont know what to think …

still need help

Can you both try upgrading to 8.0.3? We’re having problems reproducing internally here, so it if comes up after the upgrade, we’ll need to connect and run some tests. My expectation is that a past upgrade might not have gone right, so I’ll have to take a look at file sizes and things like that. We’ll see how things are after 8.0.3 is rolled out.

Ok I will try even now
if you give me an update
It says : To download the installers for Deadline®, please send a request to Thinkbox Sales.
I contacted them today but no link …
can you give an update ?

In terms of upgrading, you can just email sales and they should be getting back to you with a link to your installers. Did you send them an email with the same address you registered with on the forums? If so, I can poke them and see if they can get back to you ASAP. If not, I can still do the same if you PM me the email you did use.

And yeah, as Edwin mentioned, I unfortunately haven’t been able to reproduce this locally, so we might need to get more context from you guys as well – would it be possible to get a full Slave log for the machines that are experiencing this problem? If confidentiality is an issue, you can e-mail it to us directly via the support channel, and it’ll get to me.

If not, Edwin’s suggestion of doing a remote session is still a good one (with either/both of you guys, obviously), should speed up the debugging process since this is obviously a major roadblock. In that regard, Zac, even if your spoken english isn’t the greatest, your written English is perfectly fine – as much as he likes talking, I’m sure Edwin won’t mind typing to communicate either :slight_smile:

Cheers,
Jon

I sent logs to you already
thanks for your help

loooool ))) 8.0.03 rendered job without problems
I will check this thing 10 times today
if it will go without problems I will tell you

first try went well , my frame is rendered
no problems at all