AWS Thinkbox Discussion Forums

[Linux] Beta 4: Client installer error

Deprecated Deadline 6 Bug Reports
#1

I still get the popup from http://forums.thinkboxsoftware.com/viewtopic.php?f=156&t=8294 when running the client installer. However, I now also get the following in the terminal:

Stacktrace:

  at (wrapper managed-to-native) ssemblyManager.PyImport_ExecCodeModule (string,intptr) <0xffffffff>
  at NativeCall. (string,string) <0x00077>
  at abase.iewResult`2.etModulePreLoad (string,string) <0x0012f>
  at abase.iewResult`2.ppendSearchPath (string) <0x00043>
  at Names.ions.ranticXConfig (string) <0x00023>
  at a.a (string[]) <0x0070f>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

Note that there wasn’t anything printed for the Native stacktrace; that wasn’t just me messing up the paste.

-Nathan

#2

Sorry, here’s the bitrock installer log (still pretty bare):

[code]Log started 10/31/2012 at 16:05:04
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
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 0 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/31/2012 at 16:06:30[/code]

#3

This is so strange. We found one post-install action on linux that wasn’t being logged, so that will be added for beta 5.

We have the “Removing Launcher service” action set to not show an error if one occurs (because there is no service installed, for example). After that, we try to substitute some text in the deadlinelauncherservice file in the Deadline bin folder. This is the action that was missing a log entry. So in beta 5, run the client installer again, and then if you get the error, please post the bitrock log again.

Thanks!

  • Ryan
#4

Still getting the error, though no terminal error this time. Log appears the same.

[code]Log started 11/09/2012 at 10:52:43
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
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 0 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
Substituting text in /usr/Deadline6/client/bin/deadlinelauncherservice
Adding 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 11/09/2012 at 10:55:31[/code]

#5

We were finally able to reproduce this on our Fedora VM, so it’s probably an issue on CentOS and RedHat too. It doesn’t happen on Ubuntu, but oh well.

This should be fixed once and for all in beta 6. I hope I don’t regret saying that… :slight_smile:

Privacy | Site terms | Cookie preferences