AWS Thinkbox Discussion Forums

Krakatoa2.1.4 Partitioning NFU?

Deprecated Deadline 6 Bug Reports
#1

I can’t seem to get deadline 6.0.49200 to run a simple KrakatoaMX partition job. I tried on a local slave and a remote slave, it say it cannot open max render on both.

I can connect to Deadline, submit the job in any mode, slaves just error out.

Any hints?

win7 x64 SP1
Max2013 x64 PU6
Krakatoa 2.1.4.48313
Deadline 6.0.49200 License-Free-Mode

#2 
2012/11/30 17:48:47 ERR: No such feature exists. Feature:       krakatoa-render License path:  @192.168.19.192; FLEXnet Licensing error:-5,412 For further information, refer to the FLEXnet Licensing documentation, available at "www.flexerasoftware.com".

Ooops!

We changed the name of the “krakatoa-max-render” license to “krakatoa-render” to make it universal for KMX, KMY and KSR. This happened last year.
Your file still has “krakatoa-max-render”. Will update and email you the new one.

Sorry!

EDIT: Check your 4rand email…

#3

Thanks for that! I just updated to deadline6 and Krakatoa 2.1.4. Oddly enough or not, I really haven’t had any issues until now.

Still isn’t working :frowning:
JOB Error 1:

Error

Exception during render: An error occurred in RenderTasks(): 3dsmax exited unexpectedly before being told to render a frame
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage)
JOB Error 2:

Error

The process cannot access the file ‘C:\Users\XXXXXX\AppData\Local\Temp\lightning_startup.ms’ because it is being used by another process.

I get two Job errors and a slave error (well it is the same as job but), I attached the three different logs.
jrand_localSlave_logs.rar (6.85 KB)

#4

I am pretty sure I am doing everything “right”, no different than ever before, so here is a little screen cap of what I am doing. It appears that maybe Krakatoa is checking for deadline? It isn’t returning pool or group data so I am a bit confused. You will see what I mean. I have exceptions but I turned off all my firewalls just to rule that out.

Note: I checked and the temp file is there in the local folder on the slave machine.

#5

Ok, now it is officially a Deadline problem. Will have to pass it on to the Deadline support people as I don’t even run DL 6 at home.

#6

Thanks for checking

I had to update to get max2013 support anyway (I was running 5.1) so I figured I would try ver6.

#7

Did you reinstall the SMTD submitter for Deadline? If it’s still the older version, I’m wondering if maybe it’s pulling pool/group info from the wrong location.

As for those render errors, I’m a bit stumped. If you can try submitting again after updating SMTD, we can see if things improve or not.

Thanks!

  • Ryan
#8

Hi Ryan,

The Pool and Group Data are jnow showing up, I rebooted ?!

The SMTD in max I am using; the macro is label Deadline-SubmitMaxToDealine6.mcr

So does submitting a Save to Sequence with Partitioning from the max2013 Krakatoa UI work for you?

What I just ran through:

*I just submitted a quick test job in max2011 through Krakatoa 2.1.4 and deadline accepted the job and started doing its thing BUT I open the slave (this is a local slave) and it is stalled on “0: INFO: +Phase Eccentricity set to 0”
*Killed and restart the slave
*Back to 2013 I Submit a job through the Actual SMTB instead of the Krakatoa UI, it is now caching frames. It works! but not what I am trying to do. FYI - Sanity Check was doing its job telling me I did not have a filename in the render dialog (ie rendOutputFilename = “”) even thought the Krakatoa UI save paths were fully populated. I don’t recall seeing this before.

Conclusion - Something is wrong in/with the Krakatoa UI SMTD

  1. I can submit single partitions via SMTD interface;
    *max2013 with the 6.0 SMTD macroscript == OK :smiley:
  2. Krakatoa UI Partioning Submission: (I am trying to run the default of 10 partitions)
    *max2011 submission to Partition through Krakatoa cause the two Errors I listed. == NFU :cry:
    *max2013 submission to Partition through Krakatoa cause the two Errors I listed. == NFU :cry:
#9

I will try to run this on my laptop which has Max 2013 and Deadline 6 and see what is going on.
There were changes made to SMTD for 6 which I wasn’t involved with (location of paths is different)
It is possible that Krakatoa is using the wrong stuff because it does not know about these changes to 6…

Btw, I have no idea what NFU means, and I don’t like what urban dictionary thinks about it :wink:

#10

Thanks Bobo

LOL I will have to check to see what they say :open_mouth: The standard definition is “Non-Functional Unit”

EDIT: Sadly that is definitely the typical prepubescents uneducated definition :unamused:

#11

I launched Max 2013 (15.0 PU2) on my laptop and submitted a Partitioning job using Krakatoa v2.1.4.
Running Deadline 6.0.0.48930.
The scene loaded correctly and saved 10 particles as expected without any glitches.

So now we will have to figure out what is wrong with your setup, because it seems to be ok here.

#12

Well I am actually glad to hear that it works!

My setup is pretty much default, nothing special (maybe something needs to be?), with exceptions to my firewall and a networked mapped drive shortcut that I render/cache too. It is not however added to deadline in anyway I just use it as my save/cache path.

#13

Can you try a simple test with a default PFlow partitioned to the C:\Temp of your workstation? I tested on a laptop which has node locked licenses of all our products and was doing both the submission and the rendering, with Deadline 6 Beta installed on it and no network connections to anywhere.

#14

Still same errors.

Local slave, save path “c:/temp/particles_.prt”

Wait for it wait for it…

OK I found something! I was running 2 concurrent tasks BUT I thought I should be able to run as many as I want per node! I even have an extra render node so even two concurrent tasks should work, right?

#15

Using the latest builds of Krakatoa (2.1.3, 2.1.4, 2.1.5), it should require just a single krakatoa-render license for all concurrent tasks.
But we already fixed the licensing issue by giving you the one krakatoa-render license and the error message changed.
So please switch off the concurrent tasks and try partitioning ONE at a time on your machine. Do you get the same error?
(Probably not. Because the error was complaining about a script file being locked by another process. So it could be a bug in DL 6 concurrent tasks handling or something…)

#16

It works as expected when only running 1 concurrent task!

#17

Ok, this confirms my suspicion that there is a problem with Concurrent Tasks in DL6.
Will log it as a bug.

#18

Thanks for your help.

#19

I can’t reproduce the concurrent task problem with jobs submitted from SMTD. I also tested a concurrent Nuke job and that worked too. We didn’t change how concurrent task rendering worked in D6, so I’m not sure why it’s breaking when rendering Krakatoa partitioning jobs…

Bobo, did you try concurrent tasks with your test with D6? If not, can you give it a try to see if you can reproduce?

#20

Yes, I did and could reproduce it by submitting from the Partitioning rollout of Krakatoa.
Logs sent.

Privacy | Site terms | Cookie preferences