Page 1 of 1

License in use status after the crash of Houdini

Posted: Fri Oct 29, 2021 4:17 pm
by sick
Houdini crashes with an active octane license.
I start Houdini again and see a message that the license is taken. Obviously by the process that crashed.
I can't log out of my Octane account because in the new Houdini session Octane says I'm not logged in. It's some kind of vicious circle.
The only thing that helps is unlocking from account/subscriptions.php or writing to support. But it is very frustrating.

Re: License in use status after the crash of Houdini

Posted: Fri Oct 29, 2021 5:11 pm
by juanjgon
Hmm, even after a crash the license should be released as soon as you try to render something in the same computer using the same user, and of course, it should be available for this same system/user. Have you tried to restart?

You also have a command that you can execute from hython to release the license from the terminal or from any script:

Code: Select all

hou.hscript("Octane_releaseLicense")

Thanks,
-Juanjo

Re: License in use status after the crash of Houdini

Posted: Fri Oct 29, 2021 5:23 pm
by sick
I tried rebooting it didn't help.
Now I did an unlock on the subscription page. And I don't have any more attempts left :? .
I will try this python command next time.
Thank you.

Re: License in use status after the crash of Houdini

Posted: Fri Oct 29, 2021 5:26 pm
by juanjgon
This is something really weird. You should always be able to use the license in the same machine/user that it is locked unless there is a hardware change, system update or something like that.

Thanks,
-Juanjo

Re: License in use status after the crash of Houdini

Posted: Fri Oct 29, 2021 6:00 pm
by sick
Maybe there is some log file that I can send to investigate the cause?

Re: License in use status after the crash of Houdini

Posted: Tue Nov 02, 2021 9:17 am
by juanjgon
If you have this problem again and you are sure that you can't enable the license in a system/user that has it already enabled, it is better to contact the support team at [email protected] to let the licensing team know about this problem. They have access to your licenses log, so the probable could help you.

Thanks,
-Juanjo