Since upgrading to Deadline 6 and then moving onto the 6.1 beta, we’ve been having problems with power management which we never had a problem with before.
I realise that there must be something with our setup, because I’ve been going through the beta forum posts and it seems to be working for other people, but I just can’t get to the bottom of it.
Pulse is running properly, remote administration is turned on and working fine, but the machines never get turned off.
Like I said, this worked perfectly in D5, so I’m a bit puzzled about what’s stopping it from working now.
If anyone has some tips for me, I’d be more than grateful!
Cheers,
Dave
On the machine that Pulse is running on, can you open up the Monitor and try to manually start slave machines from the Remote Control right-click menu in the Slave list? I’m curious to see if that works or not. If it doesn’t, then there might be a network issue preventing the WOL broadcast message from reaching the slave machines.
If it does work, it could be that something in the Power Management settings is preventing Pulse from determining that the slave machines should be started. If you don’t have Pulse verbose logging enabled already, please enable it in the Repository Options under Application Logging. Then restart Pulse so that we have a clean log. Use Pulse’s Control menu to trigger a Power Management check, then select Help -> Explore Log Folder, then grab the most recent Pulse log and post it here and we’ll have a look.
Thanks!
Thanks for the tips Ryan, the farm is currently completely blocked for the next few days, but as soon as I can start trying your tips out, I’ll post back here.
Cheers,
Dave