Upgrade from 10.2.1.1 to 10.4.0.10 - Deadline Client error connecting to db

Deadline
1

I did the update (ubuntu) and connected to the existing database. Direct connection.

db version v4.2.12
git version: 5593fd8e33b60c75802edab304e23998fa0ce8a5
OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020

With Deadline 10.4 clients, they don’t launch…

2024-11-18 16:15:14: Video Card: Parsec Virtual Display Adapter
2024-11-18 16:15:14: Deadline Launcher 10.4 [v10.4.0.10 Release (aa82ae82b)]
2024-11-18 16:15:14: ERROR: DataController threw a configuration exception during initialization: Error encountered when loading the configured Client Certificate (<Deadline10Client.pfx location>). It is likely either an invalid x.509 certificate, or the wrong passphrase was provided.
2024-11-18 16:15:14: Full Error:
2024-11-18 16:15:14: The specified network password is not correct. (Deadline.Configuration.DeadlineConfigException)

If I install 10.2 again, the launcher and workers run fine. I am thinking I need to update the mongo db version that has a newer openssl version?

thanks!

2

when upgrading from 10.3 or less to 10.4, you mostly need to isntall a new database, back up before upgrading.

3

I was always wondering how one upgrades the mongo db version. It seems there is no way to do that with the deadline installer but rather with some weird manual process. Or is there something that I am missing?

4

I am going to try this process on the weekend. https://awsthinkbox.zendesk.com/hc/en-us/articles/1500008016222-How-Do-I-Upgrade-MongoDB-to-version-4-2-from-3-2

5

Ah, very interesting. Please let us know how it went.

6

The mongodump (4.2.12) that was installed with deadline on ubuntu 18.04 did not appear to work after trying a lot of options. I installed a newer one, and it partially worked. At that point I gave up.

I was a bit ambitious and tried ubuntu 24.04, which required a manual install of mongodb with preinstalled binaries. However, mongod was core dumping which is due to v5+ requiring avx instruction set and I was installing on hypervisor server that didn’t support it.

At this point I decided maybe i should stick to supported OSs. Ubuntu 20.04 it is…

It just installed… now will the mongodb version that gets installed be compatible with openssl 1.1.1f? I hope so…

7

Sadly, I still have the same issue after creating a new database

