It is the line marked “Slogan:” which gives the basic cause why the erlang system crashed. In this case you were trying to allocate more memory for process heaps but this was not allowed by the OS.

I usually remove all swap since it introduces huge unpredictablity in performance into the system. Plus I’ve seen some cases when swap causes problems with ssh. It’s safer to fail fast, in my opinion, at least on linux. I heard freebsd is a bit different in regards to swap (it’s possible to mark some processes which won’t go into swap or something like that).

“Swap or no swap for soft real-time elixir apps” might be an interesting discussion to have …

It looks like it’s just running out of memory… How much memory does the program use? How long does it take to crash? Can you open up observer on it and watch it to see if any specific process or binary heap or something keeps growing without shrinking?

EDIT: And for some reason it looks capped to 2gigs of ram?

Oooo, I think I see, you are allocating more ram than what’s available and you have no SWAP memory setup.

Either reduce the memory load of the system (again check your beam program and see what’s eating memory via :observer or so), and/or add swap. You should add swap anyway, I’d say no less than 8 gigs of swap for your system. You can add swap while the system is in use for note, instructions online.