Аварийное завершение RabbitMQ, почему?

Периодически происходит аварийное завершение RabbitMQ, помогает только перезапуск службы.
В логе RabbitMQ:
2018-11-29 03:03:56.252 [info] <0.25351.6> accepting AMQP connection <0.25351.6> (172.17.1.2:55690 -> 172.18.42.2:5672)
2018-11-29 03:03:56.252 [error] <0.25351.6> CRASH REPORT Process <0.25351.6> with 0 neighbours exited with reason: {aborted,{no_exists,[rabbit_runtime_parameters,cluster_name]}} in mnesia:abort/1 line 355
2018-11-29 03:03:56.252 [error] <0.25349.6> Supervisor {<0.25349.6>,rabbit_connection_sup} had child reader started with rabbit_reader:start_link(<0.25350.6>, {acceptor,{0,0,0,0},5672}, #Port<0.147186>) at <0.25351.6> exit with reason {aborted,{no_exists,[rabbit_runtime_parameters,cluster_name]}} in context child_terminated
2018-11-29 03:03:56.252 [error] <0.25349.6> Supervisor {<0.25349.6>,rabbit_connection_sup} had child reader started with rabbit_reader:start_link(<0.25350.6>, {acceptor,{0,0,0,0},5672}, #Port<0.147186>) at <0.25351.6> exit with reason reached_max_restart_intensity in context shutdown
2018-11-29 03:03:56.879 [error] <0.25353.6> CRASH REPORT Process <0.25353.6> with 0 neighbours exited with reason: bad argument in call to ets:lookup(rabbit_exchange, {resource,<<"rdkb-1">>,exchange,<<"rdkb-1-stream">>}) in rabbit_misc:dirty_read/1 line 392
2018-11-29 03:03:56.879 [error] <0.1860.0> Supervisor {<0.1860.0>,rabbit_federation_link_sup} had child {upstream,[<<"amqp://server1:server1@172.17.1.2/server1">>],
          <<"rdkb-1-stream">>,<<"rdkb-1-stream">>,1000,1,5,none,none,false,
          'on-publish',none,<<"rmiac">>,false} started with rabbit_federation_exchange_link:start_link({{upstream,[<<"amqp://server1:server1@172.17.1.2/server1">>],<<"rdkb-1-stream">>,<<"rdkb-1-stream">>,...},...}) at {restarting,<0.24035.1>} exit with reason bad argument in call to ets:lookup(rabbit_exchange, {resource,<<"rdkb-1">>,exchange,<<"rdkb-1-stream">>}) in rabbit_misc:dirty_read/1 line 392 in context start_error
2018-11-29 03:03:57.269 [info] <0.25357.6> accepting AMQP connection <0.25357.6> (172.17.1.2:45651 -> 172.18.42.2:5672)
2018-11-29 03:03:57.269 [error] <0.25357.6> CRASH REPORT Process <0.25357.6> with 0 neighbours exited with reason: {aborted,{no_exists,[rabbit_runtime_parameters,cluster_name]}} in mnesia:abort/1 line 355
2018-11-29 03:03:57.269 [error] <0.25355.6> Supervisor {<0.25355.6>,rabbit_connection_sup} had child reader started with rabbit_reader:start_link(<0.25356.6>, {acceptor,{0,0,0,0},5672}, #Port<0.147185>) at <0.25357.6> exit with reason {aborted,{no_exists,[rabbit_runtime_parameters,cluster_name]}} in context child_terminated
2018-11-29 03:03:57.269 [error] <0.25355.6> Supervisor {<0.25355.6>,rabbit_connection_sup} had child reader started with rabbit_reader:start_link(<0.25356.6>, {acceptor,{0,0,0,0},5672}, #Port<0.147185>) at <0.25357.6> exit with reason reached_max_restart_intensity in context shutdown
2018-11-29 03:03:58.268 [info] <0.25360.6> accepting AMQP connection <0.25360.6> (172.17.1.2:37018 -> 172.18.42.2:5672)
2018-11-29 03:03:58.284 [error] <0.25360.6> CRASH REPORT Process <0.25360.6> with 0 neighbours exited with reason: {aborted,{no_exists,[rabbit_runtime_parameters,cluster_name]}} in mnesia:abort/1 line 355
2018-11-29 03:03:58.284 [error] <0.25358.6> Supervisor {<0.25358.6>,rabbit_connection_sup} had child reader started with rabbit_reader:start_link(<0.25359.6>, {acceptor,{0,0,0,0},5672}, #Port<0.147192>) at <0.25360.6> exit with reason {aborted,{no_exists,[rabbit_runtime_parameters,cluster_name]}} in context child_terminated
2018-11-29 03:03:58.284 [error] <0.25358.6> Supervisor {<0.25358.6>,rabbit_connection_sup} had child reader started with rabbit_reader:start_link(<0.25359.6>, {acceptor,{0,0,0,0},5672}, #Port<0.147192>) at <0.25360.6> exit with reason reached_max_restart_intensity in context shutdown
2018-11-29 03:03:58.393 [error] <0.25340.6> ** Generic server channel_queue_metrics_metrics_collector terminating
  • Вопрос задан
  • 344 просмотра
Пригласить эксперта
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы