I upgraded my repository to Build 15 … looks like everything went as planned … I chose the same repository path as well as chose the same
Mongo DB. Now that it has finished I try to click on one of the clients and try to restart the slave service remotely to upgrade the node.

The nodes seem to go offline and do not seem to update themselves…

Is there something that we need to do once the update on the repository is run?

OPERATING SYS SPECS:
license server: running on linux
render node: windows 7 x64bt
workstations: mac 10.7.5 and windows 7 x64bt

Thanks!
-Tommy

That should be it.

Can you go to a node that failed to upgrade, and zip up the Deadline log folder and post it? On Windows, that will be in %ProgramData%\Thinkbox\Deadline6\logs. We can check the logs from the upgrade to try and determine what went wrong.

Thanks!

• Ryan

Here are the logs … from one of the failed render nodes

-Tommy
logs.zip (2.35 MB)

Hi
I get the same behavior here after upgrading the repo to 15 with osx 10.5.7

-b

Tommy, thanks for the logs! It looks like for some reason, the bootstrap Launcher doesn’t appear to have started. This is how the upgrade works:

1. The current launcher copies its bin directory to a temp location.
2. After the copy, the current launcher starts the bootstrap launcher from that temp location.
3. The bootstrap launcher copies the bin.zip file from the repository and unzips it to the original bin directory.
4. The bootstrap launcher starts the updated launcher in the original bin directory.

So it looks like step (2) failed for some reason.

Can you try the following?

1. Run the beta 15 client installer on a node, and get the launcher and slave up and running again.
2. Go to the local bin folder (ie: C:\Program Files\Thinkbox\Deadline6\bin), open the Version file in a text editor (ie: notepad), modify the file, and save it. The Version file is just random binary data that the launcher uses to compare with the repository Version file to determine if an upgrade is necessary. So you can modify it in any way to trigger an update.
3. After modifying the file, try restarting the slave on it again and see if the “upgrade” now works or not.

If it works (and the launcher and slave start up again), it could be possible that there was still a bug that’s now fixed. If it fails again, send us the log folder again and we’ll have a look.

Bonsak, since you’re on OSX, you have to run the client intaller again to upgrade to beta 15. See the IMPORTANT NOTICE at the top of the announcement and download thread for beta 15 for more details:
viewtopic.php?f=84&t=9256

Thanks guys for putting up with these auto-update issues. We know it’s frustrating, and it’s frustrating for us too because we test these things here, and then they go out in the wild and something breaks.

Alright. Didn’t see that

-b

Hi Russell,

Thanks for all the help! For step 3… should I restart the slave on the machine locally? Or should I be trying to restart it via the monitor remotely?

Thanks!
-Tommy

Both should trigger the same code, so it shouldn’t matter which one you use. Maybe try it remotely, since I think that’s what you originally did.

I stopped the slave remotely on node 72. Installed locally the build 15. Saw that it was idle. Stopped service remotely again. Edited Version file and saved with changes.
I went back and selected to start slave remotely… seems to have worked. I have included the logs.
logs_updated.zip (2.77 MB)

That’s promising! Thanks for running that test. This should mean that the machine should now properly upgrade to beta 16, since the auto-upgrade code is now considered stable. Maybe there was something left over from a previous version that broke things, and reinstalling the client fixed it.

So it sounds like you’ll have to manually upgrade your clients to beta 15, and then you should be good going forward.

Again, we’re very sorry for this inconvenience.