实际上我不知道如何在我的标题中描述我的问题。我遇到的问题是我通过Homebrew在本地安装了RabbitMQ(Mac),然后突然就死了,我突然就无法向队列发送消息了,很遗憾我无法发布错误消息,因为我尝试了其他几个步骤,包括重置、卸载、重新安装Rabbit,重新安装后,我无法启动Rabbit服务器;在此之后它会卡住:
sudo rabbitmq-server start
Password:
2022-08-05 11:14:17.972308-04:00 [info] <0.221.0> Feature flags: list of feature flags found:
2022-08-05 11:14:17.979492-04:00 [info] <0.221.0> Feature flags: [x] classic_mirrored_queue_version
2022-08-05 11:14:17.979531-04:00 [info] <0.221.0> Feature flags: [x] implicit_default_bindings
2022-08-05 11:14:17.979546-04:00 [info] <0.221.0> Feature flags: [x] maintenance_mode_status
2022-08-05 11:14:17.979568-04:00 [info] <0.221.0> Feature flags: [x] quorum_queue
2022-08-05 11:14:17.979583-04:00 [info] <0.221.0> Feature flags: [x] stream_queue
2022-08-05 11:14:17.979599-04:00 [info] <0.221.0> Feature flags: [x] user_limits
2022-08-05 11:14:17.979611-04:00 [info] <0.221.0> Feature flags: [x] virtual_host_metadata
2022-08-05 11:14:17.979672-04:00 [info] <0.221.0> Feature flags: feature flag states written to disk: yes
2022-08-05 11:14:18.203961-04:00 [notice] <0.44.0> Application syslog exited with reason: stopped
2022-08-05 11:14:18.204012-04:00 [notice] <0.221.0> Logging: switching to configured handler(s); following messages may not be visible in this log output
## ## RabbitMQ 3.10.7
## ##
########## Copyright (c) 2007-2022 VMware, Inc. or its affiliates.
###### ##
########## Licensed under the MPL 2.0. Website: https://rabbitmq.com
Erlang: 25.0.3 [jit]
TLS Library: OpenSSL - OpenSSL 1.1.1q 5 Jul 2022
Doc guides: https://rabbitmq.com/documentation.html
Support: https://rabbitmq.com/contact.html
Tutorials: https://rabbitmq.com/getstarted.html
Monitoring: https://rabbitmq.com/monitoring.html
Logs: /usr/local/var/log/rabbitmq/rabbit@localhost.log
/usr/local/var/log/rabbitmq/rabbit@localhost_upgrade.log
<stdout>
Config file(s): (none)
Starting broker... completed with 7 plugins.
在这之后,它就永远挂着了。
我想完全卸载兔子从我的电脑和重新安装它从新鲜;当我第一次安装它的时候,它就像一个护身符,但是自从他们不知怎么的就坏了。有人能帮我吗?
当然,最明显的是brew rm rabbitmq
,但这就是我陷入这种情况的原因,它不可能那么简单。
1条答案
按热度按时间j8ag8udp1#
我成功了。这些步骤的组合成功了:
1.更改服务的权限:
1.重新加载launchctl配置:
1.重新启动服务:
然后就成功了。