Split Up "Error 10009: No Gurobi license, or license not started or set" into "No Gurobi License" and "License not started"
ユーザーの入力を待っています。
Dear Gurobi Team,
to help other users within out organization debugging license issues, we encounter Grb error 10009 from time to time. Sometimes the source of the error is that a Gurobi license has not been placed in a default search location or the GRB_LICENSE_PATH env variable path. In other cases communication issues with the Compute Server/Cloud are the source of the error.
In order for us (and anyone else of course!) to provide a better internal support, it would be helpful to be able to immediately distinguish between a “No Gurobi License” and a “License not started” case. This may well extend to “License not set”, but this is never the root cause in our experience.
Thanks in advance!
-
-
Gurobi Staff
Hi Christian, thank you for providing this feedback. I have some good news: in our most recent version, we now include a diagnostic tool (grbdiagnose) that could be helpful for you to debug this kind of issue. Instructions on its use can be found here: How do I use the Gurobi setup diagnostic tool?
I am a bit puzzled that you would receive a 10009 NO_LICENSE error code as a result of networking/communication issues with a compute server or cloud. I would expect 10022 NETWORK or 10028 CLOUD. If you believe you are experiencing a 10009 code as a result of a network issue, please open a support request with our team so that we can investigate further.
However, if you create an empty Gurobi environment object and do not start it, you could also get a 10009 error (because the environment has not been started with the license information). I will record a feature request internally, as I do understand your point that it may be possible to break these cases into distinct error logging messages. Thank you again for sharing this with us.
0 -
サインインしてコメントを残してください。
コメント
1件のコメント