Rabbitmq服务器启动失败，文件已锁定(Rabbitmq server start failed with file locked)
Rabbitmq 3.6.5启动失败。 如何解决它？
BOOT FAILED
===========
Error description: “Found lock file at ~s.\n Either previous upgrade is in progress or has failed.\n Database
backup path: ~s”
Log files (may contain more information):
/var/log/rabbitmq/rabbit@vm-10-111-29-211.log
/var/log/rabbitmq/rabbit@vm-10-111-29-211-sasl.log
Stack trace: [{rabbit_upgrade,ensure_backup_taken,
[“/var/lib/rabbitmq/mnesia/rabbit@vm-10-111-29-211/schema_upgrade_lock”, “/var/lib/rabbitmq/mnesia/rabbit@vm-10-111-29-211-upgrade-backup”],
[{file,”src/rabbit_upgrade.erl”},{line,101}]},
{rabbit_upgrade,maybe_upgrade_mnesia,0,
[{file,”src/rabbit_upgrade.erl”},{line,144}]},
{rabbit,’-boot/0-fun-0-‘,0,[{file,”src/rabbit.erl”},{line,271}]},
{rabbit,start_it,1,[{file,”src/rabbit.erl”},{line,403}]},
{init,start_it,1,[]},
{init,start_em,1,[]}]
{“init terminating in do_boot”,”Found lock file at ~s.\n
Either previous upgrade is in progress or has failed.\n
Database backup path: ~s”}
Crash dump was written to: erl_crash.dump init terminating in do_boot
(Found lock file at ~s.
Either previous upgrade is in progress or has failed.
Database backup path: ~s)
Rabbitmq 3.6.5 start failed with this. How to fix it?
BOOT FAILED
===========
Error description: “Found lock file at ~s.\n Either previous upgrade is in progress or has failed.\n Database
backup path: ~s”
Log files (may contain more information):
/var/log/rabbitmq/rabbit@vm-10-111-29-211.log
/var/log/rabbitmq/rabbit@vm-10-111-29-211-sasl.log
Stack trace: [{rabbit_upgrade,ensure_backup_taken,
[“/var/lib/rabbitmq/mnesia/rabbit@vm-10-111-29-211/schema_upgrade_lock”, “/var/lib/rabbitmq/mnesia/rabbit@vm-10-111-29-211-upgrade-backup”],
[{file,”src/rabbit_upgrade.erl”},{line,101}]},
{rabbit_upgrade,maybe_upgrade_mnesia,0,
[{file,”src/rabbit_upgrade.erl”},{line,144}]},
{rabbit,’-boot/0-fun-0-‘,0,[{file,”src/rabbit.erl”},{line,271}]},
{rabbit,start_it,1,[{file,”src/rabbit.erl”},{line,403}]},
{init,start_it,1,[]},
{init,start_em,1,[]}]
{“init terminating in do_boot”,”Found lock file at ~s.\n
Either previous upgrade is in progress or has failed.\n
Database backup path: ~s”}
Crash dump was written to: erl_crash.dump init terminating in do_boot
(Found lock file at ~s.
Either previous upgrade is in progress or has failed.
Database backup path: ~s)
原文：https://stackoverflow.com/questions/41294754
更新时间：2020-02-03 07:21
最满意答案
在数据库升级过程中遇到问题，查看日志中发生了什么会很有趣
顺便解决这个问题很快就能解决你的mnesia目录。
该目录通常位于/var/lib/rabbitmq/mnesia ，请在此处查看详细信息。
注意
通过删除mnesia目录你将失去所有的信息
you have had a problem during the database upgrade, it would be interesting see what happened checking the logs
BTW To solve quickly the problem is enough to remove your mnesia directory.
The directory is usually located in /var/lib/rabbitmq/mnesia , check here for detail.
NOTE
By removing the mnesia directory you will lose all your messages
2016-12-23
相关问答
在Windows上，我通过以下步骤解决了问题：1.通过单击菜单中的“Repo-browser”来启动Repository Browser。 2.找到锁定的文件。 3.在锁定的文件上右键单击鼠标。 4.点击“中断锁定”。 On Windows, I fixed the problem by the following steps: 1. Launch Repository Browser by clicking “Repo-browser” in the menu. 2. Locate the lo
…
我改变了我将参数传递给exec maven插件的方式 由此 ：
org.codehaus.mojo
exec-maven-plugin
1.2.1
java
…
我修正了我的问题。 谁会有我同样的问题。 该插件无法绑定到端口1883，因为内核响应EACCESS错误。 某种安全工具(很可能是SELinux)需要将该端口列入白名单。 更改SELinux参数我能够解决我的问题。 这有两种可能 编辑文件/etc/selinux/config编辑字符串SELINUX=enforcing进入SELINUX=enforcing或进入(注意，这是一个安全错误) SELINUX=disabled 添加带有semanage port –add的端口1883 – 添加到SEL
…
您是否在安全存储使用的数据存储区中创建了RDBMS表？ 可以在WL_HOME / server / lib中找到创建脚本。 信息由http://docs.oracle.com/cd/E24329_01/web.1211/e24422/rdbms.htm#autoId5提供 Did you create RDBMS tables in the datastore used by the security store? Create scripts can be found in WL_HOME/se
…
我搞定了， 在第4步，我正在应对 /var/lib/rabbitmq/.erlang.cookie 从server1到server2 /var/lib/rabbitmq/.erlang.cookie位置。 但除此之外，.erlang.cookie是由我的主目录中的rabbitmq创建的 /home/me/.erlang.cookie。 我将它复制到server1 home / me和server 2 home / me /。 有了这个，我可以使用创建一个集群 sudo rabbitmqctl cl
…
将RabbitMQ更新为官方稳定版本修复了该问题。 Ubuntu 12.04存储库中的RabbitMQ包很老了。 Updating RabbitMQ to official stable version fixed the issue. The RabbitMQ package in Ubuntu 12.04’s repository was really old.
在数据库升级过程中遇到问题，查看日志中发生了什么会很有趣 顺便解决这个问题很快就能解决你的mnesia目录。 该目录通常位于/var/lib/rabbitmq/mnesia ，请在此处查看详细信息。 注意 通过删除mnesia目录你将失去所有的信息 you have had a problem during the database upgrade, it would be interesting see what happened checking the logs BTW To solve q
…
我希望你在RabbitMQ和ejabberd方面取得了一些进展。 以下是可能有帮助的有趣讨论的链接。 http://old.nabble.com/AMPQ-vs-XMPP-and-RabbitMQ-vs-ejabberd-td17587109.html I hope you had made some progress as far as RabbitMQ and ejabberd are concerned. Below is a link to an interesting discussio
…
您应该在启动Rabbit服务器(应用程序：start(sasl))之前尝试启动sasl以获取更多信息。 我已经检查了github上rabbitmq-server的rabbit模块中函数start(normal，[])的代码，我没看到对io：format / 2的直接调用。 更详细的报告可能有所帮助。 您可以看到io：格式失败，由于badarg原因，格式和参数在显示中被截断，因此无法确定错误，但可能的原因是参数列表的长度不适合格式定义。 You should try to start sasl pr
…
为了解决这个问题，我将日志文件的所有者更改为postgres ： chown postgres:posgres logfile_path
To solve the problem I changed the owner of the log file to postgres: chown postgres:posgres logfile_path