Deadline 7 Beta point release auto-update issue

[jpgodmaire]

Howdy folks,

We’re experiencing an interesting behaviour when upgrading from v7.0.0.26 to the latest version v7.0.0.36… I’ve seen this now on multiple machines so it doesn’t seem to be isolated to one workstation… Auto-upgrade is enabled on the server. I think it’s because the launcher service isn’t stopping properly which then doesn’t release the locks on all the files.

Anyone else have similar issues? Thanks!

2014-10-02 16:12:21: Deadline Launcher 7.0 [v7.0.0.26 R (c53f90c95)]
2014-10-02 16:12:21: deadlinelaunchernew is running
2014-10-02 16:12:21: Error occurred while trying to stop Launcher Service: Could not open Launcher Service because: Access is denied.
2014-10-02 16:12:21: deadlinelauncherservice has exited, proceeding with self upgrade
2014-10-02 16:12:26: Reading in bootstrap ini settings…
2014-10-02 16:12:26: Bootstrap file: C:\Users\render\AppData\Local\Thinkbox\Deadline7\temp\LauncherBootstrap\bootstrap.ini
2014-10-02 16:12:26: Copying \deadline\deadline\bin\Windows\bin.zip to C:\Users\render\AppData\Local\Thinkbox\Deadline7\temp\LauncherBootstrap\bin.zip
2014-10-02 16:12:26: Copying \deadline\deadline\bin\Windows\Version to C:\Users\render\AppData\Local\Thinkbox\Deadline7\temp\LauncherBootstrap\Version
2014-10-02 16:12:26: Decompressing C:\Users\render\AppData\Local\Thinkbox\Deadline7\temp\LauncherBootstrap\bin.zip to C:\Program Files\Thinkbox\Deadline7\bin
2014-10-02 16:12:26: Error: The process cannot access the file ‘C:\Program Files\Thinkbox\Deadline7\bin\MongoDB.Bson.dll’ because it is being used by another process. (System.IO.IOException)
2014-10-02 16:12:26: Launch Slave: True
2014-10-02 16:12:26: Launch Pulse: False
2014-10-02 16:12:26: Launch Monitor: False
2014-10-02 16:12:26: Launching launcher service
2014-10-02 16:12:26: Error occurred while trying to start Launcher Service: Could not open Launcher Service because: Access is denied.
2014-10-02 16:12:26: Self upgrade completed
2014-10-02 16:12:26: Shutting down

[anthonygelatka]

I also have an issue with the autoupdate.

I updated the repo to .36 but the slaves didn’t auto-update.

When I installed .36 on the client they auto-update to .26

repo on Centos 6.5, client on Windows 7x64

[rrussell]

Auto-updating wouldn’t have worked properly with beta 3 or beta 4 because we had to upgrade some core libraries. We had mentioned this in the post with the download links. Once you’re on beta 4 though, auto-upgrading to later builds should work fine.

We’ll still run some tests here with beta 4 though to make sure auto-upgrading still works.

Cheers,
Ryan