Update over here. The dev team tells me those changes were cosmetic which is good.
Currently I’m going to experiment with purposely putting whitespace into my limits at submission and see if that will break. If others can enable verbose logging and send it my way, that would be helpful as well. To enable it:
Great work Makoto on noticing that this only affected 3DS Max. It seems that if the LimitGroup property of the job info file ends with a space, it will prevent Pulse from starting the Slave with the exact error. I am able to reproduce this exactly.
I will try to find out what changed in the SMTD so you can begin working now, and we can fix it properly in core after that.
For this problem specifically, we are trying to make the change in the SMTD first, then adjusting changes in the core code from there. I’m actively working with the development team on this.
For the remaining issues outside of this thread, we are working through them as well. Thanks for raising them!
I think we have a fix here, so I’ll need some testing. It’s easier than I’d expected to work around.
It seems that any non-existing limit group (spaces or not) that is added to a job will cause machine wake-up ignore that job.
Now, the SMTD has a new feature that automatically adds some limits. My guess is that the workaround is to uncheck all of these in the “limits” rollout:
I tried submitting a new job with all the limit checkboxes turned off but it still didn’t work. I did notice though that when I went into the Job Properties max was still listed in the Required Limits. I tried a few different combos of check boxes, all off, all on and some in between and max was always listed under Required Limits.
When I moved it to the left column under Limits List (which makes it disappear btw) it worked! The machines all started up as usual.
To be honest, I’m not sure what these limits do. Is there a way to submit a job without having max listed under the Required Limits or is that a bug in SMTD?
I’ve got a quick fix on the integration-side until the changes make their way into core.
Make backups and copy the two included files into
DeadlineRepository10/submission/3dsmax/Main
This will turn all of those auto-limits off by default, and fix a few issues with setting them (ie. the ‘max’ limit not turning off). Due to sticky settings, the options might be enabled the next time you open the dialog, but any new user, or subsequent dialog will have them off. Let me know how it goes.
We had this issue, I just added max and vray limits with unlimited resources. Stumped me for a while as I couldn’t work out why it was suddenly applying a limit!
Is it the same issue here Makoto? I’m just curious if we missed an auto-limit here. Also, without testing the normal job it could very well be that the existing limits are causing you trouble.
We’ll still be fixing this in core, but the script adjustment Morgan provided should get you working so a base test would be very much appreciated.
Can post a job info file or double check what limits are on that job and if they’re correct (ie. The limits exist in your repository)?
My mitigation fix won’t turn off auto-limits if they’re saved as sticky settings, it just changes their default behaviour, so you’ll still need to turn off those options in the submitter if these limits don’t exist for you.
My fix also can’t remove limits from existing jobs. To make them work though, you can modify the job properties to remove the limits that don’t exist, or you can make dummy limits.
Sorry I asked again Makoto. I was hoping that you could give some more details based on what we have learned from this problem. As Morgan asked, your job info file or a screenshot of your job’s “Limits” section in the Monitor would be very much appreciated here so we can understand what is happening.
After the Update from DL9 to 10 the Maschine Autostart by Submission from 3dsMax doesen´t work anymore but Autostart with Fusion and other Software works fine.
The scripts from Morgan solved the Problem and all Maschines autostart by Submitting from 3Dsmax.