AWS Thinkbox Discussion Forums

Centos 6.3 client install - problems beta11

Deprecated Deadline 6 Bug Reports
#1

See other post over repository install… suspect this is related as although its installed I dont think its correct!

Built libdigplus and mono from source (there must be a better way - can we build these into rpms locally).

Installed 64bit client and it all seemed to work.

Check the repository directory was being exported and users can read/write to it without problems.

Ran up the deadline launcher program. This seem to go away and upgrade itself from the server - good sign so far, then it failed with unable to contact mongoDB.

Initially this was pointing to 127.0.0.1 for the mongo database - as this is on another system it’s not going to find it that way so changed the xml file to point to licserver where the mongoDB is running.

Restarted deadline launcher program and get the following output:

[chrish@z600-7 bin]$ ./deadlinelauncher &
[1] 5953
[chrish@z600-7 bin]$ Could not find platform independent libraries
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to [:<exec_prefix>]
Error occurred while updating network settings: An error occurred while trying to connect to the Database (licserver:27017). It is possible that the Mongo Database server is incorrectly configured, currently offline, or experiencing network issues. (FranticX.Database.DatabaseConnectionException)
slave config names: 0
Launching Slave: z600-7
Launcher Thread - Launcher thread initializing…
Error occurred while updating network settings: An error occurred while trying to connect to the Database (licserver:27017). It is possible that the Mongo Database server is incorrectly configured, currently offline, or experiencing network issues. (FranticX.Database.DatabaseConnectionException)
Launcher Thread - Remote administration is disabled
Launcher Thread - Launcher thread listening on port 17060
Could not find platform independent libraries
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to [:<exec_prefix>]
Checking slave startup lock file: /var/lib/Thinkbox/Deadline6/slaves/.lock
Slave startup file is unlocked
Auto Configuration: No auto configuration could be detected, using local configuration
Error occurred while updating network settings: An error occurred while trying to connect to the Database (licserver:27017). It is possible that the Mongo Database server is incorrectly configured, currently offline, or experiencing network issues. (FranticX.Database.DatabaseConnectionException)
Traceback (most recent call last):
File “DeadlineLauncher\UI\Forms\MainWindowLauncher.py”, line 229, in updateScriptsMenuItems
DatabaseConnectionException: An error occurred while trying to connect to the Database (licserver:27017). It is possible that the Mongo Database server is incorrectly configured, currently offline, or experiencing network issues.
at e.a (MongoDB.Driver.MongoDatabase A_0, System.Exception A_1) [0x00000] in :0
at Deadline.StorageDB.MongoDB.MongoScriptsStorage.a (Boolean A_0, ScriptType A_1, FranticX.Collections.Generic.ThreadSafeDictionary`2& A_2) [0x00000] in :0
at Deadline.StorageDB.MongoDB.MongoScriptsStorage.GetGeneralScriptInfos (Boolean invalidateCache) [0x00000] in :0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,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] in :0

Traceback (most recent call last):
File “DeadlineLauncher\UI\Forms\MainWindowLauncher.py”, line 250, in updateSubmitMenuItems
DatabaseConnectionException: An error occurred while trying to connect to the Database (licserver:27017). It is possible that the Mongo Database server is incorrectly configured, currently offline, or experiencing network issues.
at e.a (MongoDB.Driver.MongoDatabase A_0, System.Exception A_1) [0x00000] in :0
at Deadline.StorageDB.MongoDB.MongoScriptsStorage.a (Boolean A_0, ScriptType A_1, FranticX.Collections.Generic.ThreadSafeDictionary`2& A_2) [0x00000] in :0
at Deadline.StorageDB.MongoDB.MongoScriptsStorage.GetSubmissionScriptInfos (Boolean invalidateCache) [0x00000] in :0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,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] in :0

