Issue connecting to RCS after reverting to 10.3.1.4 from 10.4.2.2

Deadline
1

Hello.
Having an odd issue here.
We’ve been running deadline 10.3.1.4 connected via RCS on port 4434. This has been relatively problem free for a while now.(Running rocky 9.3, now rocky 9.5 client side workstation)

I recently tested a centralized launch of 10.4.2.2 launcher/monitor on my workstation. I tried connecting to the 10.3.1.4 rcs and it wouldn’t let me because of version compatibility reasons(which makes sense).

I then switched back to my locally installed 10.3.1.4 launcher and was unable to reconnect to our 10.3.1.4 rcs. I checked to make sure I could ping the rcs server on port 4434 and all is good there. There is no information in the launcher log related to why I can’t connect, it just doesn’t do anything when I try to connect and remains connected to the repo directly.

I reinstalled 10.3.1.4 locally, hoping that this would solve the situation. But I’m still hitting the same issue.
Running deadline command yields the error:

deadlinecommand -ChangeRepository Proxy "SERVER:4434" "/server/Deadline10RemoteClient.pfx" "PASSWORD"
Deadline configuration error: Failed to establish connection to SERVER:4434 due to a communication error.

Is there anyway to get more verbose info?
I checked the RCS logs and don’t see anything there either, so my hunch is that it’s some issue on my local configuration.

Any help would be greatly appreciated.
Thanks,
-Jake

2

If you are reinstalling the 10.3 client locally, uninstall first, then browse for any leftover thinkbox files and delete them, then install the client again. I had the same issue and after uninstalling there were still some files left that weren’t removed by the uninstaller. After a clean reinstall I could connect again.

I forgot where exactly those files were, but I hope it can still help you.

3

Thanks @Dominic for the quick reply and suggestions.
I gave this a shot: full uninstall, removed the following folders:
/var/log/Thinkbox
/var/lib/Thinkbox
~/.config/Thinkbox
~/Thinkbox
Workstation reboot.
I then installed 10.3.1.4 and unfortunately hit the same behavior.
I can connect directly to the repository, but still cannot connect via the rcs(the way all of our other clients are connected).

Interestingly the command line:

deadlinecommand -ChangeRepository Proxy "SERVER:4434" "/server/Deadline10RemoteClient.pfx" "PASSWORD"

now doesn’t show any error. But the connection to the rcs is still not established. Logs aren’t showing anything related to the attempted connection or why it’s failing.

Oddly, I’m able to launch a monitor connected to the rcs in question, just can’t set the launcher/worker to use the rcs.