[rabbitmq-discuss] rabbitmq nodedown - nodedown - Generic server rabbit_disk_monitor terminating
Michael Klishin
mklishin at gopivotal.com
Tue Oct 29 12:23:15 GMT 2013
On 29 Oct 2013, at 08:56, Michael Sander <michael.sander at gmail.com> wrote:
> ** Reason for termination ==
> ** {{badmatch,[]},
> [{rabbit_disk_monitor,parse_free_unix,1,[]},
> {rabbit_disk_monitor,internal_update,1,[]},
> {rabbit_disk_monitor,handle_info,2,[]},
> {gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,607}]},
> {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,227}]}]}
> =INFO REPORT==== 28-Oct-2013::19:48:36 ===
> Disabling disk free space monitoring on unsupported platform: {{'EXIT',
> {{badmatch,[]},
> [{rabbit_disk_monitor,
> parse_free_unix,
> 1,[]},
> {rabbit_disk_monitor,
> init,1,[]},
> {gen_server,
> init_it,6,
> [{file,
> "gen_server.erl"},
> {line,
> 304}]},
> {proc_lib,
> init_p_do_apply,
> 3,
> [{file,
> "proc_lib.erl"},
> {line,
> 227}]}]}},
> 1887428608}
Michael,
Is there a more or less reliable way to reproduce the issue? E.g. what OS, RabbitMQ
version and RabbitMQ configuration can we try? What is your workload like?
Thank you.
MK
Software Engineer, Pivotal/RabbitMQ
More information about the rabbitmq-discuss
mailing list