We use cookies and similar tools to enhance your experience, provide our services, deliver relevant advertising, and make improvements. Approved third parties also use these tools to help us deliver advertising and provide certain site features.
Customize cookie preferences
We use cookies and similar tools (collectively, "cookies") for the following purposes.
Essential
Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms.
Performance
Performance cookies provide anonymous statistics about how customers navigate our site so we can improve site experience and performance. Approved third parties may perform analytics on our behalf, but they cannot use the data for their own purposes.
Allowed
Functional
Functional cookies help us provide useful site features, remember your preferences, and display relevant content. Approved third parties may set these cookies to provide certain site features. If you do not allow these cookies, then some or all of these services may not function properly.
Allowed
Advertising
Advertising cookies may be set through our site by us or our advertising partners and help us deliver relevant marketing content. If you do not allow these cookies, you will experience less relevant advertising.
Allowed
Blocking some types of cookies may impact your experience of our sites. You may review and change your choices at any time by clicking Cookie preferences in the footer of this site. We and selected third-parties use cookies or similar technologies as specified in the AWS Cookie Notice.
Having an issue with our Repository it seems. Any user trying to access Deadline Monitor is seeing this issue:
I tried restarting the machine hosting our Database, freeing up some of the disk space, and then attempted to restart the Database Service but I’m seeing this error:
I’ve been checking firewall settings and looking at logs to no avail. Does anyone have any idea what might be causing this?
In the Deadline default port 27100 is used and is connected to default by ssl and ca certificates. You can connect as a test when you run mongo/bin/deadline_mongo.bat.
That script does work as a good test to see if the Database is running.
I think if you’re hitting that error, you should check out the database log. Info about that is in this duplicate thread:
Since that went down a certain path, I’m not sure if it make sense to continue the conversation there, but we will want to see the Database log all the same. Can you provide the log and we’ll take a look? It may include job or machine information so feel free to provide just the errors you find there.
Ah, yes it seems that we were running low on disk space where our Repository was stored causing a mongodb.lock file to be created which was blocking the Service from being restarted. Had to increase disk space quite substantially to the drive. It seems when our Deadline service was set up it was under-estimated how much space would be required.
Luckily I seem to have it under control. Thanks for the input folks!