see attached logs.
Archive.zip (5.41 KB)
Weird. Worked here on most slaves. A couple of them had to be manually updated.
-b
Hey Mike,
Can you try this?
- Uninstall the client from the machine, and blow away the /Applications/Thinkbox/Deadline6 folder if it still exists.
- Install the Client using the public release of the 6.0 Client installer.
- Try the auto-upgrade again to 6.1 beta 2.
In previous 6.0 beta releases, the permissions on the Python.framework folder weren’t being set properly, but this issue was fixed before 6.0 went public. Based on the log, I’m wondering if this is causing the auto-upgrade problem you’re seeing.
Cheers,
- Ryan
Hey Ryan,
I followed your instructions. Re-installed the v6.0 public client after 100% removing the client “deadline6” install directory.
Auto-upgrade is enabled in the v6.1 beta 2 repository. I started up launcher and monitor, it went for an auto upgrade but again, failed due to permissions not being set correctly on ALL items under the “python2.6” directory. See log below:
2013-08-23 17:46:27: BEGIN - mbp.home\owenm
2013-08-23 17:46:27: Deadline Launcher 6.0 [v6.0.0.51561 R]
2013-08-23 17:46:27: deadlinelaunchernew is running
2013-08-23 17:46:27: deadlinelauncher has exited, proceeding with self upgrade
2013-08-23 17:46:31: Reading in bootstrap ini settings…
2013-08-23 17:46:31: Bootstrap file: /Users/owenm/Library/Application Support/Thinkbox/Deadline6/temp/LauncherBootstrap/bootstrap.ini
2013-08-23 17:46:31: Copying /Applications/Thinkbox/DeadlineRepository6/bin/Mac/bin.zip to /Users/owenm/Library/Application Support/Thinkbox/Deadline6/temp/LauncherBootstrap/bin.zip
2013-08-23 17:46:31: Copying /Applications/Thinkbox/DeadlineRepository6/bin/Mac/Version to /Users/owenm/Library/Application Support/Thinkbox/Deadline6/temp/LauncherBootstrap/Version
2013-08-23 17:46:31: Decompressing /Users/owenm/Library/Application Support/Thinkbox/Deadline6/temp/LauncherBootstrap/bin.zip to /Applications/Thinkbox/Deadline6/Resources
2013-08-23 17:46:31: Error: Access to the path “/Applications/Thinkbox/Deadline6/Resources/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/MagmaFLUX.so” is denied. (System.UnauthorizedAccessException)
2013-08-23 17:46:31: Launch Slave: False
2013-08-23 17:46:31: Launch Pulse: False
2013-08-23 17:46:31: Launch Monitor: True
2013-08-23 17:46:31: Launching launcher
“/Applications/Thinkbox/Deadline6/Resources/Frameworks/Python.framework/Versions/2.6/lib/python2.6” is set to read & write. Anything below this directory including the “site-packages” directory only has “read only” permissions.
Not sure what else to try. Could you possibly verify this issue at your end? Maybe it’s specific to OSX 10.8.4?
Thanks,
Mike
Hey Mike,
Thanks for testing this. We tested the same thing on one of our Macs and we were able to reproduce. This is unfortunate, as it would appear the permissions are not set properly by the public 6.0 client installer, which will prevent the auto-update for 6.1 from working on OSX. We should be able to fix the permission issues during the 6.1 beta, but that would only apply to the 6.1 client installer.
Cheers,
- Ryan
OK. Thanks for confirming I’m not going mad! Maybe v6.1 can have any other outstanding core changes if the auto update won’t be working for OSX at least…?
Not sure I follow. Are there specific core changes you’re referring to?
Note that the auto update should still work fine for Linux and Windows, and that this auto-update issue on the Mac will only affect workstations (machines that run the Monitor), so we’ll basically need a disclaimer in the auto-updating section of the docs that on Macs running the Monitor, the client installer will need to be installed again.