OTOY Forums

What you see is normal. If your machine get's powered off and upon restart the settings are different:

1) Octane won't get a chance to deactivate the licenses in use.
2) The machine will look like a different one when it restarts.

This leads to the licensing system that the license is still in use on the first machine as it hasn't been released, which does not even exist anymore.

I'd recommend to make sure you don't use offline licensing and that Octane is gracefully closed when your machines are switched off, this should release the license and make it available to the next machine.

I'll ask to reset your counter while you can solve this issue.

I hope that helps.

Is there any possible way to release the Octane license via a Linux command? I ask this because then maybe I can setup a script to run anytime the machine is going to be powered off automatically.

I am just trying to think of a solution to fix this issue in my situation where I am running the Linux slaves from a network attached OS install image; and these Linux slaves can be randomly powered off from certain factors occurring.

Mojave,

Also, thank you for asking for my counter to be reset while I figure out a workaround solution.

nrygpu wrote:Is there any possible way to release the Octane license via a Linux command? I ask this because then maybe I can setup a script to run anytime the machine is going to be powered off automatically.

You may use regular Linux commands (kill, pkill, killall) to send a signal to the Octane daemon process running on your node and use wait to make sure the process has gracefully finished upon receiving the signal.

The daemon will stop the slave process if it is currently running, which will release the license automatically (make sure offline licensing is not used on your nodes or otherwise they won't), just make sure that at this point, there's still a valid Internet connection available so Octane can reach the server to free the license.