Is there a way to make runfeko wait until licenses become available

Hi,
We are using several Altair products and are regularly in a situation where runfeko won't start because all licenses are occupied. In this situation runfeko aborts its attempts and I have to manually restart to retry the license check until a license becomes available.
The biggest problem occurs with optfeko and adaptfeko where the program seems to returns and requires the license after each runfeko run and then if the license became occupied it aborts the whole optfeko/adaptfeko run. I assume amrfeko would have the same problem if I tried it.
For normal runs we have a wrapper script that waits for an available licence and then runs runfeko, but it also has problems with race conditions and it does not solve the problems with optfeko and adaptfeko.
I am hoping that there is some kind of execution flag that i can use, or some other solution.
Thanks
Answers
-
Hi Tobias,
I will ask the development if they have any suggestions for a solution. At the same time, you could perhaps also create a support ticket ("License / Installation"). Perhaps there is a solution via the License Server.
Best regards,
Torben0 -
Hi Tobias,
You can set the
ALM_QUEUE_TIMEOUT
environment variable to wait a fixed time before aborting.
ALM_QUEUE_TIMEOUT=<positive integer would enable queuing and set the timeout in seconds>
Best regards,
Torben0 -
It does not seem to work.
0 -
Strange, it should work. Could you try defining the environment variable system-wide?
0 -
Or another guess, add it to the machine where the License Server is running? Does this work?
0 -
I won't be able to check those until next week due to the way permissions are setup on our system.
0 -
Most likely it's sufficient to define it on your machine (not in Feko). Please report when you can test.
0 -
Defining the variable in Windows's User Environment Variables on the local machine does not work.
0 -
Did you also try to add the environment to the machine where the License Server is running?
0 -
We just tried this, and it also did not work.
0 -
Hi Tobias,
You will probably be asked this in your support case, but I will also comment here for the community: Have you already tried to define the environment variable ALM_QUEUE_TIMEOUT as a system variable (not user variable!) on the machine where the simulation is running?
Best regards,
Torben0 -
Hello Torben,
We have also tested setting the variable as a system variable. We are testing on a windows machine where feko is running locally.
0 -
Ok, then let's wait for Sotirios to comment in your support case.
0