We've started seeing Nuke license failures, specifically relating to the "Keylight" node. This shouldn't require it's own license, the Nuke license should suffice. I've been going back and forth with Foundry support on this, and apparently Keylight did formerly require its own license, but no longer does, and that functionality has "pretty much" been migrated forward. They're claiming the failure is due to the license server being "slow," but I have fifty bazillion successful license transactions a minute from other vendors that says otherwise.
FLEXnet Licensing error:-16,287 For further information, refer to the FLEXnet Licensing documentation, available at "www.acresso.com".
I've also had "-17,13 System Error: 11 Resource temporarily unavailable" reported.
I managed to dig up this;
-16 Cannot read data from license server system. -17 Cannot write data to license server system.
I've recently had to increase the number of file descriptors on our license server due to the Foundry flexlm server running out. Also, Nuke appears to be keeping lots of sockets open to the license server on some clients for some reason, probably something that could be correlated by one of the Heavy Nuke Cats if I could justify grabbing one. I get no indication of a problem in the logs on the license server. Anybody else seen this? Foundry support wants me to point the clients at a file-based license for the Keylight node to bypass our license server, but I'm having a lot of trouble pointing the finger at our "pokey" license server for this.
Also, what did I do in a previous life to end up responsible for software licensing in this one? To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe