HI,
we just upgraded to 7.0.1.3 (from 7.0.0.52) and now Pulse does not wake up any machines that are assigned to a job we just submitted. It says
Power Management - Machine Startup: There are no slaves that need to be woken up at this timeAfter starting one of the machines manually it picked up the job and rendered it.
Attached is the Pulse log and a screenshot of the Monitor with the affected job selected.
Cheers,
Holger
deadlinepulse-cell-temp-01-2015-01-06-0002.log (506 KB)
Hello,
It looks by your screenshot that the monitor doesn’t recall ever having those slaves connected before, so you may need to manually start up the first time if they haven’t been started since the upgrade.
Hi,
that’s actually another thing that made me wonder. I don’t remember seeing this before with previous upgrades during the beta program.
But what does the monitor actually have to do with booting up machines for a job? I thought this is all done by Pulse?
Cheers,
Holger
Hello,
The monitor is only a method of displaying the information stored in the database. It’s showing us that the all but one of your slaves are showing ‘unknown’ as their status, which is resolved by manually starting the slaves. Pulse likewise won’t ‘know’ any of the slaves, so can’t start them up. Generally I believe we advise that when going from beta to release that you do a fresh install to ensure that there is no old beta code kicking around.
We did not upgrade the client machines and the Pulse machine through Deadline’s auto-upgrade feature but installed everything with the installers. We didn’t uninstall first, though. So was this not correct in this case? And when you say “fresh install” does that also include using a new and empty database?
Best,
Holger
Hello Holger,
We were looking over your screenshot and it seems almost all the slaves are still running the old version. How about we try to upgrade those slaves and start them up manually and see if that changes the situation? Let me know how that goes.
Hey Dwight,
maybe i should have been a bit more elaborate. All the Slaves are upgraded to 7.0.1.3. It’s not visible from the screenshot i provided for the following reason:
we have an automated install system (wpkg) in place which takes care of installing/upgrading software when a machine is booted just before a user can log in. So the way it worked for us in the past (i.e. the beta program) was by simply upgrading the Deadline Repository and and the Pulse machine (making sure all other machines were off) and the next reboot that happened either manually or by Pulse launching machines to render would then cause the update to the most current version. This is why in the screenshot in my first post you see all the other Slaves being on the old version. Once they were booted manually by me they all upgraded to 7.0.1.3. and since then were woken up as they used to be before. I just expected this to happen automatically as it was in the past.
But i guess this is basically all expected as you described when going from beta to final. For me, it’s basically enough to know that this can happen with certain upgrades and one manual boot is necessary. I was just confused as i didn’t know about this.
Cheers,
Holger
Ahh, well glad that it’s working once the right version got installed and the slaves were started. Hopefully future upgrades won’t have the same issue.
And also next time is should read the Release Notes before posting, it seems:
Pretty much says everything, i guess 
That it would, but we all have our moments of forgetting to read the docs 