Deadline 6.0.0.50661
Window 7 Pro
We’re having a weird issue where the status of jobs in the Monitor are not changing from Queued to Rendering even though the job has been picked up and has active tasks in the Task panel. This seems to happen across the board, ie we had two users with exactly the same jobs not showing the right status. To fix it we restarted the monitor and it then updated the status but both users had to restart to get the fix.
Cheers
Nick
We discovered this bug too earlier this week. The issue is that when a slave dequeues the task, it doesn’t update the job’s last write time, so the job isn’t shown as rendering in the monitor until something else updates the job (ie: the properties are changed, a task is completed, etc).
This has already been fixed internally, and will be fixed in beta 16.
Cheers,
We have the same issue on some machines, using build 50841 (beta17).
The jobs list just stops updating altogether… i come in in the morning and see 100+ queued jobs. Shut down the monitor, restart, it shows them all complete.
I think this might be related to this problem:
viewtopic.php?f=156&t=9383
Which could also be related to this problem:
viewtopic.php?f=156&t=9385
I think if we can figure out why that one mongodb thread is pegged at 100%, that would be a good start!
Added some logs the the second thread in there
Any news on this? This is getting so annoying that we are considering rolling back to beta 15 
We’re putting beta 18 through its paces right now, with a good chance that it will be released tomorrow. This releases addresses some data refreshing in the Monitor, and also fixes some inefficiencies with how the slaves talk to the database. We’re currently running 500 slaves with 3000 jobs in the queue, and mongo is averaging about 25-50% load (spread over multiple threads), and the data in the Monitor seems pretty up to date, so beta 18 should solve some of the issues you’ve been seeing lately.
Cheers,
Thanks Ryan! Fingers crossed it fixes the weird job status updating!