With beta 6, I want to try installing a repo and client inside our pipeline to make sure Deadline will be able to import and use all of our pipeline code. I was hoping to do this in a semi-sandboxed way, so I have a mongod instance running in a shell (as root), rather than actually having it installed as a service, using the default configuration. I can connect to it from other shells on the same machine, but when I run the repository installer, it is unable to connect to the mongo instance in order to configure the DB.
I grabbed the configuration command it’s running out of the one of the installer logs and tried running it myself (while the installer was still open so I could use the temp unpack of the binaries). This is what I got:
Which version of Mono do you have installed on the machine? We know that the Deadline applications can have a problem connecting to Mongo if an older version of Mono is installed, and I imagine it would be the same when configuring the database.
So from another machine, the repo install fails with the same error, but I can connect to the machine running mongod from the second machine just using the mongo shell.
I ran some tests on a fresh CentOS VM here, following the steps you described with the same version of mono/mongo, and everything worked fine for me.
The only thing I can think of that you might want to double-check is to make sure is that running mono with ‘sudo’ isn’t pointing to a different (and older/outdated) install of mono, because of PATH changes due to the elevation. I only mention this because in following your steps, I actually got bit by mono not being in the PATH at all when I was using sudo; it’s pretty easy to overlook.
If that’s not the problem, I’ll have to add in some more detailed exception messaging in the next build to give us a better idea of what exactly is going wrong.
Thanks for following up on this. I’m embarrassed to say that this turned out to be an oversight on my part, as I had forgotten to yum install mono-data on this internal machine…
The error message had me on a bit of a wild goose chase, as it made it seem like the issue was something simpler (port mismatch, firewall getting in the way, etc.). Going forward, it may be useful to echo a more specific error message in cases where mono components are missing (if possible, of course).
On a similar note, would it be possible for you guys to provide a list of the lightest subset of mono components necessary to run Deadline? If we got to the point that we were ready to deploy this across the facility, I would like to build my own copy of mono to keep the bloat to a minimum, as yum-installing mono-data brings along a lot of dependencies that Ryan mentioned Deadline doesn’t actually need (see this thread for more info http://forums.thinkboxsoftware.com/viewtopic.php?f=86&t=8237).
on Debian I had a similar issue. I’m not familiar with mono nor do I wish to be. 8) mono-data and mono-core don’t appear to be apt packages. installing mono-devel did the trick, but it also installs a slew of other packages along with it, of which 99% are not required I’d think.