Fusion Linux RenderSlave woes

Deadline
1

Hey Ryan, how’s it going, got a great problem again :slight_smile:

We’re trying to get Fusion for Linux going, which is, well, not going at all.

For some reason Eyeon decided to go for a WINE solution rather than a native Linux solution, which is a painful experience to say the the least (it’s one of those deal breakers that actually makes me want to switch to Nuke, investments we made be damned.)
Anyhoo, we got the RenderSlave to run manually, so you can connect to it through the build in RenderManger of Fusion, but that manager doesn’t check for crashed nodes, hence we try to get it going in Deadline.

And there lies the rub, i can’t get it going. I get this message :

[code]=======================================================
Error Message

Error in RenderExecutable(): Wine could not be found in the path on this machine, it is required to run the Linux version of Fusion

=======================================================
Slave Log

0: Task timeout is disabled.
0: Loaded job: futest (999_050_999_42b28c92)
0: INFO: StartJob: initializing script plugin Fusion
0: INFO: About: Fusion Plugin for Deadline
0: INFO: Starting monitored managed process Fusion
0: INFO: Any popup windows with titles matching the regular expression “.Queue.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Render Manager.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Editor.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Precision.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Taper.” will be ignored
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: False
0: INFO: Creating New Console: False

=======================================================
Error Type

ManagedProcessAbort

=======================================================
Error Stack Trace

at FranticX.Processes.ManagedProcess.Execute (bool) <0x0073b>
at FranticX.Processes.MonitoredManagedProcesses.StartMonitoredManagedProcess (string,FranticX.Processes.ManagedProcess) <0x000f3>
at Deadline.Plugins.ScriptPlugin.StartMonitoredManagedProcess (string,Deadline.Plugins.ManagedProcess) <0x0032b>
at (wrapper dynamic-method) object.CallSite.Target (System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,IronPython.Runtime.CodeContext,object,string,object) <0x000fe>
at System.Dynamic.UpdateDelegates.UpdateAndExecute4<IronPython.Runtime.CodeContext, object, string, object, object> (System.Runtime.CompilerServices.CallSite,IronPython.Runtime.CodeContext,object,string,object) <0x00494>
at (wrapper delegate-invoke) Microsoft.Scripting.Utils.Func`6<System.Runtime.CompilerServices.CallSite, IronPython.Runtime.CodeContext, object, string, object, object>.invoke_object__this___CallSite_CodeContext_object_string_object (System.Runtime.CompilerServices.CallSite,IronPython.Runtime.CodeContext,object,string,object) <0x00096>
at (wrapper dynamic-method) object.StartJob$2649 (System.Runtime.CompilerServices.Closure,IronPython.Runtime.PythonFunction,object) <0x052ef>[/code]

even though WINE is installed (the special eyeon version), and we run the launcher that came with the Linux RenderSlave install (it basically should take care of the paths), however, it doesn’t seem to do anything, it even looks like it is starting a a completely different program, even though it seems to start the “/opt/eyeon/bin/RenderSlave64_6.4” program (as set in the Deadline plugin config).

Running Deadline 5.2.0.47700, Fusion 6.4 (build 1104 64bit, CentOS version, with wine 1.3.21.2-2 for RHEL, CentOS (17th October 2011)) on CentOS 6.3

Hope you guys have some experience with this and can help out.

Thanks in advance,

Sven

2

Hey Sven,

Honestly, you’re probably the first person to try getting Fusion on Linux to work with Deadline. We had started work on supporting it with Deadline back when we were part of a production studio because there was the potential for our render farm to move to Linux. We put the basics in there, but it was never put through its paces. We were actually considering dropping it in Deadline 6 since no one was using it. :slight_smile:

What is the name of Fusion’s wine executable? Is it just “wine”, or is it something else?

Cheers,

  • Ryan
3

Wow, you sure know how to get my hopes up Ryan :smiley:

the executable is wine, but it is located in eyeon’s own wine distribution, located in /opt/eyeon/wine/bin

maybe i’m trying to start the program in a way Deadline doesn’t know how to work with? i start the render slave in deadline using the /opt/eyeon/bin/RenderSlave64_6.4 executable.

If you’re interested, the installers are located for download on eyeon’s site (on page 2 of the Fusion page i believe).

cheers,

Sven

4

Hey Sven,

Let’s try getting it to work with the FusionCmd plugin first. This is the command line Fusion plugin, and it should be much simpler to debug this with it. When we get it working, we can apply the same knowledge to the regular Fusion plugin.

When configuring the FusionCmd plugin, you’ll want to point to Fusion’ ConsoleSlave executable (assuming that’s shipped with the Linux version too). Then to submit to the FusionCmd plugin, you’ll want to enable the “Command Line Mode” option in the submitter.

If you get the same error you’re getting now (which you probably will), send us the error report and we’ll go from there.

Thanks!

  • Ryan
5

Alrighty, going to try that later on (at the moment the build in render manager works, needs some baby sitting, but deadlines loom.)

When the fusion rendernodes become available i’ll have it render via commandslave and send you the log.