The client and server cannot communicate

Deadline
1

Trying to get our setup happy with Windows machines after being all Mac. When attempting to run DeadlineMonitor10 I get this error message. Which i believe has to do with the certificate we have for the database. Anyone know a work around for this? The repo is running on a Mac.

Could not connect to any of the specified Mongo DB servers defined in the “Hostname” parameter of the “settings\connection.ini” file in the root of the Repository.

The following errors were encountered:

  • 10.1.10.72: The client and server cannot communicate, because they do not possess a common algorithm.
  • deadline.local: The client and server cannot communicate, because they do not possess a common algorithm.
2

So I’ve not been able to figure this out. I started up a new test repo on another Mac and connected to it without issue. Running the same version.
It was recommended that I disable the requirement for a certificate on the repo in the config.conf as well as the connection.ini which I’ll attempting to do tonight. Which me luck.

3

can you ping the hostname of the mac server from the windows machine? If not try changing the hostname in connection.ini to the IP

4

Yes I can ping the host name and IP address from the Windows box. For the production repo as well as the test repo.

I think even though it is running the same version on my production repo it is not the same beast. It’s been upgraded a few times as well as my clients. When I compare the config.conf file between the production (upgraded) and the test (fresh install) I see differences. I posted both of them down below. And I ended up disabling the need for the cert and authorization which now allows everyone to connect to the production repo, even the Windows machine. In hindsight I’m guessing if I had installed an older client version and then upgraded I probably would have been able to connect with the same cert as all of the Macs.

PRODUCTION REPO FILE

---
#MongoDB config file
systemLog:
  destination: file
  #Mongo DB's output will be logged here.
  path: /Applications/Thinkbox/DeadlineDatabase10/mongo/data/logs/log.txt
  #Default to quiet mode to limit log output size. Set to 'false' when debugging.
  quiet: true
  #Increase verbosity level for more debug messages (max: 5)
  verbosity: 0
net:
  #Port MongoDB will listen on for incoming connections
  port: 27100
  ipv6: true
  ssl:
    #SSL/TLS options
    mode: requireSSL
    #If enabling TLS, the below options need to be set:
    PEMKeyFile: /Applications/Thinkbox/DeadlineDatabase10/certs/deadline.local.pem
    CAFile: /Applications/Thinkbox/DeadlineDatabase10/certs/ca.crt
  http:
    #Set to 'true' to enable REST interface
    RESTInterfaceEnabled: false
storage:
  #Database files will be stored here
  dbPath: /Applications/Thinkbox/DeadlineDatabase10/mongo/data
  engine: mmapv1
security:
  authorization: enabled
---

TEST REPO FILE

---
#MongoDB config file
systemLog:
  destination: file
  #Mongo DB's output will be logged here.
  path: /Applications/Thinkbox/DeadlineDatabase10/mongo/data/logs/log.txt
  #Default to quiet mode to limit log output size. Set to 'false' when debugging.
  quiet: true
  #Increase verbosity level for more debug messages (max: 5)
  verbosity: 0
net:
  #Port MongoDB will listen on for incoming connections
  port: 27100
  ipv6: true
  ssl:
    #SSL/TLS options
    mode: requireSSL
    #If enabling TLS, the below options need to be set:
    PEMKeyFile: /Applications/Thinkbox/DeadlineDatabase10/certs/deadline.local.pem
    CAFile: /Applications/Thinkbox/DeadlineDatabase10/certs/ca.crt
  #By default mongo will only use localhost, this will allow us to use the IP Address
  bindIpAll: true

storage:
  #Database files will be stored here
  dbPath: /Applications/Thinkbox/DeadlineDatabase10/mongo/data
  engine: wiredTiger

security:
  authorization: enabled