db version v6.0.16
Build Info: {
“version”: “6.0.16”,
“gitVersion”: “1bbe71e91a41b097b19d036dee47b861b3f27181”,
“openSSLVersion”: “OpenSSL 1.1.1f 31 Mar 2020”,

If I install the 10.4 client, launcher doesn’t open.

2024-11-22 18:32:52: Deadline Launcher 10.4 [v10.4.0.10 Release (aa82ae82b)]
2024-11-22 18:32:53: ERROR: DataController threw an unexpected exception during initialization: FranticX.Database.DatabaseConnectionException: 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.
2024-11-22 18:32:53: The following errors were encountered:
2024-11-22 18:32:53: * 10.10.1.10: The credentials supplied to the package were not recognized
2024-11-22 18:32:53: * deadline10: The credentials supplied to the package were not recognized
2024-11-22 18:32:53: at Deadline.StorageDB.MongoDB.MongoDBUtils.HandleException(String serverAddress, Exception ex, String optionalMessagePrefix)
2024-11-22 18:32:53: at Deadline.StorageDB.RepositoryConnect.DirectRepositoryStorage.a(DirectConnectionSettings ov, Int32 ow, X509Certificate2 ox, X509Certificate2 oy)

etc…

but if I install 10.2 client on the same machine, with the same settings it connects fine to the old mongo v4 sb and the new v6 db. I am thinking of just using 10.2 client with 10.4 repo… or hack the 10.2 repo to support the newer apps.

It really is a mystery to me!

8

I did a test where -

Require client authentication via SSL/TLS [Y/n]: n

and now the deadline client 10.4 works!!

The supported Ubuntu 20.04 only has openSSL 1.1.1f, so you have to manually build the newer versions. What do I need for 10.4 windows clients?

On the Ubuntu mongo db server, I now have

jason@deadline10:/install$ openssl version
OpenSSL 3.0.15 3 Sep 2024 (Library: OpenSSL 3.0.15 3 Sep 2024)

However, the mongodb that the deadline repo installed says it using 1.1.1f still. Anyway, time to learn about mongodb installation.

tl;dr getting closer to a win, but feeling very insecure about it.

9

latest test instance using ubuntu 22.04 (not officially supported, but getting desperate)

"version": "6.0.19",
"gitVersion": "a7ada5ff3a4d8a1e2ed88f86bd6b3d1d16cb43c6",
"openSSLVersion": "OpenSSL 3.0.2 15 Mar 2022",

Still the same issue with the 10.4 window client when using ssl. Next test will be using a RCS instead of direct.

10

RCS test. Installed RCS on same ubuntu server as the mongodb.

Full Error:
error:10080002:BIO routines::system lib
Deadline Remote Connection Server will try to connect again in 10 seconds…
ERROR: DataController threw a configuration exception during initialization: Error encountered when loading the configured Client Certificate (/opt/Thinkbox/DeadlineDatabase10/certs/Deadline10Client.pfx). It is likely either an invalid x.509 certificate, or the wrong passphrase was provided.

On both the ubuntu server and windows client, I can view the certificate with passphrase using

openssl pkcs12 -info -in Deadline10Client.pfx

maybe i should try redhat 9!

11

It is definitely something to do with the 10.4.0.10 client and ssl certificates that is causing my issue.

I installed 10.3.2.1 client and I can connect to the database using ssl.

12

10.4 is just full of surprises for us!
A total no go on max 2024, doesn’t even open the file:

2024-11-26 20:21:04: Scheduler Thread - Render Thread 0 threw a major error:
2024-11-26 20:21:04: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2024-11-26 20:21:04: Exception Details
2024-11-26 20:21:04: RenderPluginException – Error: 3dsmax: Failed to load max file: “C:/ProgramData/Thinkbox/Deadline10/workers/W10-TR3-256-096/jobsData/6746606d3c359bffc93dcaf1/3175_Interior_08.max”
2024-11-26 20:21:04: at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)
2024-11-26 20:21:04: RenderPluginException.Cause: JobError (2)
2024-11-26 20:21:04: RenderPluginException.Level: Major (1)
2024-11-26 20:21:04: RenderPluginException.HasSlaveLog: True
2024-11-26 20:21:04: RenderPluginException.SlaveLogFileName: C:\ProgramData\Thinkbox\Deadline10\logs\deadlineslave_renderthread_0-W10-TR3-256-096-0000.log
2024-11-26 20:21:04: Exception.TargetSite: Deadline.Slaves.Messaging.PluginResponseMemento d(Deadline.Net.DeadlineMessage, System.Threading.CancellationToken)
2024-11-26 20:21:04: Exception.Data: ( )
2024-11-26 20:21:04: Exception.Source: deadline
2024-11-26 20:21:04: Exception.HResult: -2146233088
2024-11-26 20:21:04: Exception.StackTrace:
2024-11-26 20:21:04: at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgt, CancellationToken bgu)
2024-11-26 20:21:04: at Deadline.Plugins.SandboxedPlugin.StartJob(Job job, CancellationToken cancellationToken)
2024-11-26 20:21:04: at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajx, CancellationToken ajy)
2024-11-26 20:21:04: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

13

A side note: same job in Max 2022 gave us an intermittent error (it will pop up a few times but then start to render)
Error: RenderTask: Unexpected exception (Trapped SEH Exception in CurRendererRenderFrame(): Access Violation

14

Not sure what to do … was 10.3 any better? I don’t mind downgrading, just to keep the render queue going

15

Sorry to hear that. Deadline and Max was the original dream time…

My issue was different, but one thing i noticed in my ordeal was since I was switching from ssl to no ssl, i couldn’t just run the client with the new settings. I remember seeing some error related to C:/ProgramData/Thinkbox/Deadline10/workers/ .

In my case I clean uninstalled deadline client by running the uninstaller, then deleting %localappdata%/Thinkbox , Program Files/Thinbox, ProgramData/Thinkbox . To delete program data, I had to change permissions so that I could delete that workers folder. I then ran my deployment with is a silent install with the settings. This is the same as manually installing it.

16

i might as well try that, thanks!