Solver returning non-zero return code (-1)

Answered

Katie Jordan

• September 05, 2023 16:00

Hi,

I'm getting the following error when running my model. It's worked fine for months, so I'm not sure what's causing this change. The full error message is: 

ERROR: Solver (gurobi) returned non-zero return code (-1)

ERROR: Solver log: Set parameter Username Academic license - for non-

    commercial use only - expires 2024-09-04 Read LP format model from file

    /Users2/khjordan/temoa/data_files/debug_logs/lp_files/tmpbi3jw8b7.pyomo.lp

    Reading time = 15.19 seconds x2097419: 2144809 rows, 2097419 columns,

    9752257 nonzeros Set parameter QCPDual to value 1 Gurobi Optimizer version

    9.5.2 build v9.5.2rc0 (linux64) Thread count: 32 physical cores, 64

    logical processors, using up to 32 threads Optimize a model with 2144809

    rows, 2097419 columns and 9752257 nonzeros Model fingerprint: 0x6105eb42

    Coefficient statistics:

      Matrix range     [8e-07, 2e+03] Objective range  [6e-02, 3e+04] Bounds

      range     [0e+00, 0e+00] RHS range        [2e-05, 2e+08]




    Concurrent LP optimizer: primal simplex, dual simplex, and barrier Showing

    barrier log only...




    Presolve removed 900419 rows and 828802 columns (presolve time = 5s) ...

    Presolve removed 1194686 rows and 1070281 columns (presolve time = 12s)

    ... Presolve removed 1229832 rows and 1093824 columns (presolve time =

    17s) ... Presolve removed 1297883 rows and 1107290 columns (presolve time

    = 23s) ... Presolve removed 1321548 rows and 1107308 columns Presolve

    time: 25.85s Presolved: 823261 rows, 1013776 columns, 5033477 nonzeros




    Elapsed ordering time = 5s Elapsed ordering time = 10s Elapsed ordering

    time = 15s Elapsed ordering time = 20s Elapsed ordering time = 25s Elapsed

    ordering time = 39s Elapsed ordering time = 40s Elapsed ordering time =

    45s Elapsed ordering time = 50s Elapsed ordering time = 55s Elapsed

    ordering time = 60s Elapsed ordering time = 65s

Exception found in solve_temoa_instance

Solver (gurobi) did not exit normallySolver (gurobi) did not exit normally

Exiting Temoa ...

Traceback (most recent call last):

  File "temoa_model/temoa_run.py", line 275, in createAndSolve

    for k in self.solveWithoutMGA():

  File "temoa_model/temoa_run.py", line 247, in solveWithoutMGA

    for k in temoaInstance1.solve_temoa_instance():

  File "temoa_model/temoa_run.py", line 433, in solve_temoa_instance

    raise model_exc

  File "temoa_model/temoa_run.py", line 399, in solve_temoa_instance

    symbolic_solver_labels=self.options.keepPyomoLP )

  File "/Users2/khjordan/miniconda3/envs/temoa-py3/lib/python3.7/site-packages/pyomo/opt/base/solvers.py", line 626, in solve

    "Solver (%s) did not exit normally" % self.name)

pyutilib.common._exceptions.ApplicationError: Solver (gurobi) did not exit normally

Any advice is appreciated! 

Related to

• Memory
• Pyomo

0

• 

  David Torres Sanchez

  Gurobi Staff

  • September 05, 2023 16:15

  Hi Katie,

  That is interesting, could it be that the machine runs out of memory?
  Do you mind profiling/checking the resources while running this?

  Cheers, 
  David

  0
• 

  Katie Jordan

  • September 05, 2023 18:49

  

  

  

  Hi David, 

  It did appear to be a memory issue- I was able to work with the system administrators to fix the issue.

  Thanks!
  Katie

  0

Please sign in to leave a comment.