用户 '/' 的 RabbitMQ-vhost 'XYZ' 已关闭。即使用户拥有所有访问权限

Question

我使用的是 RabbitMQ 版本 3.7.17

因为我的AWS硬盘已完全被占用(100%已满)。因此所有服务都停止工作
解决方案:我扩展了 AWS 服务器内存，然后尝试启动所有 API 服务，然后它开始抛出错误。 (发布此内容开始出现错误)

Connection.open: (541) INTERNAL_ERROR - access to vhost '/' refused for user 'XYZ': vhost '/' is down

使用以下代码重新启动 RabbitmMQ 服务器仍然出现错误:

sudo 服务rabbitmq-server restart

如果我使用以下方式检查用户的权限:

sudorabbitmqctl list_permissions --vhost/

响应显示用户拥有所有访问权限。

Listing permissions for vhost "/" ...
user    configure   write   read
XYZ .*  .*  .*

谢谢。

Answer 1

由于内存已满，正在处理的 RabbitMQ 未完成，导致 vhost 中出现错误。

当尝试重新启动虚拟主机sudorabbitmqctl restart_vhost时出现错误:

ERROR:

Failed to start vhost '/' on node 'rabbit@ip-172-31-16-172'Reason: {:shutdown, {:failed_to_start_child, :rabbit_vhost_process, {:error, {{{:function_clause, [{:rabbit_queue_index, :journal_minus_segment1, [{{true, <<230, 140, 82, 5, 193, 81, 136, 75, 11, 91, 31, 232, 119, 30, 99, 112, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 144>>, <<131, 104, 6, 100, 0, 13, 98, 97, 115, 105, 99, 95, 109, 101, 115, 115, 97, 103, 101, 104, 4, 100, 0, 8, 114, 101, 115, 111, 117, 114, ...>>}, :no_del, :no_ack}, {{true, <<230, 140, 82, 5, 193, 81, 136, 75, 11, 91, 31, 232, 119, 30, 99, 112, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 144>>, <<131, 104, 6, 100, 0, 13, 98, 97, 115, 105, 99, 95, 109, 101, 115, 115, 97, 103, 101, 104, 4, 100, 0, 8, 114, 101, 115, 111, 117, ...>>}, :del, :no_ack}], [file: 'src/rabbit_queue_index.erl', line: 1231]}, {:rabbit_queue_index, :"-journal_minus_segment/3-fun-0-", 4, [file: 'src/rabbit_queue_index.erl', line: 1208]}, {:array, :sparse_foldl_3, 7, [file: 'array.erl', line: 1684]}, {:array, :sparse_foldl_2, 9, [file: 'array.erl', line: 1678]}, {:rabbit_queue_index, :"-recover_journal/1-fun-0-", 1, [file: 'src/rabbit_queue_index.erl', line: 915]}, {:lists, :map, 2, [file: 'lists.erl', line: 1239]}, {:rabbit_queue_index, :segment_map, 2, [file: 'src/rabbit_queue_index.erl', line: 1039]}, {:rabbit_queue_index, :recover_journal, 1, [file: 'src/rabbit_queue_index.erl', line: 906]}]}, {:gen_server2, :call, [#PID<10397.473.0>, :out, :infinity]}}, {:child, :undefined, :msg_store_persistent, {:rabbit_msg_store, :start_link, [:msg_store_persistent, '/var/lib/rabbitmq/mnesia/rabbit@ip-172-31-16-172/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L', [], {#Function<2.32138423/1 in :rabbit_queue_index>, {:start, [{:resource, "/", :queue, "xx_queue"}, {:resource, "/", :queue, "app_xxx_queue"}, {:resource, "/", :queue, "default"}, {:resource, "/", :queue, "xx_priority_queue"}, {:resource, "/", :queue, "xxx_queue"}, {:resource, "/", :queue, "xxxx_queue"}, {:resource, "/", :queue, "yyy_queue"}, {:resource, "/", :queue, "zzz_queue"}, {:resource, "/", :queue, "aaa_queue"}]}}]}, :transient, 30000, :worker, [:rabbit_msg_store]}}}}}

解决问题的步骤

1. 通过以下命令停止您的应用节点。

sudo rabbitmqctl stop_app

通过以下命令重置您的节点。从其所属的任何集群中删除节点，从管理数据库中删除所有数据，例如配置的用户和虚拟主机，并删除所有持久消息。(使用时要小心。) To backup your data before reset look here

sudo rabbitmqctl reset

通过以下命令启动您的节点。

sudo rabbitmqctl start_app

通过以下命令重新启动您的虚拟主机。

sudo rabbitmqctl restart_vhost

如果您正在使用一些依赖于 RabbitMQ 的应用程序。例如我使用 celery，您将必须再次重新启动它们。

这是 link这帮助我解决了这个问题。