SYMPTOMS
When attempting to render from a render farm in Nuke 14.0, you may encounter the following error:
Failed to lock during LicenseInterprocessLockTryGuard()
You may also experience some slow performance issues in Nuke 14.0.
CAUSE
With the introduction of Login licensing in Nuke 14.0, when you launch Nuke, it writes a temporary lock file to this location:
Windows:
C:\Users\<USERNAME>\AppData\Local\Foundry\Tokens
OSX:
/Users/<USERNAME>/Library/Application Support/Foundry/Tokens
Linux:
$HOME/.local/share/Foundry/Tokens
The location in which the lock file is written to should be unique per machine. If multiple nodes share the same network/shared directory for that resource then that may result in the timeouts.
RESOLUTION
If multiple render nodes share the same network or shared directory, we suggest changing the location where the lock file writes to using the environment variable environment variable:FOUNDRY_CLOUDLIC_WRITE_DIR
This environment variable is available in Nuke 14.
For example: FOUNDRY_CLOUDLIC_WRITE_DIR=/Users/<USERNAME>/Desktop/Tokens
From Nuke 14.0v6 onwards, it is possible to completely disable the Login code using the environment variable:FOUNDRY_DISABLE_LICENSE_TYPE=tend
Further information on setting environment variables can be found in the following article: Q100015: How To Set Environment Variables
If you are running a floating license server, we would also recommend upgrading your RLM build to RLM 12. RLM 12 is available in versions 8 and above of the Foundry Licensing Utility.
For Mac & Linux, we would recommend using FLU 9 due to a known server tools installation bug found in FLU 8.1.6 on these operating systems. Further reference on this bug can be found in this article: Q100630: Unable to install license server via FLU 8.1.6 on Mac/Linux
If you are not using the Foundry Licensing Utility, you can manually upgrade your RLM build by running the steps in this article: Q100260: How to manually upgrade the version of RLM in the Foundry Licensing Tools
FURTHER HELP
If you are still experiencing difficulties please create a support ticket to let us know the exact issue encountered and the troubleshooting steps that have been taken.
For more information on how to open a support request, please refer to this article: Q100064: How to raise a support ticket
We're sorry to hear that
Please tell us why