Cannot start deadline Linux on fedora 10

Deadline
1

On a fresh DVD install of Fedora 10, I don’t seem to be able to run any of the deadline apps. When I try to start the slave (either via ‘deadlinelauncher --slave’ or via ‘deadlineslave’), I get the following message:

[code][lustre@bigtower ~]$ deadlinelauncher --slave

** (/usr/local/lib/deadline/deadlinelauncher.exe:4492): WARNING **: System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
manager != null: False
Deadline Launcher 3.0: Protocol option not supported (System.Net.Sockets.SocketException)
at System.Net.Sockets.Socket.SetSocketOption (SocketOptionLevel level, SocketOptionName name, Int32 opt_value) [0x00000]
at FranticX.Net.SocketUtils.CreateTcpSocket (AddressFamily addressFamily) [0x00000]
at FranticX.Net.SocketUtils.IsSocketInUse (Int32 port) [0x00000]
at DeadlineLauncher.DeadlineLauncherApp.Main (System.String[] args) [0x00000]
[lustre@bigtower ~]$
[/code]

did I not install something properly, or what? This message is like trying to read hiroglyphs to me…

Any insight you can provide on this will be greatly appreciated.

2

Which version of Deadline did you install, 3.0 or 3.0 SP1? This error looks like one that we fixed in 3.0 SP1. Also, which version of Mono is installed on the machine? Deadline 3.0 and 3.0 SP1 have been tested against Mono 1.9.1.

Cheers,

  • Ryan
3

the output of “mono --version” spits out 2.0.1.

As for running the slave, I can run it as root (which I REALLY don’t want to do), but when I try to run it as a regular user, I get the following:

[code][lustre@bigtower flexlm]$ deadlineslave

** (deadlineslave:4382): WARNING **: System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
Socket supports IPv6 and IPv4, but a socket that supports both could not be created because: Protocol option not supported
Deadline Slave 3.0 [v3.0.33353 R]
slave initialization beginning.
Repository time: 12/03/2008 12:01:04
Info Thread - Created.

** (deadlineslave:4382): WARNING **: System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
Socket supports IPv6 and IPv4, but a socket that supports both could not be created because: Protocol option not supported
Marshaling unrealize signal
Exception in Gtk# callback delegate
Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.InvalidProgramException: can not call Slave.Shutdown() when Slave.Mode is Initializing
at Deadline.Slaves.Slave.Shutdown () [0x00000]
at Deadline.Slaves.SlaveManager.ShutdownSlave () [0x00000]
at DeadlineSlave.SlaveMainWindow.SlaveMainWindow_Unrealized (System.Object sender, System.EventArgs e) [0x00000]
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
— End of inner exception stack trace —
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000]
at System.Delegate.DynamicInvokeImpl (System.Object[] args) [0x00000]
at System.MulticastDelegate.DynamicInvokeImpl (System.Object[] args) [0x00000]
at System.Delegate.DynamicInvoke (System.Object[] args) [0x00000]
at GLib.Signal.ClosureInvokedCB (System.Object o, GLib.ClosureInvokedArgs args) [0x00000]
at GLib.SignalClosure.Invoke (GLib.ClosureInvokedArgs args) [0x00000]
at GLib.SignalClosure.MarshalCallback (IntPtr raw_closure, IntPtr return_val, UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr marshal_data) [0x00000]
at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
at GLib.SignalClosure.MarshalCallback(IntPtr raw_closure, IntPtr return_val, UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr marshal_data)
at Gtk.Object.gtk_object_destroy(IntPtr )
at Gtk.Object.Destroy()
at Gtk.Widget.Destroy()
at FranticXGtk.Forms.MainForm.CloseForm()
at FranticX.Applications.ApplicationManager.StartupException(System.Exception e)
at DeadlineSlave.DeadlineSlaveApp.Main(System.String[] args)
[lustre@bigtower flexlm]$

[/code]

I’ve both chmodded and chowned the deadline repo, as well as several files in the /etc/ folder, with no luck. It was giving me file access errors, but I think I got rid of them, and now it’s a mono issue (or at least it looks that way to me, but then again, I’m not a programmer).

Any suggestions?

4

Which version of Deadline? 3.0 or 3.0 SP1?

I’m currently downloading Fedora 10, so we’ll test it out as soon as we can and get back to you.

Cheers,

  • Ryan
5

Sorry, 3.0 SP1. At least on the test machine anyways.

6

I’ve tested our beta version of 3.1 on fedora 10, and it worked fine - albeit with some permission changes on the /etc/deadline folder. We’re thinking of moving this folder to [install_dir]/share (so if you used the default /usr/local install path, this folder would then be in /usr/local/share/deadline).

The difference between 3.0 and 3.1 is that we’re no longer using GTK#, which the error message you posted seems to stem from. We’re always looking for beta testers, so if you’re interested:
viewtopic.php?f=10&t=1574

We’re finding that the Linux version is much more stable in 3.1 than it was in 3.0, and 3.1 also ships will a full Monitor application.

Cheers,

  • Ryan
7

I figured it’s some sort of permissions issue, since it starts up and display’s the slave UI as root, but not as the installed user (I only have one user set up on that machine, other than root).

Which files did you have to change the permissions on? I ran the install as root, but installed the repo in the user’s home folder, then did “chmod -R 777 deadline_repo/” to make sure that all the files had write permission for everyone. Do you think it would help if I ran chown on the folder, and changed the owner, or since all the files are writeable already, would that not make a difference?

Also, is the actual install folder that you need to change the permissions on?

We’re totally interested in beta testing the Mac version, since we do alot of after fx here as well. I’ll also do some extensive testing with a mixed windows and Linux environment, at home. Expect an email at the beta address within the hour.

8

The only permissions we had to change were those of /etc/deadline for the client install. We were connecting to a repository on another linux box that already allowed for full read/write permissions.

9

hmmm…ok, then I must have done something wrong…I’ll have another go at it as soon as I can