Traceback (most recent call last):
File “DeadlineSlave\UI\Forms\MainWindowSlaveStartup.py”, line 98, in Startup
File “DeadlineSlave\UI\Forms\MainWindowSlaveStartup.py”, line 203, in ConnectToRepository
UnauthorizedAccessException: Access to the path “/var/lib/Thinkbox/Deadline6/deadline.ini” is denied.
at System.IO.File.Delete (System.String path) [0x00000] in :0
at FranticX.IO.File2.Delete (System.String fileName, Int32 attempts, TimeSpan retryDelay) [0x00000] in :0

Checked post 27017 on licserver and got back (either with or without firewall up on both systems):

[root@z600-7 tmp]# nmap -p 27017 licserver

Starting Nmap 5.51 ( nmap.org ) at 2013-02-11 15:27 GMT
Nmap scan report for licserver (192.168.110.110)
Host is up (0.00019s latency).
PORT STATE SERVICE
27017/tcp closed unknown
MAC Address: 00:25:90:69:BD:8D (Super Micro Computer)

Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds
[root@z600-7 tmp]# nmap -p 27017 licserver

Starting Nmap 5.51 ( nmap.org ) at 2013-02-11 15:27 GMT
Nmap scan report for licserver (192.168.110.110)
Host is up (0.00021s latency).
PORT STATE SERVICE
27017/tcp closed unknown
MAC Address: 00:25:90:69:BD:8D (Super Micro Computer)

Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds
[root@z600-7 tmp]#

For the access to path error - as far as I can see it’s open:

[root@z600-7 Deadline6]# ls -al
total 16
drwxrwxr-x 3 root root 4096 Feb 11 13:20 .
drwxrwxr-x 3 root root 4096 Feb 11 13:20 …
-rwxrwxrwx 1 nobody nobody 144 Feb 11 13:20 deadline.ini
drwxrwxrwx 2 nobody nobody 4096 Feb 11 13:56 slaves
[root@z600-7 Deadline6]# pwd
/var/lib/Thinkbox/Deadline6
[root@z600-7 Deadline6]#

Suggestions?

Chris

#2

Edwin has a handy script on github for building RPMs of Mono:
github.com/ThinkboxSoftware/Dea … nux/CentOS

They’re for 2.6.7, but I’m sure they can be easily modified for 2.10.x. We’ll get an updated script there soon.

It definitely sounds like there is still a problem connecting to the MongoDB database. On the client machine, are you able to connect to licserver:28017? This can normally be entered into a web browser to view some mongo stats.

#3

I will take a look at Edwins script on Tuesday.

OK - licserver:28017 fails, even locally and using 127.0.0.1

Checked mongo.conf as webpages are disabled :frowning: nohttpinterface = true so changed to false and 127.0.0.1:28017 worked.

Then changed bind_ip = licserver and magic happens… licserver:28017 locally and remotely works as does deadlane monitor - yippie… just another 38 systems to build!

So, the repository install script needs looking into as it will not accept licserver as a valid hostname/fails to build the mongo DB files, plus if the http interface is supposed to be open then that option needs to be updated.

Thanks for your help Ryan so far.
Next for me will be shotgun integration.

Chris

#4

Hey Chris,

That’s great news!

I just wanted to confirm something I may have missed earlier. Did you install and/or build MongoDB manually, or were you using the MongoDB binaries that were installed by the Repository installer? The reason I ask is that we don’t ship with a mongo.conf file, so I’m curious if you were changing settings for a MongoDB installation that was installed separately. I checked MongoDB’s docs here, and nohttpinterface defaults to false, and bind_ip defaults to all interfaces, so even if a mongo.conf was created automatically by our mongo installation, you shouldn’t have had to make these changes yourself.

docs.mongodb.org/manual/referenc … n-options/

The repository installer will install MongoDB to /opt/mongo, so if your mongodb database is running from another location, that confirms you’re using a different Mongo installation.

That doesn’t change the fact that our installer couldn’t launch the mongodb that it installed itself, but that could explain why this installation was more complicated than it should have been.

Cheers,

  • Ryan
#5

Hi Ryan,

Yes I did go and get a different version of the mongoDB to see if it would help - which it didn’t but the problem was resolved in the end.

Chris

Privacy | Site terms | Cookie preferences