When installing beta 2 (in this case, over a beta 1 installation), I get a popup warning:

Unknown error running post-install step. Installation may not complete correctly

The installer is running as root, and I am not trying to install the Launcher as a daemon. This also doesn’t seem to affect the installation (at least from what I can tell so far).

The installer writes a log to your temp folder. I believe it’s prefixed with “BitrockInstaller”, or something similar. If you can run the installer again so that the error occurs, and then send us that log after the installation finishes, that would be great!

Cheers,

• Ryan

Here’s the log (though I’m afraid it isn’t particularly illuminating). When the popup occurs, the last line in the log is “Adding /usr/Deadline6/client to PATH.”

[code]
Log started 10/15/2012 at 10:37:10
Preferred installation mode : gtk
Trying to init installer in mode gtk
Mode gtk successfully initialized
Executing mono -V
Script exit code: 0

Script output:
Mono JIT compiler version 2.10.5 (tarball Mon Sep 5 20:45:01 UTC 2011)
Copyright © 2002-2011 Novell, Inc, Xamarin, Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: debugger softdebug
LLVM: supported, not enabled.
GC: Included Boehm (with typed GC and Parallel Mark)

Script stderr:

Preparing to Install
Preparing to Install
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Unpacking files
Creating Shortcut for Uninstall Deadline Client
Removing /usr/Deadline6/client from PATH.
Adding /usr/Deadline6/client to PATH.
Unknown error running post-install step. Installation may not complete correctly
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 10/15/2012 at 10:40:35[/code]

Thanks! We’ll add more progress logging to the post install actions so that if this happens in beta 3, we’ll know where.

Still getting the same error in Beta 3. Log is included below.

Preparing to Install Preparing to Install Unpacking files Unpacking files Unpacking files Unpacking files Unpacking files Unpacking files Unpacking files Unpacking files Unpacking files Unpacking files Creating Shortcut for Uninstall Deadline Client Removing /usr/Deadline6/client from PATH. Adding /usr/Deadline6/client to PATH. Setting NetworkRoot to /usr/Deadline6/repo in /var/lib/Thinkbox/Deadline6/deadline.ini Setting LicenseServer to @localhost in /var/lib/Thinkbox/Deadline6/deadline.ini Setting LauncherListeningPort to 5042 in /var/lib/Thinkbox/Deadline6/deadline.ini Setting AutoConfigurationPort to 5043 in /var/lib/Thinkbox/Deadline6/deadline.ini Setting SlaveDataRoot to in /var/lib/Thinkbox/Deadline6/deadline.ini Setting LaunchSlaveAtStartup to 1 in /root/Thinkbox/Deadline6/deadline.ini Creating dpython symbolic link Creating libpython symbolic link Setting permissions on /usr/Deadline6/client Setting permissions on /var/lib/Thinkbox/Deadline6 Setting file permissions on deadlinecommand Setting file permissions on deadlinecommandbg Setting file permissions on deadlinelauncher Setting file permissions on deadlinelauncherservice Setting file permissions on deadlinemonitor Setting file permissions on deadlinepulse Setting file permissions on deadlineslave Setting file permissions on dpython Setting file permissions on tileassembler64 Removing Launcher service Unknown error running post-install step. Installation may not complete correctly Creating Uninstaller Creating uninstaller 25% Creating uninstaller 50% Creating uninstaller 75% Creating uninstaller 100% Installation completed Log finished 10/18/2012 at 09:43:20

-Nathan

Since you aren’t installing the launcher as a daemon, there is only one thing in the installer that could throw this error, and it’s a simple text replacement action in a file. As I mentioned in another thread, we are currently setting up a Fedora 16 VM to test, as this might just be specific to that OS.

Cheers,

• Ryan