I posted this in the wrong thread an was asked to redirect to this topic, so this is a partial repost. Sorry for that.
We are experiencing license authentication errors when 2 octane instances start more or less at the same time.
We use a proprietary render dispatcher that is build in python to run standalone, but in the end it just starts octane on the specified slave PC's with the following command parameters "--stop-after-script" and "--script" pointing to an on the fly generated lua script ( table with shot and renderJob info and a call to our lua pipeline batchRender script ) to start the rendering process inside octane.
We only run 2 slave units on a render PC when the loading times are substantially higher than the per frame render times. And even then the chance that 2 octane jobs start simultaneously is small, but is has happened more than once that one instance stopped due to this error massage and since our batch job doesn't finish until octane exists, we had 1 of the 2 slaves idle for a whole weekend, which is not desirable when chased by deadlines
This problem is not specific to our render dispatcher, as the problem arises as well when you start two octane instances at the same time ( by clicking the app icon quickly after each other
)
This even happens when octane has run just before and thus the PC has been authenticated only minutes before.
I attached a screengrab of our renderDispatcher ( just for fun ) and one of the error message.
Is this something that is circumvent-able, by means of automated retry timer or is it on the bug-fix-list?
Cheers
Jean-Paul Tossings
polderRenderDispatcher.jpg
errorMessage.PNG
You do not have the required permissions to view the files attached to this post.
