[7.1.0.35] Integration connection to shotgun fails

Deadline
1

Hello,

When trying to connect to shotgun, I have this error.

First a popup containing :

Then a trace that says :

It’s the same if I test the connection from the monitor’s Script->Integration->“Test Integration Connection”

Any clue ?

2

Whenever I’ve seen problems like this revolving around the ‘hashlib’ module, the root cause has always been the OpenSSL libraries.

Can you check which versions of libcrypto and libssl you have installed on your system, and try installing version 1.0.1, if it isn’t already on there?

You could also try setting “No SSL Validation” to ‘True’ in the Shotgun Event Plugin configuration, which has worked around similar issues in the past.

Cheers,
Jon

3

Hello,

zypper result :

libssl and libcrypto locations :

Am I missing something ?

Thank you,
Pierre

4

Have you tried setting “No SSL Validation” to ‘True’ in the Shotgun Event Plugin configuration? Did that make a difference?

I totally forgot we’re actually shipping with a copy of libssl/libcrypto, which really shouldn’t be causing these issues.

I’m guessing those particular copies aren’t loading for whatever reason, might be that they’re looking for other shared libraries that are missing/older on openSUSE.

Can you run ldd on the copy of libssl/libcrypto that we ship, and post the output here?

ldd /opt/Thinkbox/Deadline7/bin/libssl.so.6
ldd /opt/Thinkbox/Deadline7/bin/libcrypto.so.6
5

After doing some testing, I was able to replicate this on a local openSUSE VM. It looks like we might be shipping the wrong (old) version of openSSL with Deadline 7.1.

I’m also not sure why, but our build of python is trying to link against libssl.so.10 (and libcrypto.so.10), instead of libssl.so.1.0.0.

I was able to work around this by creating some symlinks to trick it into finding the correct libraries:

[code]sudo ln -s /lib64/libcrypto.so.1.0.0 /lib64/libcrypto.so.10
sudo ln -s /lib64/libssl.so.1.0.0 /lib64/libssl.so.10

sudo ln -s /lib/libcrypto.so.1.0.0 /lib/libcrypto.so.10
sudo ln -s /lib/libssl.so.1.0.0 /lib/libssl.so.10
[/code]

We obviously need to fix our installers, but hopefully this should let you work around this problem in the short-term.

Cheers,
Jon

6

Hurray !

The workaround works, thank you very much.

For the record :

Cheers,
Pierre