Replies: 1 comment
-
|
It has been discussed many times before. On Windows, disk space monitoring occasionally fails for reasons we do not know. Anti-virus software and comparable security tools is a common source of obscure failure of such periodic operations. The metric is used by free disk space alarms. If you have evidence of almost running out of disk, most likely you do not have disk space monitoring in place. A fast publisher can fill up a few hundred gigabytes in way less time than you expect. |
Beta Was this translation helpful? Give feedback.
-
Community Support Policy
RabbitMQ version used
4.0.5
Erlang version used
26.2.x
Operating system (distribution) used
Windows Server 2019
How is RabbitMQ deployed?
Windows binary package
rabbitmq-diagnostics status output
See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
PASTE LOG HERE, BETWEEN BACKTICKS
rabbitmqctl deactivate_disk_monitoring once rabbitmq node is up and running
....
...
...
alarm_handler: {clear,{disk_almost_full,"E:\"}}
** Generic server memsup terminating
** Last message in was {'EXIT',<0.78183.0>,
{timeout,
{gen_server,call,
[os_mon_sysinfo,get_mem_info]}}}
** When Server state == [{data,[{"Timeout",60000}]},
{items,{"Memory Usage",
[{"Allocated",31803535360},
{"Total",274645454848}]}},
{items,{"Worst Memory User",
[{"Pid",<0.425.0>},{"Memory",6948808}]}}]
** Reason for termination ==
** {timeout,{gen_server,call,[os_mon_sysinfo,get_mem_info]}}
crasher:
initial call: memsup:init/1
pid: <0.128.0>
registered_name: memsup
exception exit: {timeout,{gen_server,call,[os_mon_sysinfo,get_mem_info]}}
in function gen_server:handle_common_reply/8 (gen_server.erl, line 1226)
ancestors: [os_mon_sup,<0.124.0>]
message_queue_len: 0
messages: []
links: [<0.125.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 2586
stack_size: 28
reductions: 142941200
neighbours:
crasher:
initial call: memsup:init/1
pid: <0.78188.0>
registered_name: memsup
exception exit: {{badmatch,{error,{fread,integer}}},
[{memsup,get_memory_usage,1,
[{file,"memsup.erl"},{line,616}]},
{memsup,'-handle_info/2-fun-0-',2,
[{file,"memsup.erl"},{line,361}]}]}
in function gen_server:handle_common_reply/8 (gen_server.erl, line 1226)
ancestors: [os_mon_sup,<0.124.0>]
message_queue_len: 0
messages: []
links: [<0.125.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 6772
stack_size: 28
reductions: 12414
neighbours:
supervisor: {local,os_mon_sup}
errorContext: child_terminated
reason: {{badmatch,{error,{fread,integer}}},
[{memsup,get_memory_usage,1,[{file,"memsup.erl"},{line,616}]},
{memsup,'-handle_info/2-fun-0-',2,
[{file,"memsup.erl"},{line,361}]}]}
offender: [{pid,<0.78188.0>},
{id,memsup},
{mfargs,{memsup,start_link,[]}},
{restart_type,permanent},
{significant,false},
{shutdown,2000},
{child_type,worker}]
supervisor: {local,os_mon_sup}
errorContext: shutdown
reason: reached_max_restart_intensity
offender: [{pid,<0.78188.0>},
{id,memsup},
{mfargs,{memsup,start_link,[]}},
{restart_type,permanent},
{significant,false},
{shutdown,2000},
{child_type,worker}]
Application os_mon exited with reason: shutdown
PASTE LOG HERE, BETWEEN BACKTICKS
PASTE LOG HERE, BETWEEN BACKTICKS
PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS
{vm_memory_high_watermark, {absolute, "2048M"}},
%%
%% Supported units suffixes:
%%
%% k, kiB: kibibytes (2^10 bytes)
%% M, MiB: mebibytes (2^20)
%% G, GiB: gibibytes (2^30)
%% kB: kilobytes (10^3)
%% MB: megabytes (10^6)
%% GB: gigabytes (10^9)
%% Fraction of the high watermark limit at which queues start to
%% page message out to disc in order to free up memory.
%% For example, when vm_memory_high_watermark is set to 0.4 and this value is set to 0.5,
%% paging can begin as early as when 20% of total available RAM is used by the node.
%%
%% Values greater than 1.0 can be dangerous and should be used carefully.
%%
%% One alternative to this is to use durable queues and publish messages
%% as persistent (delivery mode = 2). With this combination queues will
%% move messages to disk much more rapidly.
%%
%% Another alternative is to configure queues to page all messages (both
%% persistent and transient) to disk as quickly
%% as possible, see https://www.rabbitmq.com/lazy-queues.html.
%%
%% {vm_memory_high_watermark_paging_ratio, 0.5},
%% Selects Erlang VM memory consumption calculation strategy. Can be
allocated,rssorlegacy(aliased aserlang),%% Introduced in 3.6.11.
rssis the default as of 3.6.12.%% See #1223 and rabbitmq/rabbitmq-common#224 for background.
%% {vm_memory_calculation_strategy, rss},
%% Interval (in milliseconds) at which we perform the check of the memory
%% levels against the watermarks.
%%
%% {memory_monitor_interval, 2500},
%% The total memory available can be calculated from the OS resources
%% - default option - or provided as a configuration parameter:
{total_memory_available_override_value, "25600MB"},
%% Set disk free limit (in bytes). Once free disk space reaches this
%% lower bound, a disk alarm will be set - see the documentation
%% listed above for more details.
%%
%% {disk_free_limit, 50000000},
%%
%% Or you can set it using memory units (same as in vm_memory_high_watermark)
%% with RabbitMQ 3.6.0+.
%% {disk_free_limit, "50MB"},
%% {disk_free_limit, "50000kB"},
%% {disk_free_limit, "2GB"},
PASTE advanced.config HERE, BETWEEN BACKTICKS
Kubernetes deployment file
What problem are you trying to solve?
I was facing issue where get_disk_info giving issue,.
Through the rabbitmq forum I got a solution to run rabbitmqctl deactivate_disk_monitoring once rabbitmq node is up and running
now I am running rabbitmqctl deactivate_disk_monitoring once rabbitmq node is up and running still I am getting disk montoring issue.
PS: I also have got disk almost full alarm also
Beta Was this translation helpful? Give feedback.
All reactions