While going through the installation of the repository, i was stuck when it asked me to install MongoDB, because the server on which I’m installing The repository doesn’t have Internet, I’d like to know if the Internet connection is a most, and if the machine that are going to render need to be connected to the Internet to be able to render, cause the problem would be a discontinuity in our Internet connection, we frequently have problems with the Internet going off(country issue).
Deadline 5 didn’t need MongoDB, am i correct?, do we necessarily need MongoDB, shouldn’t it be an option(in the installation) for a country with bad Internet connection?
And It doesn’t seem to be possible to install it on windows server 2003 sp2
MongoDB is a must, but it doesn’t need an internet connection. The slaves and workstations communicate with the MongoDB database over your local network, the same way that they connect to the repository over the network.
Deadline 5 just used the file-based repository to store all the data. In Deadline 6, most of this data is now stored in the database to improve performance and scalability. However, the file-based repository is still used to store the Deadline plugins, job auxiliary files, and log files.
Hope that helps clarify things!
- Ryan
But We still have a problem with its installation, cause it cannot be installed on windows server 2003 Sp2.
Tryed a non bundled version for monodb?
http://www.mongodb.org/downloads
If this does not work use a linux box. (2k3 is some kind of old.)
Someway easy to set up, I have a CentOS6 VM.
Right now it does the following:
- Sharing the repo via smbd
- Runnung mongod
- Running pulse
First jobs rendered with no problems.
I used EPEL repos (always like this better then bundled version because I actually have control over it and it gets updated).
Since the shared repo is still necessary, I would opt for replacing our current pulse vm with pulse + mongodb and leave the repo share on our file servers for production.
If somebody is interested I could post the machine as an image plus libvirt config somewhere sometime this week.
Cheers,
Helge
I would try installing MongoDB by itself. My suspicion would be that you are missing .NET 4 on an ancient box like that.
We’ve already updated to .net 4.0, We’re gonna try installing it manually than, and see how it goes.
If you could send us a screen shot of the error message, as well as the installer log, we can take a look to see what went wrong. The installer writes its log to the %TEMP% folder.
Cheers,
- Ryan
Finally we were able to make it work, we installed mongoDB manually, it was quite a headache but it worked, the big issue was trying to install the db on another partition, in fact it didn’t work, even after following the guide, we finally decided to keep the default installation of the database on the C:( we had to free some space in order to let it install correctly).
The second issue was the ip connection, we didn’t know how to change it in the manual installation, we finally had to go through the installation of the repository and choose to connect to an existing db with the correct ip, and it worked.
Glad to hear you were able to get it working!
That’s the way we would actually recommend doing it, but it can be done manually. The dbConnect.xml file that contains these settings can be found in \your\repository\settings.
Cheers,
- Ryan