Forum Replies Created
-
-
18th October 2019 at 11:07 am #23471We found an issue in the logic, please get in touch with me so I can send you a pre-release that address the issue, it will be part of the next service release.
Thanks
17th October 2019 at 11:56 am #23426we will run some additional tests and let you know asap
17th October 2019 at 11:48 am #23422Hi Alex,
This kind of check runs in a multithreaded environment, so it is possible that some instances are skipped because others are being selected in that moment. By pausing/clicking into Muster, you’re forcing the “selection logic” to be run again and further instances are picked. The selection logic has its own timeout and will re-run on its own after a couple of seconds. I suggest you to wait to see if the instances start on their own, while running in a production scenario this should not be a problem.
11th October 2019 at 8:01 pm #23155Could you open a ticket in the support section ? I think we may need to arrange a fast remote session to solve this, from there no other options
11th October 2019 at 7:26 pm #23152Did you follow my suggestion to check the T & J columns of the nodes ? Are the nodes idle ? (Green). Do you also see a blue moving bar in the bottom right corner of Console ? (that means Dispatcher is running and processing the queue…)
11th October 2019 at 9:31 am #23124you can download 11511, and use into a template:
self.setLicensesMode(MTemplateAPI.MTemplate.kTemplateLicenseCountNodes
10th October 2019 at 9:39 am #23073Hi Alex,
Muster 9.0.14-11511 will implement a new model for license counting configurable into the MTemplate object. Further info in the release note, it will be released between today and tomorrow, if you get in touch with me on my email, I can send you the direct download info, the license is already into your account.
Cheers!
9th October 2019 at 9:38 am #23025If you got the Maya2017 error, it’s possible that the template has gone into the client “exclusion” list. Did you have a red cross under the T or J column ? Try to right click on the node and PURGE the templates and jobs exclusions lists
7th October 2019 at 4:29 pm #22942Hi Andres,
You get only some jobs stuck into the queue, or all Maya Arnold are stuck ? If so, I suggest you to check the renderclients preferences, and check that the Maya Arnold template is enabled. You can also right click on one node and select “supported engines” to see if that particular template is enabled.
If only the jobs submitted by users are stuck, then you should look at the users settings about the limitation on a particular engine and/or maximum jobs.
4th October 2019 at 11:14 am #22790error = MTemplateAPI.MTemplateError(2, ‘Error’, MTemplateAPI.MTemplateError.kTemplateErrorTypeError) error.addErrorAction(MTemplateAPI.MTemplateError.kTemplateErrorRequeueChunk); return error
4th October 2019 at 9:12 am #22784Hi Alex,
That sounds a reasonable request, we’ll see if we can push this change into 9.0.14 LTS for the upcoming patch release.
Thanks
18th September 2019 at 7:56 pm #22051nice one, but you have the base class into another template file ? or you just import it from another module ? Be aware that templates are synchronised and loaded in alphabetical order 😉
18th September 2019 at 11:08 am #22032Hi Claus
Best thing under that circumstances is to use multiple templates for multiple versions. Otherwise, you can check the licensing limits on your own using onValidateJobDependancies , in that function, you can check how many clients are rendering a certain engine on the jobs, and allow on deny the job/chunk.
16th September 2019 at 10:39 am #21933I confirm a regression bug we just fixed, we uploaded a new build for 9.0.14, you can just re-download it from the web site (linux and windows installers are fixed, mac and rasp will come later). You need to reinstall the Dispatcher (or instead of doing a full installation, install it on another machine and replace the MDispatcherCore.dll file after stopping the service).
Thanks for reporting the bug!
16th September 2019 at 9:47 am #21930We are checking if there’s a regression bug in the current 9.0.14 , I’ll let you know during the day or tomorrow, but I’m suspecting so.
-
