AWS Thinkbox Discussion Forums

Deadline failing to launch (Linux)

More of heads up more than anything (not urgent/not affecting any main machines:
I installed Deadline on an experimental machine we test things on (testing Fedora 14 to see what explodes this time), and Deadline binaries fail to run on that machine:

Machine Info:
Fedora 14 (64 bit)
Mono:Mono JIT compiler version 2.10.2 (tarball Mon Apr 18 19:06:50 UTC 2011) Copyright (C) 2002-2011 Novell, 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)

Running deadlinelauncher produces:

System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level Deadline Launcher 5.1: An exception was thrown by the type initializer for System.Windows.Forms.XplatUI (System.TypeInitializationException) at System.Windows.Forms.Theme.get_MenuAccessKeysUnderlined () [0x00000] in <filename unknown>:0 at System.Windows.Forms.SystemInformation.get_MenuAccessKeysUnderlined () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:.ctor () at System.Windows.Forms.WindowsFormsSynchronizationContext..cctor () [0x00000] in <filename unknown>:0

deadlineslave produces:

Deadline Slave 5.1 [v5.1.0.44754 R] Deadline Slave 5.1: An exception was thrown by the type initializer for System.Windows.Forms.WindowsFormsSynchronizationContext (System.TypeInitializationException) at System.Windows.Forms.Control..ctor () [0x00000] in <filename unknown>:0 at System.Windows.Forms.ScrollableControl..ctor () [0x00000] in <filename unknown>:0 at System.Windows.Forms.ContainerControl..ctor () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Form..ctor () [0x00000] in <filename unknown>:0 at FranticXForms.CustomControls.CustomForm..ctor () [0x00000] in <filename unknown>:0 at FranticXForms.Forms.SplashScreen..ctor (System.Drawing.Bitmap bitmap) [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) FranticXForms.Forms.SplashScreen:.ctor (System.Drawing.Bitmap) at FranticXForms.Forms.SplashScreen.ShowAsynch (System.Drawing.Bitmap bitmap) [0x00000] in <filename unknown>:0 at DeadlineSlave.DeadlineSlaveApp.Main (System.String[] args) [0x00000] in <filename unknown>:0

deadlinemonitor produces:

Deadline Monitor 5.1: An exception was thrown by the type initializer for System.Windows.Forms.XplatUI (System.TypeInitializationException) at System.Windows.Forms.Application.EnableVisualStyles () [0x00000] in <filename unknown>:0 at FranticXForms.Utils.ApplicationUtils.EnableVisualStyles () [0x00000] in <filename unknown>:0 at DeadlineMonitor.DeadlineMonitorApp.Main (System.String[] args) [0x00000] in <filename unknown>:0

Like I said, this is on an experimental machine that we’re testing Fedora 14 on, but so far it seems Deadline and Fedora 14 aren’t friends :frowning:

Oops! I meant to put this in the bug report forum! thwacks self Anyway to move it there? :blush:

Hey Matt,

No worries! I moved it for you. :slight_smile:

The errors appear to be UI related. Is libgdiplus installed on this system? It’s the Mono dependency that is used for all UI-related code.

Cheers,

  • Ryan

Yup, libgdiplus is installed. (I did 'yum install mono-addon* to install the whole shebang).

Hmm, it must be something about the system then (and in particular the Mono installation on that system). We haven’t had any issues on our Linux systems here.

Where is Mono installed to on the system? I’m guessing that because it’s an addon that it’s not installed in /usr or /usr/local. Is the place that the libraries are installed to in the path used by the system to search for shared libraries?

I found these instructions on how to add the path if it’s not:

It’s installed from novell’s repository, with vanilla setup, so it’s in /opt/novell. We use that handy mono-addon-environment.sh profile.d script another kindly user posted, so the libraries are indeed in the system path (the script appends the mono libraries to the system library path).

It’s actually identical to our Fedora 13 setup, which works fine on multiple machines.

Forgot to mention: SELinux is disabled, as well as the firewall.

Thanks for confirming that. We’ll try to set up a similar VM here and see if we can reproduce.

Do you have 5.1 installed on any of your Fedora 13 machines? I’m just curious if this problem is specific to your Fedora 14 machine.

Cheers,

  • Ryan

Yes, I do have 5.1 installed on a Fedora 13 machine. Works fine! :slight_smile:

Cheers!
-Matt

Privacy | Site terms | Cookie preferences