Deadline 10 database service constantly stopping

Deadline
1

Hey, I’ve suddenly started having this issue where this service - mongod.exe won’t stay running and therefore the renderfarm won’t work. If I restart the service the farm is active and I can connect to view it via the monitor - but normally after a few seconds the service then stops.

I found this super helpful post below, which helped me figure out the mongod.exe was the issue. We did have a power cut which I think might have caused the problem but I don’t know how to run the repair command on the MongoDB.

Any help would be amazing.

Phil

2

What do the logs say?
C:\DeadlineDatabase10\mongo\data\logs
Is it failing to launch the service? did the firewall block the launch?
Which version OS and Deadline/Mongo?

1 Like
3

Hi Anthony,

Thanks for your reply. I have looked at the log but not sure what it means - not sure its a good idea to upload it publicly here?

The service starts without issue, but then very soon after it stops.

Am using windows 11.
Deadline Client Version: 10.1.23.6 Release (773a6289d)
Mongo DB 4.2.12.0

4

The system requirements advise not to use non-server based OS as they’ll have a connection limit, although with less than 10 users this shouldn’t be a problem

https://docs.thinkboxsoftware.com/products/deadline/10.3/1_User%20Manual/manual/system-requirements.html#system-requirements-windows-non-server-ref-label

Mongo 4/5 don’t appear to be on the supported list for Windows 11 either

Do you have a server you can run the DB on?

5

I ran into this as well, and Gemini the Intern helped me through it. This is the basic process it led me through, and that worked for me:

  • Go into Services (services.msc), and stop the Deadline 10 Database Service.

  • Find your “Data” and “Bin” folders

The bin folder is where mongod.exe lives, which for me was:
C:\DeadlineDatabase10\mongo\application\bin

The Data folder on my end was:
C:\DeadlineDatabase10\mongo\data

  • Make a copy of your data folder & place it somewhere safe in the event that the repair function makes things worse.

Run the Repair Command

  • Open the Command Prompt as Administrator.
  • We’re going to navigate to the location of the bin folder; I entered the following, adjust the path accordingly:

cd "C:\DeadlineDatabase10\mongo\application\bin"

  • Now we run the repair command, using the path to the data folder:

mongod.exe --dbpath “C:\DeadlineDatabase10\mongo\data” --repair

The process will scroll a lot of text. You are looking for a series of lines at the very end that say something like:

“shutdown: going to flush diaglog…” “shutdown: going to close sockets…” “shutdown: going to close listening sockets…”

If successful, it will finish and return you to the command prompt.

rvncconnect_EHGnK2SMMD
rvncconnect_EHGnK2SMMD1399×585 99.7 KB

From Gemini: “If you see an error about mongod.lock, the repair tool usually fixes this automatically. If it fails specifically saying the lock file is the issue, you may need to go into your data folder and manually delete the file named mongod.lock.”

Go back to Services & Restart the Deadline 10 Database Service.

1 Like