AWS Thinkbox Discussion Forums

Foundry License error on a Single machine pipeline (Centos7, Katana / Redshift)

SOLUTION

Turns out it was a license issue with Foundry. I have the Production Collective and it doesn’t include a headless Katana so Deadline can’t pick it up. The Collective does comes with the headless Nuke so my assumption that Katana would work was wrong.

###############

Hi there,

I’m new to deadline so I’m just following rendering instructions here. I’m all the way to the last set apparently but now I’m bumping into a License Error when launching a Katana / RedShift render.

Here’s what it print out:

2019-12-19 21:42:14: 0: STDOUT: [INFO LicenseCheck]: Render License failed.
2019-12-19 21:42:14: 0: STDOUT: [INFO LicenseCheck]: FOUNDRY LICENSE ERROR REPORT
2019-12-19 21:42:14: 0: STDOUT: ----------------------------
2019-12-19 21:42:14: 0: STDOUT: Timestamp: Thu Dec 19 21:42:14 2019
2019-12-19 21:42:14: 0: STDOUT: License(s) Requested:
2019-12-19 21:42:14: 0: STDOUT: katana 2019.1121 render only with options all
2019-12-19 21:42:14: 0: STDOUT: Extended Info: None Provided
2019-12-19 21:42:14: 0: STDOUT: Host : vfx.machine
2019-12-19 21:42:14: 0: STDOUT: System ID(s) : 7085c2bdc0ff , 7085c2bd8082 , 48f17f06cceb , 525400a42fe3 , 525400a42fe3
2019-12-19 21:42:14: 0: STDOUT: RLM Environment Info: /root/FoundryLicensing/7085c2bdc0ff:/usr/local/foundry/RLM:/root/FoundryLicensing
2019-12-19 21:42:14: 0: STDOUT: Reason for failure: Failed to understand response from server.
2019-12-19 21:42:14: 0: STDOUT: RLM LICENSE DIAGNOSTICS
2019-12-19 21:42:14: 0: STDOUT: ---------------------------
2019-12-19 21:42:14: 0: STDOUT: katana_r : Communications error with license server (-17)
2019-12-19 21:42:14: 0: STDOUT: Connection refused at server (-111)
2019-12-19 21:42:14: 0: STDOUT: License Path:
2019-12-19 21:42:14: 0: STDOUT: /root/FoundryLicensing/7085c2bdc0ff:/usr/local/foundry/RLM:/root/FoundryLicensing:/usr/local/foundry/RLM/
2019-12-19 21:42:14: 0: STDOUT: [ERROR MAIN]: No ‘Render’ license available.

My licenses are node locked but they are all working and deadline (including data base) are all on the same machine. I tried setting render limits to see if that would fix the license problem but that didn’t change anything.

As a background on what I’m doing. I’m building my own little pipeline based on Centos7, Maya, Katana, Nuke and adding Deadline will help me avoid problems I had on my last freelance where I would render a frame range from Maya overnight and would wake up to a crash in the morning with only 3 frames rendered. I’m hoping Deadline will at least help me keep rendering and logging errors going with the added benefit of using AWS if I need a quicker render.

Something tells me it’s the node locked licenses. Any ideas?

Thank you

Do you have a Katana Render license or just Katana?

Nuke has an option to use a full interactive license instead of a render license but I don’t see that option in the Katana plug-in
https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User%20Manual/manual/app-katana.html

Not sure if you can manually adjust the plug-in to use the full license (I’m not a katana user)

What does your license server say you have?

You might also find more information in the license server’s logs (https://docs.thinkboxsoftware.com/products/licensing/1.0/Licensing%20Guide/finderror.html). We don’t have any notes about how licensing with Katana works outside of whatever is on the docs page.

Hey Anthony! Thank’s for the reply!

Maybe I’ll have to check with Foundry, I see that nuke has this interactive variation on my license server but Katana is just Katana in there. I’ll check up on the link you gave me and I’ll reach out to them. Thank you again!

Awesome! Thanks a lot Justin!

Privacy | Site terms | Cookie preferences