Deadline 6.0.48466
Windows 7 Pro SP1
“Ok”-button in Configure Repository Options dialog doesn’t close window.
Cheers
Bonsak
Hey Bonsak,
I’m guessing an error must be occurring. We’ll be going through the code soon to have errors like this popup in an error dialog. Currently though, they should be written to the Monitor log. Launch the Monitor, reproduce the problem, and then cancel the repository options dialog. Then select Help -> Explore Log Folder and send us the most recent Monitor log. We’ll take a look.
Thanks!
- Ryan
Thanks for the log! We should have this issue resolved in the next beta release.
Cheers,
- Ryan
Just found the same issue.
Happy to leave it till next release, but how can we get around it so we can tick the Slave settings - slave behavior if pulse is not online - Manually scan for jobs? I have not got Pulse working yet, and none of my slave can pick up any jobs!!
Thanks,
Mark
In Deadline 6, the slaves and monitors no longer use Pulse as a proxy, so you don’t need Pulse running.
There could be a bug in the scheduling code when it comes to Limits. Are you using a machine limit > 0, or submitting the job to any Limits that have a count > 0?
Cheers,
- Ryan
Hi,
Yes just installed Pulse, and not started the jobs.
I have looked and current the 3ds max job was submitted with limits set to 0, the default I believe. I have tried setting it to 2 and 5 and still does not start the job.
Should I try resubmitting the job, not just changing the setting in the monitor? EDIT: resub’d the scene with 5 as the machine limit, and still not starting.
Has anyone else not come across the fact that you can not render a 3ds max job!?
Mark
Hmm… I’m not really sure what the problem could be.
Can you see the job you submitted in the Deadline 6 monitor? Can you see the slave you’re trying to render with in the Deadline 6 monitor? Just wondering if there is any possible cross-over between Deadline 5 and Deadline 6 on your farm that may be messing stuff up.
Yes strange.
The jobs are all sat in the monitor, and the slaves are in their list. Just not picking them up.
Happy to keep trying your suggestions.
Can you send us a screen shot of the Machine Limit section of the job properties for the job? We’ll take a look to see if anything stands out.
Thanks!
- Ryan
Sure, I have just sent to the support email address. If you search for DH SCREENGRAB in the title!
Hope it helps, all I can see is the limit set to 20 as you suggested 0 might be the course.
Mark
Hey Mark,
Thanks! I checked the screen shot, and the only difference I see between it and on my end (where a job is running) is that my Slaves That Can Render This Job is set to 0. I’m rather stumped at this point. We will be doing some major testing with regards to scheduling/rendering very soon. We’re currently focused on getting the Linux UI to behave better (and run on older Linux versions), and getting the Mac version bundled up. After that, we will focus heavily on issues like this.
Cheers,
- Ryan
Hey Mark,
I think we figured this problem out. It ended up being two issues:
-
The slaves were not updating their Limit cache, so they wouldn’t recognize changes made from the Monitor to the job’s Machine Limit, or any global Limits that it used.
-
The slaves could not dequeue jobs with Limits > 0.
Both these issues are now fixed (at least that’s what our testing confirms). We will be including this in the beta 2 release that we hope to get out next week.
Cheers,
- Ryan
Perfect, look forward to testing next week.
It is sad when I look over to other other machine with 6 running and the monitor has jobs init, but the slave is not picking them up!
Mark
Beta 2 was released today, and should fix this dequeing problem. Give it a try and let us know if you continue to have problems rendering!
Cheers,
- Ryan
Installed and noticed it now installs to the root of c:, so deleted the old install in the programs\thinkbox folder.
The alves picked up the update, but sadly still do not lick up the 3ds max job, nor can I make changes in the repository options as the ok button does not work.
I am tempted to uninstall all of 6 and start again to make sure its not user error, but can anyone else confirm these issues too?
EDIT: yes uninstalling everything now, as some strange things happening. Ill remove Mongo to to be safe.
Mark
Installed from scratch. Got an error on the MongoDB service startup. Ignored and seems to have carried on ok, but service is not running and cannot start manually.
The error when starting the service is
Windows could not start the Mongo DB service on local computer
"Error 2: The system cannot find the file specified.!
I am running as administrator.
I think I’ll leave it for now until the issues are fixed.
Mark
We haven’t seen this problem with the installer, and we’ve tried installing a fresh mongo install, as well as installing over an existing one. It should be installing mongo to c:\mongo, and the file the service should be trying to start is “C:\mongo\application\bin\mongod.exe”. Can you check to see if that’s there?
For now, you can run mongo by running this command from a command prompt:
"C:\mongo\application\bin\mongod.exe" --logpath "C:\mongo\data\logs\log.txt" --logappend --dbpath "C:\mongo\data"But we would really like to figure out why the service isn’t working for you. Which OS are you running the repository installer on? Also, does your machine have the SYSTEMDRIVE environment variable defined? That’s what the installer uses to figure out where to install and run mongo from.
I should also mention that you need to manually upgrade the Deadline 6 clients (we mentioned this in the download thread for beta 2). We are currently modifying our auto-update system, so until that’s finalized, both the repository and clients will need to be upgraded manually. It’s possible your slaves were still running beta 1, which would explain why they didn’t pick up the job. Also, the job would have to be resubmitted for the slaves to pick it up.
Cheers,
- Ryan
Ok, so I have tried again. Same errors, image attached of the first error, but when it errored the second time not able to connect to the database and configure, I ran your code and the service then started fine, and the install continued perfect.
I’m running it on Windows Small Business Server 2011 Standard. SP1.
The issue with the “ok” button in the rep options not working seems to have fixed itself, so I think there was definatley something messing up with the old install. Maybe for the beta’s the last version should be uninstalled first?
I’m just about to send a new job to see if it will now render!
Mark
