RabbitMQ Crash on docker

[Arash Mohammadi]

Hello ,

im using RABBITMQ VERSION=3.11.7 with docker container

in first hours i have no problem with rabbitmq and its working fine but after few days it start crashing with following message :

Slogan: sys_alloc: Cannot allocate 98 bytes of memory (of type "environment").

and this is my erl_crash.dumps

any help appreciated :)

[Michal Kuratczyk]

Hi,

Sounds like you're running out of memory:

https://www.erlang.org/doc/apps/erts/crash_dump.html#reasons-for-crash-dumps--slogan-

You probably need to assign more memory to your container. You can use `rabbitmq-diagnostics memory_breakdown` to see what uses most of the memory.

Best,

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/584fbcf4-f996-45ce-bbdc-50b09d4aeaean%40googlegroups.com.

--

Michał

RabbitMQ team

[Arash Mohammadi]

eheap_alloc: Cannot allocate 600904 bytes of memory (of type "heap").
and again

[Arash Mohammadi]

hi michal thank you for answering my question :)
i dont have any limits over rabbitmq docker container and im sure ihave enough memory because my server have 128GB Ram
this is what i have from rabbitmq-diagnostics
Reporting memory breakdown on node rabbit@cc6dd539ebf0...
reserved_unallocated: 0.3404 gb (73.2%)
code: 0.035 gb (7.54%)
other_system: 0.03 gb (6.46%)
other_proc: 0.0204 gb (4.39%)
allocated_unused: 0.0201 gb (4.32%)
binary: 0.0089 gb (1.91%)
queue_procs: 0.0035 gb (0.76%)
metrics: 0.0033 gb (0.7%)
atom: 0.0014 gb (0.31%)
connection_other: 0.0004 gb (0.1%)
other_ets: 0.0004 gb (0.08%)
plugins: 0.0003 gb (0.07%)
connection_readers: 0.0003 gb (0.06%)
mnesia: 0.0003 gb (0.06%)
connection_channels: 0.0 gb (0.01%)
quorum_ets: 0.0 gb (0.01%)
msg_index: 0.0 gb (0.01%)
connection_writers: 0.0 gb (0.0%)
quorum_queue_procs: 0.0 gb (0.0%)
quorum_queue_dlx_procs: 0.0 gb (0.0%)
stream_queue_procs: 0.0 gb (0.0%)
stream_queue_replica_reader_procs: 0.0 gb (0.0%)
queue_slave_procs: 0.0 gb (0.0%)
stream_queue_coordinator_procs: 0.0 gb (0.0%)
mgmt_db: 0.0 gb (0.0%)

On Wednesday, January 18, 2023 at 9:13:16 PM UTC+3:30 mkura...@gmail.com wrote:

[Arash Mohammadi]

docker stats --no-stream
-> cc6dd539ebf0   rabbitmq-broker   47.70%    178MiB / 125.7GiB     0.14%     8MB / 321kB       0B / 26.3MB      86

[Michal Kuratczyk]

Hi,

I'm fairly sure you must have limits. Either way - as you can see RabbitMQ uses hardly any memory so there is no RabbitMQ problem.

The errors you see are clean: Erlang virtual machine can't allocate memory. Whether that's due to user limits, Docker settings or something else - I can't tell you.

Best,

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/441cf872-c262-4131-980a-022dfd7f748cn%40googlegroups.com.

--

Michał

RabbitMQ team

[Arash Mohammadi]

and finally this is what i have

[Arash Mohammadi]

this photo have better quality

[Michal Kuratczyk]

1. This issue has nothing to do with the previous one. Start a new thread for a new issue.

2. The error message says what happens - client terminates the connection uncleanly. The stacktrace is harmless and basically says the same thing.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/a1175802-74b7-4c70-a923-363a7b73951bn%40googlegroups.com.

--

Michał

RabbitMQ team