Deadline 6.0.0.48466
Mono 2.10.5
Fedora 15 x64

I am currently unable to launch the Monitor after configuring my Mongo server and repository. When I try to launch it, I get a split-second of the splash screen, a popup dialog that says “The classes in the module cannot be loaded. Deadline Monitor will now exit.”, and the following dumped to the terminal:

[code]System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
Initializing…
System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
Connecting to repository…
Exception on Startup: The classes in the module cannot be loaded. (System.Reflection.ReflectionTypeLoadException)
at (wrapper managed-to-native) System.Reflection.Assembly:GetTypes (System.Reflection.Assembly,bool)
at System.Reflection.Assembly.GetTypes () [0x00000] in :0
at Python.Runtime.AssemblyManager.ScanAssembly (System.Reflection.Assembly assembly) [0x00000] in :0
at Python.Runtime.AssemblyManager.AssemblyLoadHandler (System.Object ob, System.AssemblyLoadEventArgs args) [0x00000] in :0
at System.AppDomain.DoAssemblyLoad (System.Reflection.Assembly assembly) [0x00000] in :0
at Deadline.Controllers.DataController…ctor (System.String repositoryRootDirectory) [0x00000] in :0
at Deadline.Monitor.MonitorManager.Connect (System.String networkRoot) [0x00000] in :0
at a.a (System.String[] A_0) [0x00000] in :0

Deadline Monitor will now exit.[/code]

followed by the process hanging indefinitely.

I can’t even query the repository using something as simple as deadlinecommand Slaves. When I try this (either from a secondary slave or from the repository machine itself, which is also currently hosting the DB), I get:

[code]Error: An error occurred while trying to connect to the Database.

It is possible that the Mongo Database server is incorrectly configured, currently offline, or experiencing network issues. (FranticX.Database.DatabaseConnectionException)[/code]

I can run mongo manually on either machine and connect to my running mongo daemon using the port specified, and the config settings in [REPO_ROOT]/settings/dbConnect.xml include the correct hostname and port.

Is there some kind of DB initialization script that needs to be run to actually set up the database? When I run show dbs from a mongo shell connected to my DB server/repo machine, it simply says “local (empty)”, so the deadlinedb pointed to by the dbConnect XML config doesn’t seem to be there.

Any thoughts?

I think the “The classes in the module cannot be loaded” error is due to missing Mono 4.0 profiles. How did you install Mono on the machine? Was it through Fedora’s package manager, or did you build from source? If it was from the package manager, did you install the mono-complete package, or did you pick specific packages manually?

That database connection error could be related to this problem, so we’ll tackle it after we get this problem sorted out.

Note that we still have to test on Fedora internally. We have already discovered that we’re building against a version of glib that is too new, so we’re fixing that issue now, and then we’ll move on to testing on all the Linux OS’s we plan to support. By beta 2 or 3, the Linux version should start to stabilize.

Cheers,

• Ryan

Initially, I simply installed mono-core (and libgdiplus as a dependency) via yum. I’ve been under the impression that mono-core is now the only Mono component required by Deadline 6… is this not actually the case? Would you mind providing the bare minimum Mono subset that needs to be installed?

Thanks,

-Nathan

I don’t have a problem building it all from source if that’s what’s necessary, but I’m hoping to try and keep deployments as simple as possible.

OK, just as an update, I installed mono-data via yum, and that seems to allow the GUIs to start now. In case anyone is curious, the total dependency list for mono-data is:

Installing: mono-data Installing for dependencies: mono-data-sqlite mono-extras mono-mvc mono-wcf mono-web mono-winforms mono-winfx

The UIs ain’t pretty, but I’ll post separately for those issues.

Thanks again

It looks like the mongo driver we use requires the data component.

Just to confirm, you just have mono-core and mono-data, along with their dependencies, and that’s working well (minus the UI issues)? We will update our installation docs to mention this.

We didn’t realize that those two packages brought libgdiplus and winforms with them, but be assured that we won’t be using them.

Cheers,

• Ryan

You’re correct. On Fedora, the “do-it-all-at-once” command should simply be yum install mono-core mono-data

For ultimate purity, installing only mono-data should properly resolve mono-core as a dependency (and thus libgdiplus as well).