AWS Thinkbox Discussion Forums

Hacking Auto Update doesn't work

I tried to deploy the updated deadline salve through the auto update system and it just gave me this error when a slave attempts to update:

2012-11-14 10:33:49: BEGIN - RENDER-04\renderadmin 2012-11-14 10:33:49: Start-up 2012-11-14 10:33:49: 2012-11-14 10:33:48 2012-11-14 10:33:49: deadlinelaunchernew.exe is running 2012-11-14 10:33:49: Launcher Service stopped successfully 2012-11-14 10:33:50: deadlinelauncherservice.exe has exited, proceeding with self upgrade 2012-11-14 10:33:55: Reading in bootstrap ini settings... 2012-11-14 10:33:55: Bootstrap file: C:\Users\renderadmin\AppData\Local\Thinkbox\Deadline6\temp\LauncherBootstrap\bootstrap.ini 2012-11-14 10:33:55: Copying \\sfs-file\deadlinerepository6\bin\Windows\bin.zip to C:\Users\renderadmin\AppData\Local\Thinkbox\Deadline6\temp\LauncherBootstrap\bin.zip 2012-11-14 10:33:56: Copying \\sfs-file\deadlinerepository6\bin\Windows\Version to C:\Users\renderadmin\AppData\Local\Thinkbox\Deadline6\temp\LauncherBootstrap\Version 2012-11-14 10:33:56: Decompressing C:\Users\renderadmin\AppData\Local\Thinkbox\Deadline6\temp\LauncherBootstrap\bin.zip to C:\Program Files\Thinkbox\Deadline6\bin 2012-11-14 10:33:56: Error: Could not find a part of the path 'C:\Program Files\Thinkbox\Deadline6\bin\bin\AxInterop.QTOControlLib.dll'. (System.IO.DirectoryNotFoundException) 2012-11-14 10:33:56: Launch Slave: True 2012-11-14 10:33:56: Launch Pulse: False 2012-11-14 10:33:56: Launch Monitor: False 2012-11-14 10:33:56: Launching launcher service 2012-11-14 10:33:57: Launcher Service started successfully 2012-11-14 10:33:57: Self upgrade completed 2012-11-14 10:33:57: Shutting down

P.S. Not a fan of the zipped Bin folder.

P.P.S can the version file be in plaintext please?

There are actually a few benefits to the zipped bin folder.

  1. The auto update occurs faster because we only need to copy 2 files (the Version and the bin.zip files) instead of the current count of 532, and we’re getting about 37% compression on the overall size.
  2. There is less chance for the auto update to go bad, since an error in copying these 2 files won’t cause the local bin folder to potentially contain files from two different versions.

The Version file is just random data, which we do an MD5 checksum on to determine if the local Version file is different than the repository’s. All you need to do to trigger an update is just modify it. You can open it in a text editor, mash the keyboard, and save it, because it doesn’t matter what is actually in the file. We don’t store the actual Deadline version number here because it’s possible for an update to be required when there hasn’t been a version bump (especially when we’re doing internal testing).

For your error, how did you zip up the bin folder? Did you zip up the bin folder itself, or did you go inside the bin folder and just zip up its contents? We require the latter case, because bin.zip is decompressed directly into the local bin folder.

Ahhh, I zipped up the zip folder. That was the problem.

Privacy | Site terms | Cookie preferences