AWS Thinkbox Discussion Forums

Deadline 10.4.0.8 install issues

Hi All,

Installing Deadline 10.4 on Rocky 9 I’m hitting this error

If I look at the docs they say that 6.0.16 is compatible
(Database and Repository Installation (Quick) — Deadline 10.4.0.8 documentation)
The docs also show Rocky 9 is supported
System Requirements — Deadline 10.4.0.8 documentation

I tried to download manually
https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-rhel90-6.0.16.tgz
but this results in the same issue

Just testing this path with one of the engineers this morning - we didn’t have issues getting passed the --version check but did run into issues with the pre-packaged binaries no longer having the mongo shell application included in them, which the installer isn’t prepared for. They’re looking into that as I’m writing so for the moment either use the manual database setup steps or let it download MongoDB.

We tested letting the installer download MongoDB on Rocky 9.4 and it worked. Let us know if that’s not the case.

Also - could I get the installer log? It’ll be in /tmp named installbuilder_*. That should have the actual error that was kicked back running mongod --version. If we’re lucky it’ll be a human friendly message. If we’re not it’ll be a non-zero exit code. :smiley:

1 Like

I scrapped that VM which was on the server, ran a minimal 9.4 on a VM locally, it installs now so not sure what happened on the first vm

dnf install openssl bzip2 tar

I first get this issue

I think this is due to new rhel versions not using init.d, if I try to abort/retry/ignore it gives me this hint

image
I ran that, then re-installed again
dnf install initscripts

It looks like that installed, I’ve no idea what happened the first time

Thanks
Ant

Interesting - our 9.4 test was on a machine with a desktop manager, so very much not a minimal install. Glad tip was actionable and useful from the installer!

HI there, I am having an issue with the database on Windows Server 2016. Trying to upgrade 10.3.2.1. to 10.4.0.8 and it says the database is too old. I am also trying to export settings and it says the database is too old.

I tried looking at the Docs but It is pretty unclear to me how to upgrade the database In Situ. I really need to preserve my existing infrastructure and settings so I can’t just start fresh, as we have production now. I cannot continue to use 10.3.2.1 because the school at which I work (as well as Autodesk licensing) has made Maya 2025.2 the default software and the layer submission is broken under 10.3.2.1

The Deadline installer says I am running wire 4 and it wants wire 6

I have never upgraded MongoDB myself so if someone can point me to a) which distro of Mongo to download for Windows Server 2) which version of MongoDB should I use 3) what commands to use in order to upgrade it, I’d be very thankful.

I am going to try V5 of mongodb to see what happens.

I have also opened an internal ticket for this via AWS paid support.

I didn’t know AWS paid support was an option, is there a web page for this?

You can install another Mongo on the system I think? Is it a VM and can you save and restore from it?

I didn’t know the layers thing was fixed in 10.4, I’ll have to check as I’m having a similar issue

I’m having other issues with Linux, the monitor keeps crashing

malloc(): unaligned tcache chunk detected
Aborted (core dumped)

as well as the /etc/init scripts not starting in Rocky 9

ok, 10.4 works! you should be able to update the 10.3 plugin with the 10.4 maya plugin, just drop it in the custom folder

If you log into your AWS page, under Support there will be an option to buy support, and you can choose from a list of products - one of them will be Thinkbox Deadline

The layering works on 2025.2 on Windows with the new version, I don’t get that annoying “can’t find deadline_submission” error that just stops the submission process.

I’m just not havaing any luck with either exporting data from my online repository or installing 10.4 on top of it.

1 Like

I had the same issue and just used a ubuntu 20.04 lts server image and it installed no problem.

On a proxmox vm make sure you set the cpu type host as well

Privacy | Site terms | Cookie preferences