Just installed Beta 5 repository and turned on the render nodes to uninstall/update.
The auto-installation system though now has every single system in some kind of loop locking the systems. (windows)
Uninstall beta 4 and then update your repository.
I might have the same thing going on.
Updated the rep, started the launcher, and slave, notice states update in progress, then launcher dies. Restarted the launcher, but same thing happens.
Restarted the machine, and the launcher started, and died, but when manually started it looks to have updated, and is running.
Maybe just removing the beta 4 slave, first would have helped.
Mark
Mark, did you have Deadline installed as a service too (I know Gavin did)? I wonder if it’s a service specific problem, since there were issues with the service that was created by beta 4 and earlier.
It took me power-cycling each computer 2-3 times and they eventually were able to accept an RDP connection for purging.
Now that I’ve removed the service, uninstalled and re-installed it seems to be working ok again.
Hi Ryan, no, the launcher/slave is not installed as a service. I’m currently only testing the beta’s on one slave machine.
Happy to test any other ideas you have, is there a log I can send you?
Mark
Yeah, the deadlinelauncher and deadlinelaunchernew logs would be helpful. Since it was stuck in an infinite loop, I’m sure there are quite a few of these. If you run the Launcher, you can access the log folder from the right-click menu. Maybe just grab a handful of deadlinelauncher and deadlinelaunchernew logs and we’ll sort through them.
Thanks!
Sounds fun! I will asap, just got the 5.2 slave running at the mo. If you point me to the folder the logs are stored, or Ill need to wait until I can start the other launcher, I cant risk this render crashing.
On Windows, the application logs should be in C:\ProgramData\Thinkbox\Deadline6\Logs (in Windows 7, at least). If you’re on XP/Linux/Mac (I don’t remember those off the top of my head), you should be able to right-click the Launcher and select “Explore Log Folder”, and that should get you to the right spot. Note that if you do that with the 5 launcher, you’ll have to go up a couple folders, and into the “Deadline6” one, since we’ve split off the 6 stuff into its own folder.
Look for files prefixed with ‘deadlinelauncher’ and ‘deadlinelaunchernew’ dated roundabout when you were updating.
Cheers,
Thanks Jon,
I have just emailed a load of logs to the support email addresss. Subject called “WARNING BETA 5 - log files”
Hope they help, I did look at one and see a list of files being copied.
Mark
Got them! We’ll take a look to see what we can figure out.
Thanks,
Hmm, there is info explaining why the update fails, but we’re not sure why it’s happening. We still haven’t finalized the bin folder for the client yet, so I would recommend avoiding the auto upgrade until later in the beta when it has been finalized. For now, we will continue to mention in the Deadline 6 download pages that auto-upgrading is not supported yet.
Cheers,