Hey,
I know I should’ve tried Deadline 5 beta first before posting this 4.1 issue, but unfortunately the current projects don’t allow us to switch to a Beta right now 
So, what I came across when using a MacPro running Win7 64Bit via Bootcamp is that Deadline show tasks running only for a few minutes as if they were running 9hrs. As a result, the slave gets stalled and the task is requeued while rendering 
Is there a possibility to disable “stalling”? I’d assume then he’d render just fine.
Thanks & best regards
Dziga
Edit: forgot to post the log
[code]=======================================================
Error Message
STALLED SLAVE REPORT
Current House Cleaner Information
Machine Performing Cleanup: Mg01
Version: v4.1.0.43205 R
Stalled Slave: Fcp02_7
Last Slave Update: 2011-01-31 07:12:07
Current Time: 2011-01-31 16:12:23
Time Difference: 9.001 hrs
Maximum Time Allowed Between Updates: 10 m
Current Job Name: ######_cam_16 - BTY
Current Job ID: 004_050_999_2cd5160f
Current Job User: dziga
Current Task Names: 1-5
Current Task Ids: 0
Searching for job with id “004_050_999_2cd5160f”
Found possible job: ########cam_16 - BTY
Searching for task with id “0”
Found possible task: :[1-5]
Task’s current slave: Fcp02_7
Slave machine names match, stopping search
Associated Job Found: #########_cam_16 - BTY
Associated Task Found: :[1-5]
Task’s current slave: Fcp02_7
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.
=======================================================
Slave Log
=======================================================
Error Type
=======================================================
Error Stack Trace
[/code]
Taking a closer look at the log I realize that the system time is wrong
…yep was the wrong timezone, so he submitted a time UTC+8hrs
Sorry for instantly posting here 
edit:
Mh, there still seem to be problems. I changed the timezone and resubmitted the job. Again the slave is stalled and the task is requeued and the log tells the last slave update was yesterday (the post before it told last update today in the morning). He seems to always show the wrong time. New log:
[code]=======================================================
Error Message
STALLED SLAVE REPORT
Current House Cleaner Information
Machine Performing Cleanup: Mg01
Version: v4.1.0.43205 R
Stalled Slave: Fcp02_7
Last Slave Update: 2011-01-30 22:42:11
Current Time: 2011-01-31 16:42:28
Time Difference: 18.001 hrs
Maximum Time Allowed Between Updates: 10 m
Current Job Name: #######_cam_15 - BTY
Current Job ID: 004_050_999_546e67d9
Current Job User: dziga
Current Task Names: 23-27
Current Task Ids: 0
Searching for job with id “004_050_999_546e67d9”
Found possible job: #####_cam_15 - BTY
Searching for task with id “0”
Found possible task: :[23-27]
Task’s current slave: Fcp02_7
Slave machine names match, stopping search
Associated Job Found: ##_cam_15 - BTY
Associated Task Found: :[23-27]
Task’s current slave: Fcp02_7
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.
=======================================================
Slave Log
=======================================================
Error Type
=======================================================
Error Stack Trace
[/code]
It could be that another machine in your farm doesn’t have its date/time synced properly. According to both reports, Mg01 is the machine that is determining that the render node is stalled, so check that machine’s date/time to see if it’s accurate. In Deadline 5.0, a render node’s system time no longer plays a role in stalled slave detection, so this won’t be a problem going forward.
It is possible to adjust the minimum time for stalled slave detection (the default is 10 minutes). In the Monitor, enter Super User Mode, and scroll down to find the Slave Settings. If you set it to 1440 minutes for example, a slave will only be considered stalled if it hasn’t updated it’s state for 24 hours. As long as your machines’ date/time are with 24 hours of each other, it should work fine.
Cheers,
I checked the times and they were all set up right. It turned out that a simple machine restart solved the issue. Sometimes it’s so easy 