Windows: an exception in os_mon_sysinfo:get_mem_info is logged periodically, how can I avoid it?

[ssm6498]

Is your feature request related to a problem? Please describe.

This is inline with issue #12293
rabbitmq has been upgraded to 3.13.7 core requirement is meeting its already 4 core setup,
and in the rabbitmq logs, we are still seeing issue with [os_mon_sysinfo,get_mem_info]

please find gathered logs

rabbitmq_crash1.txt

Can anyone please provide provision to disable this check
([{memsup,get_memory_usage,1,[{file,"memsup.erl"},{line,616}]}, or [os_mon_sysinfo,get_mem_info]),

like rabbitmqctl.bat deactivate_free_disk_space_monitoring

Describe the solution you'd like

Resolving the mem check issue, some way to disable the memory check or get rid of the crashes

Describe alternatives you've considered

No response

Additional context

No response

[michaelklishin]

RabbitMQ 3.13.x is out of community support.

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:

# 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.