Skip to main content

gurobipy.GurobiError: Job was not found

Answered

Comments

2 comments

  • Official comment
    Simranjit Kaur
    • Gurobi Staff
    This post is more than three years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum, or try Gurobot, our chatbot interface offering instant, expert-level support.
  • Jaromił Najman
    • Gurobi Staff

    Hi Markus,

    This is a network error that usually indicates a problem connecting to the Compute Server (CS). Is it possible there was an intermittent network issue that prevented the client machine from connecting to the Compute Server? That said, this error message can also occur when the CS node runs out of memory.

    Did you restart the Compute Server? This error can also be thrown if you restart the CS and your model does not clean up its environment properly, then the model tries to continue with the same environment. In case something goes wrong, you should always dispose of the model and the underlying environment. If you do not specify a dedicated environment, you have to dispose of the default Python environment in case something goes wrong.

    Best regards,
    Jaromił

    1

Post is closed for comments.