# SIGKILL from Gurobi.jl?

**URL:** https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099
**Category:** Optimization (Mathematical)
**Tags:** jump
**Created:** [April 23, 2020, 6:21pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099 "2020-04-23T18:21:27Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![mlhetland](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mlhetland/32/283_2.png) [@mlhetland](https://discourse.julialang.org/u/mlhetland)
#### Post date: [April 23, 2020, 6:21pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099/1 "2020-04-23T18:21:27Z")

</div>

One of my JuMP models seem to be too much for Gurobi/Gurobi.jl – after a while, it kills Julia with SIGKILL. Other models of similar structure work just fine; I suspect the reason is that they are smaller, and that I’m running out of memory with the problematic one … is that documented behavior? Does anyone have experience with this?

---

<div class="post-metadata">

### Author: ![mlhetland](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mlhetland/32/283_2.png) [@mlhetland](https://discourse.julialang.org/u/mlhetland)
#### Post date: [April 23, 2020, 6:56pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099/2 "2020-04-23T18:56:29Z")

</div>

It does indeed seem like that may be it – and that setting `NodefileStart` could possibly help. I guess I’ll try that.

---

<div class="post-metadata">

### Author: ![leethargo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/leethargo/32/6004_2.png) [@leethargo](https://discourse.julialang.org/u/leethargo)
#### Post date: [April 23, 2020, 7:54pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099/3 "2020-04-23T19:54:41Z")

</div>

It could be your operating system killing the process, not the Gurobi solver.

---

<div class="post-metadata">

### Author: ![mlhetland](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mlhetland/32/283_2.png) [@mlhetland](https://discourse.julialang.org/u/mlhetland)
#### Post date: [April 23, 2020, 7:55pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099/4 "2020-04-23T19:55:24Z")

</div>

Yeah, that’s my conclusion, too. Just confused myself initially. 🙂

---

<div class="post-metadata">

### Author: ![odow](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/odow/32/28685_2.png) [@odow](https://discourse.julialang.org/u/odow)
#### Post date: [April 23, 2020, 8:13pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099/5 "2020-04-23T20:13:23Z")

</div>

You should look at the `gurobi.log` file for clues. This doesn’t seem like an issue with Julia and JuMP. You could contact Gurobi directly for support.

---

<div class="post-metadata">

### Author: ![mlhetland](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mlhetland/32/283_2.png) [@mlhetland](https://discourse.julialang.org/u/mlhetland)
#### Post date: [April 23, 2020, 8:26pm UTC](https://discourse.julialang.org/t/sigkill-from-gurobi-jl/38099/6 "2020-04-23T20:26:30Z")

</div>

Yeah. [According to Ed Rothberg](https://groups.google.com/d/msg/gurobi/gOmiJzLlaRw/aaoLwZiu_UQJ) (from Gurobi), a SIGKILL from the OS does indeed generally mean that Gurobi has run out of memory.
