RabbitMQ 3.13.2 on Erlang 26.2.3 logs an exception "timeout,{gen_server,call,[os_mon_sysinfo,get_mem_info]" on Windows with CrowdStrike tool suite #12293
-
Describe the bugRabbitMQ 3.13.2 with Erlang 26.2.3 is terminating with RabbitMQ log
Erlang coredump log
Reproduction steps
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 8 replies
-
Please answer the following questions:
|
Beta Was this translation helpful? Give feedback.
-
This is a duplicate of #11358, even the patch version is exactly the same. RabbitMQ does not "crash", it is the runtime memory monitor that runs into an exception. So the effects of this should be one (obviously important but still) metric unavailable. |
Beta Was this translation helpful? Give feedback.
-
@sharad578 please upgrade to |
Beta Was this translation helpful? Give feedback.
-
From another discussion on exactly the same topic.
The exception is entirely harmless. You can "disable" it by telling the node to use an absolute value instead: # rabbitmq.conf or a conf.d file such as conf.d/total_memory_override.conf
total_memory_available_override_value = 4GB Then the node won't try to infer that value. This is a rarely used feature that was added as a last resort measure for environment when a node cannot compute how much memory it has because years ago, Erlang's memory allocators were not cgroups-aware. |
Beta Was this translation helpful? Give feedback.
From another discussion on exactly the same topic.
os_mon_sysinfo:get_mem_info/1
is the monitor of available memory used on Windows. Most likely the node is prevented from fetching relevant information from the OS due to security policies or anti-virus software of sorts.The exception is entirely harmless.
You can "disable" it by telling the node to use an absolute value instead:
Then the node won't try to infer that value. This is a rarely used feature that was added as a last resort measure for environment when a node cannot compute how much memory it has because years …