Hello,
we are having an issue with our new install of deadline 7.
we have the machines powering down if they have been idle for 120 minutes.
and i thought i set it up so they would boot up at 5:30 am and then not be subject to the 120 min idle shutdown until after 8pm.
I also thought I set it up to wake them up when there are job pending.
We can have a huge queue of jobs and the machines wont start via wake on lan.
i can right click --> remote control --> machine commands --> start machine
this will boot the machine.
I have included screen grabs of my power management setting.
thanks for your help
Hello Troy,
So based on your settings, it definitely looks like your machines should have a 500 minute idle shutdown, but can you verify the system time on your Pulse machine is set right?
As for the wake on lan issue, I think the best thing would be to obtain a wake on lan testing app, there are several I found on google, and make sure your machines respond to wake on lan signals sent by your Pulse machine. Once we know that, we can move on with other testing. Thanks.
Cheers,
I am not certain this is a valid test, but rather than install an unknown third party app on our server I ran the monitor and was able to successfully start machines that were powered off by issuing a remote control command to wake the computer.
This is the computer running our primary pulse server.
I submitted a test job this morning and it did infact wake up the machines as intended, so i guess the part of the powermanagement that isnt behaving as expected is that i want all the machines to boot up at 5:30am and not to be subject to power management decisions until 8pm.
Thanks so much for the help
Hello Troy,
I think for that aspect, the best thing would be to send over the slave logs from machines that should not have been subject to those settings, but where anyways, as well as the pulse log. Send those over here, or via the support email address. Thanks.
Cheers,
I have made changes to things today, I will get the logs in the am after i have had another idle and wake cycle happen “naturally”
more to come tomorrow.
thanks,
OK, the machines are powering up on demand correctly, but i cant figure out how to force them to boot at 5:30 am and stay running no matter what until 8pm.
Below is the pulse log and a log from a slave that didn’t boot when I expected (530am even if it wasnt needed)
pulse log.txt (46.8 KB)
Slave Log.txt (8.19 KB)
Hello Troy,
Apologies for confusion, but now that I understand a bit better what you are wanting, I find there is no method to schedule a machine startup as you are wanting. You would need to just have them startup when there is work to do, which is what the machine startup is for.
As for the other issue of idle shutdown, we will need full slave log file for diagnosing the idle shutdown, not just the small cross section from the viewing windows that you sent over. You can obtain the slave log file by opening the slave window on the machine and choosing help, then explore log folders, and send over the log file from the time period in question. Reminder, this should be a log from a machine that entered idle shutdown when it shouldn’t have. A pulse log from the same time would be helpful too.
Thanks
well if the machines wont boot on a schedule and only on demand I think my problem is solved.
I can still send the logs over if you want but i think everything is working the way it should now!
thanks for your help
Hello,
Well, if everything is working how you want it, I’ll consider it resolved.
