Port server exited with status 134


#1

Has anyone has any knowledge regarding this error?

Port server ns_server on node ‘babysitter_of_ns_1@127.0.0.1’ exited with status 134. Restarting. Messages: [os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed

Crash dump was written to: erl_crash.dump.1424002060.1000.ns_server
eheap_alloc: Cannot allocate 123210440 bytes of memory (of type “heap”)

We are running on r3.large aws ec2 servers (x4) with couchbase 3 and ubuntu os.


#2

An exit with status 134 indicates that it’s a SIGABRT, so that erlang process must have exited. The best thing to do would be to get a cbcollect_info and file an issue so we can have a look. That should capture any core files or other info.

Frequently, a SIGABRT can be due to a problem with handling memory, but it can also happen if the program logic triggers it for another reason or from an assertion. To know what the state was at the time, we’d need more info.

Was this on a listed supported version of Ubuntu? What was happening when you saw this?


#3

Thanks @ingenthr.
a. I can’t run cbcollect_info as it fails the servers, not sure why. They just lose connection and fail.
b. It seems that there was indeed problem with the memory although I’m not sure what. I’ve changed the servers to r3.xlarge (and by that had multiplied the available RAM) and the problem solved.
This problem started after a failed attempt to add nodes and rebalance. The nodes failed and since then the beam.smp and memcache processes started to consume a lot of memory.
c. We are running Ubuntu 14.04.

What is the beam.smp process?
Should we preserve an amount of memory for it? How much?

Thanks again.