Bug 1641754 - rabbitmq-server: eheap_alloc: Cannot allocate 3280272216 bytes of memory (of type "old_heap")
Summary: rabbitmq-server: eheap_alloc: Cannot allocate 3280272216 bytes of memory (of ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 10.0 (Newton)
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Peter Lemenkov
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks: 1381612
TreeView+ depends on / blocked
 
Reported: 2018-10-22 15:47 UTC by Mikel Olasagasti
Modified: 2020-09-20 12:37 UTC (History)
5 users (show)

Fixed In Version: rabbitmq-server-3.6.3-11.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-16 17:09:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rabbitmq rabbitmq-server issues 1302 0 None closed Stable GM memory usage during constant redelivery 2020-09-02 19:28:36 UTC
Red Hat Knowledge Base (Solution) 3662331 0 None None None 2018-10-22 15:50:19 UTC
Red Hat Product Errata RHBA-2019:0075 0 None None None 2019-01-16 17:09:28 UTC

Description Mikel Olasagasti 2018-10-22 15:47:42 UTC 
Description of problem:

rabbitmq-server crhased with the following error message:

Oct 21 14:47:16 ctrl01 rabbitmq-server: eheap_alloc: Cannot allocate 3280272216 bytes of memory (of type "old_heap").
Oct 21 14:49:14 ctrl01 rabbitmq-server: Crash dump is being written to: erl_crash.dump...done
Oct 21 14:49:16 ctrl01 systemd: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 21 14:49:18 ctrl01 rabbitmqctl: Stopping and halting node rabbit@ctrl01 ...
Oct 21 14:49:18 ctrl01 rabbitmqctl: Error: unable to connect to node rabbit@ctrl01: nodedown
Oct 21 14:49:18 ctrl01 rabbitmqctl: DIAGNOSTICS
Oct 21 14:49:18 ctrl01 rabbitmqctl: ===========
Oct 21 14:49:18 ctrl01 rabbitmqctl: attempted to contact: [rabbit@ctrl01]
Oct 21 14:49:18 ctrl01 rabbitmqctl: rabbit@ctrl01:
Oct 21 14:49:18 ctrl01 rabbitmqctl: * connected to epmd (port 4369) on ctrl01
Oct 21 14:49:18 ctrl01 rabbitmqctl: * epmd reports: node 'rabbit' not running at all
Oct 21 14:49:18 ctrl01 rabbitmqctl: no other nodes on ctrl01
Oct 21 14:49:18 ctrl01 rabbitmqctl: * suggestion: start the node
Oct 21 14:49:18 ctrl01 rabbitmqctl: current node details:
Oct 21 14:49:18 ctrl01 rabbitmqctl: - node name: 'rabbitmq-cli-65@ctrl01'
Oct 21 14:49:18 ctrl01 rabbitmqctl: - home dir: /var/lib/rabbitmq
Oct 21 14:49:18 ctrl01 rabbitmqctl: - cookie hash: BxO2AVpt07xu8IfZkZu7ew==
Oct 21 14:49:18 ctrl01 systemd: Unit rabbitmq-server.service entered failed state.
Oct 21 14:49:18 ctrl01 systemd: rabbitmq-server.service failed.


Version-Release number of selected component (if applicable):

rabbitmq-server-3.6.3-9.el7ost.noarch

How reproducible:

First time happening
Comment 4 Peter Lemenkov 2018-12-01 14:38:58 UTC 
(In reply to Mikel Olasagasti from comment #0)
> Description of problem:
> 
> rabbitmq-server crhased with the following error message:

Mikel, please advice the customer to upgrade to rabbitmq-server-3.6.3-11.el7ost which will be available in RHOS-10 repositories soon. This version should fix the issue.
Comment 11 errata-xmlrpc 2019-01-16 17:09:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0075
Note You need to log in before you can comment on or make changes to this bug.