One machine here took the installation without issue. That was upgraded from Mono 2.6.4 to 2.6.7 and has the repository and client 5.0 beta 2 now installed without issue (with 2.6.4, the installer postflight failed)
On another machine that had Mono 2.8 installed, the client installer failed and this was then forcibly downgraded to Mono 2.6.7. The installer still fails with the following in the console.app output :
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Checking OSX version
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Checking X11
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] /Volumes/Deadline Installers/DeadlineClient.pkg/Contents/Resources/InstallationCheck: line 13: /Volumes/Deadline: No such file or directory
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] /Volumes/Deadline Installers/DeadlineClient.pkg/Contents/Resources/InstallationCheck: line 14: [: !=: unary operator expected
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Checking Mono
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Mono JIT compiler version 2.6.7 (tarball Wed Jul 14 11:57:56 MDT 2010)
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Copyright © 2002-2010 Novell, Inc and Contributors. www.mono-project.com
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] TLS: normal
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] GC: Included Boehm (with typed GC)
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] SIGSEGV: normal
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Notification: Thread + polling
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Architecture: x86
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] Disabled: none
27/01/2011 21:13:30 [0x0-0x18bd8bc].com.apple.installer[34734] Finished pre-install checks
27/01/2011 21:13:40 Installer[34734] The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
On the machine where the error was not reported, the client folder matches the machine which reports the error. Here’s the installed file listing on both machines :
total 0
drwxrwxrwx 3 root admin 102 Jan 21 21:30 Deadline.saver
drwxrwxrwx 18 root admin 612 Jan 27 21:04 Resources
./Deadline.saver:
total 0
drwxrwxrwx 5 root admin 170 Jan 27 21:04 Contents
./Deadline.saver/Contents:
total 8
-rwxrwxrwx 1 root admin 797 Jan 21 21:30 Info.plist
drwxrwxrwx 3 root admin 102 Jan 27 21:04 MacOS
drwxrwxrwx 4 root admin 136 Jan 27 21:04 Resources
./Deadline.saver/Contents/MacOS:
total 128
-rwxrwxrwx 1 root admin 64448 Jan 21 21:30 Deadline
./Deadline.saver/Contents/Resources:
total 136
-rwxrwxrwx 1 root admin 66354 Jan 21 21:30 DeadlineMainSplashMini.BMP
drwxrwxrwx 3 root admin 102 Jan 27 21:04 English.lproj
./Deadline.saver/Contents/Resources/English.lproj:
total 8
-rwxrwxrwx 1 root admin 218 Jan 21 21:30 InfoPlist.strings
./Resources:
total 1736
-rwxrwxrwx 1 root admin 102446 Jan 21 21:30 DeadlineCommand.icns
-rwxrwxrwx 1 root admin 102446 Jan 21 21:30 DeadlineCommandBG.icns
-rwxrwxrwx 1 root admin 55169 Jan 21 21:30 DeadlineJobMonitor.icns
-rwxrwxrwx 1 root admin 66504 Jan 21 21:30 DeadlineLauncher.icns
-rwxrwxrwx 1 root admin 53623 Jan 21 21:30 DeadlineMonitor.icns
-rwxrwxrwx 1 root admin 58132 Jan 21 21:30 DeadlinePulse.icns
-rwxrwxrwx 1 root admin 189606 Jan 21 21:30 DeadlineQuicktimeGeneratorExe.icns
-rwxrwxrwx 1 root admin 62877 Jan 21 21:30 DeadlineSlave.icns
-rwxrwxrwx 1 root admin 51430 Jan 21 21:30 RepositorySetupWizard.icns
-rwxrwxrwx 1 root admin 102446 Jan 21 21:30 TileAssemblerExe.icns
drwxrwxrwx 48 root admin 1632 Jan 27 21:04 bin
drwxrwxrwx 3 root admin 102 Jan 27 21:00 logs
-rwxrwxrwx 1 root admin 9603 Jan 21 21:30 setDefaults.py
drwxrwxrwx 2 root admin 68 Jan 27 21:04 settings
drwxrwxrwx 4 root admin 136 Jan 27 21:04 slave
drwxrwxrwx 2 root admin 68 Jan 27 21:04 temp
./Resources/bin:
total 49376
-rwxrwxrwx 1 root admin 61440 Jan 21 21:30 Growl.Connector.dll
-rwxrwxrwx 1 root admin 24576 Jan 21 21:30 Growl.CoreLibrary.dll
-rwxrwxrwx 1 root admin 122880 Jan 21 21:30 ICSharpCode.SharpZipLib.dll
-rwxrwxrwx 1 root admin 464728 Jan 21 21:30 IronPython.Modules.dll
-rwxrwxrwx 1 root admin 1496920 Jan 21 21:30 IronPython.dll
-rwxrwxrwx 1 root admin 956248 Jan 21 21:30 Microsoft.Dynamic.dll
-rwxrwxrwx 1 root admin 403288 Jan 21 21:30 Microsoft.Scripting.Core.dll
-rwxrwxrwx 1 root admin 58200 Jan 21 21:30 Microsoft.Scripting.Debugging.dll
-rwxrwxrwx 1 root admin 11096 Jan 21 21:30 Microsoft.Scripting.ExtensionAttribute.dll
-rwxrwxrwx 1 root admin 178008 Jan 21 21:30 Microsoft.Scripting.dll
-rwxrwxrwx 1 root admin 181248 Jan 21 21:30 Mono.Posix.dll
-rwxrwxrwx 1 root admin 1024 Jan 21 21:30 Version
-rwxrwxrwx 1 root admin 307200 Jan 21 21:30 ZedGraph.dll
-rwxrwxrwx 1 root admin 3477504 Jan 21 21:30 deadline.dll
-rwxrwxrwx 1 root admin 96 Jan 21 21:30 deadlinecommand
-rwxrwxrwx 1 root admin 16384 Jan 21 21:30 deadlinecommand.exe
-rwxrwxrwx 1 root admin 100 Jan 21 21:30 deadlinecommandbg
-rwxrwxrwx 1 root admin 10240 Jan 21 21:30 deadlinecommandbg.exe
-rwxrwxrwx 1 root admin 737280 Jan 21 21:30 deadlineforms.dll
-rwxrwxrwx 1 root admin 102 Jan 21 21:30 deadlinejobmonitor
-rwxrwxrwx 1 root admin 131072 Jan 21 21:30 deadlinejobmonitor.exe
-rwxrwxrwx 1 root admin 98 Jan 21 21:30 deadlinelauncher
-rwxrwxrwx 1 root admin 126976 Jan 21 21:30 deadlinelauncher.exe
-rwxrwxrwx 1 root admin 96 Jan 21 21:30 deadlinemonitor
-rwxrwxrwx 1 root admin 155648 Jan 21 21:30 deadlinemonitor.exe
-rwxrwxrwx 1 root admin 92 Jan 21 21:30 deadlinepulse
-rwxrwxrwx 1 root admin 139264 Jan 21 21:30 deadlinepulse.exe
-rwxrwxrwx 1 root admin 246 Jan 21 21:30 deadlinequicktimegenerator
-rwxrwxrwx 1 root admin 66960 Jan 21 21:30 deadlinequicktimegeneratorexe
-rwxrwxrwx 1 root admin 92 Jan 21 21:30 deadlineslave
-rwxrwxrwx 1 root admin 155648 Jan 21 21:30 deadlineslave.exe
-rwxrwxrwx 1 root admin 1138688 Jan 21 21:30 franticx.dll
-rwxrwxrwx 1 root admin 499712 Jan 21 21:30 franticxforms.dll
-rwxrwxrwx 1 root admin 3857768 Jan 21 21:30 libDeadlinePlugin.dylib
-rwxrwxrwx 1 root admin 568012 Jan 21 21:30 libHalf.6.dylib
-rwxrwxrwx 1 root admin 208432 Jan 21 21:30 libIex.6.dylib
-rwxrwxrwx 1 root admin 2019712 Jan 21 21:30 libIlmImf.6.dylib
-rwxrwxrwx 1 root admin 77432 Jan 21 21:30 libIlmThread.6.dylib
-rwxrwxrwx 1 root admin 75180 Jan 21 21:30 libImath.6.dylib
-rwxrwxrwx 1 root admin 1154928 Jan 21 21:30 libMagick++.1.dylib
-rwxrwxrwx 1 root admin 3181564 Jan 21 21:30 libMagickCore.1.dylib
-rwxrwxrwx 1 root admin 1943832 Jan 21 21:30 libMagickWand.1.dylib
-rwxrwxrwx 1 root admin 108 Jan 21 21:30 repositorysetupwizard
-rwxrwxrwx 1 root admin 122880 Jan 21 21:30 repositorysetupwizard.exe
-rwxrwxrwx 1 root admin 98 Jan 21 21:30 tileassembler
-rwxrwxrwx 1 root admin 1069032 Jan 21 21:30 tileassemblerexe
./Resources/logs:
total 8
-rwxrwxrwx 1 root admin 2603 Jan 27 21:04 installlog.txt
./Resources/settings:
./Resources/slave:
total 0
drwxrwxrwx 2 root admin 68 Jan 27 21:04 jobsData
drwxrwxrwx 2 root admin 68 Jan 27 21:04 plugins
./Resources/slave/jobsData:
./Resources/slave/plugins:
./Resources/temp:
Thanks for reporting this! It looks like there are two issues that are occurring. The first one that stands out is this:
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] /Volumes/Deadline Installers/DeadlineClient.pkg/Contents/Resources/InstallationCheck: line 14: [: !=: unary operator expected
We could reproduce this, but we found that it wasn’t fatal. We’ll fix it it in beta 3.
The other is this:
27/01/2011 21:13:29 [0x0-0x18bd8bc].com.apple.installer[34734] /Volumes/Deadline Installers/DeadlineClient.pkg/Contents/Resources/InstallationCheck: line 13: /Volumes/Deadline: No such file or directory
We could also reproduce this, but it also didn’t appear to be fatal. This is a result of us not quoting a path in the InstallationCheck script (the dmg is mounted as “Deadline Installers”. This will also be fixed in beta 3.
So because those two issues are non-fatal, they’re probably not related to the installer failing. However, these errors are occurring as a result of a failed attempt to confirm that X11 is installed. Do you have X11 installed on the machine the installer fails on?
Cheers,
Yes - all machines have previously had Deadline 4.1 installed and have the vanilla OS X X11 installed. I moved all of the Deadline 4.1 files out of the way (client on both machines that saw an attempt to install DL 5, and repository was moved out of the way as well)
Depending on the ETA for beta 3, what issues might I face backing up to 4.1? The release notes suggest that reverting back is a problem, so I wanted to ask.
Beta 3 should be released early next week. Our plan is to build the installers this afternoon and run a few tests, so there is a good chance we can release it on Monday. To roll back to 4.1, you should just reinstall 4.1 (or move the files back to their original location, since you said you just moved them out of the way).
I’m not sure if the fixes we’ve made to the installer address your specific problem though. I guess we’ll find out one way or another next week. If you have the same problem with beta 3, can you post both the console log (which you did previously) and the installer log? You can get the installer log while the installer is running by selecting Window -> Installer Log form the Installer menu at the top. In the drop down, choose Show All Logs so that we can see everything.
Thanks!
Sadly, beta 3 is still uninstallable here (client installation - repository appears to install just fine)
I’ve attached the full installer log.
Installer Log 4-Feb-2011.txt (11 KB)
Thanks for the log. The install is failing during the execution of the post flight script, which indicates that there is a problem with your installation of Mono. At the point of the error, the Deadline files are already installed, so you can confirm if it’s a mono issue by opening a terminal and running this command:
/Applications/Deadline/Resources/bin/deadlinecommand UpdatePathVariable
I’m expecting you to get an error dumped to the terminal. If you do, post it and we’ll go from there.
On a related note, we need to figure out how to get these mono-related errors to show up in the installer log.
/Applications/Deadline/Resources/bin/deadlinecommand: line 3: /Applications/Deadline/Resources/bin/…/…/DeadlineCommand.app/Contents/MacOS/DeadlineCommand: No such file or directory
/Applications/Deadline/Resources/bin/deadlinecommand: line 3: exec: /Applications/Deadline/Resources/bin/…/…/DeadlineCommand.app/Contents/MacOS/DeadlineCommand: cannot execute: No such file or directory
This is unsurprising - there’s no such file or folder. File/folder listing is attached.
DL5list.txt (2.54 KB)
Sorry, try this instead:
mono /Applications/Deadline/Resources/bin/deadlinecommand.exe UpdatePathVariable
If I use Pacifist instead, I can get the full file/folder extracted and run your command. I then see this :
Error occured while editing environment.plist file:
Access to the path “/Users/mediacentre/.MacOSX/environment.plist” is denied.
Indeed, that file is inaccessible :
-rw-r–r-- 1 root staff 212 Sep 25 08:41 environment.plist
Changing permissions and owner to the logged in user and with group writeable access, the command reports no error.
I guess that would make sense. Running the installer elevates the privileges, so this would have worked fine. The only other deadline command in the post flight script is the following, so try it and let me know if you get an error this time:
mono /Applications/Deadline/Resources/bin/deadlinecommand.exe ExecuteScript /Applications/Deadline/Resources/SetDefaults.py /Applications/Deadline $HOME
If that works, then it would appear that Mono is installed properly, and maybe it’s something else in the postflight script.
That displays the client configuration dialog without any error.
Alright, so that pretty much confirms that Mono is installed properly. I’ll take another look at the installer log you posted and see if anything else stands out. For reference, here are the actual commands that the postflight script runs:
mkdir $HOME/Deadline
mkdir $HOME/Deadline/settings
mkdir $HOME/Deadline/slave/jobsData
mkdir $HOME/Deadline/slave/plugins
mkdir $HOME/Deadline/temp
mkdir $HOME/Deadline/themes
/Applications/Deadline/Resources/bin/deadlinecommand UpdatePathVariable
chmod -v -R 0777 /Applications/Deadline
chmod -v -R 0777 $HOME/Deadline
/Applications/Deadline/Resources/bin/deadlinecommand ExecuteScript /Applications/Deadline/InstallTemp/SetDefaults.py /Applications/Deadline $HOME
chmod -v -R 0777 /Applications/Deadline
chmod -v -R 0777 $HOME/Deadline
cp -r “/Applications/Deadline/Deadline.saver” “/Library/Screen Savers/”
You’ve already tried the highlighted commands, so maybe try the others in the meantime to see if any of them fail.
Cheers,
Forgot, but you may have to SUDO those commands…
Here’s a crazy idea. Try copying the Client installer from the mounted disk to your desktop and then try running it again. I’m really starting to wonder if the space in “Deadline Installers” is causing more problems then we expected.
What I really don’t understand is the absence of the myriad .app bundles in the Deadline client folder. I’ll run the installation tomorrow.
In the meantime, it seems that reverting back does causes issues - on the machines which saw an attempted install of DL5, the DL4.1 interface (monitor in particular) becomes totally unpredictable - I’m unable to scroll lists or select tasks or nodes. Menus also behave utterly randomly.
Copying the .pkg from the mounted .dmg to the desktop still results in an installation failure - the output seems to be the same as for the installation from the .dmg
Ah, I think that is the problem. The .app bundles don’t get installed, and thus the the UpdatePath command which I had you test earlier fails. Knowing that the problem isn’t with the postflight script itself, I took another look at the installer log and this caught my eye:
So it appears the installer is installing the .app packages to the relocated 4.1 client install folder. So it might be best to do the following:
- Delete the 5.0 client folder (which I assume is /Applications/Deadline) and empty your trash bin
- Move “Deadline41” back to “Deadline” (which should hopefully fix the redirection)
- Run the 5.0 client installer and install over the existing installation (you shouldn’t have to delete it from disk first)
Cheers,