Rabbitmq 服务器启动失败，文件被锁定 [英] Rabbitmq server start failed with file locked
本文介绍了Rabbitmq 服务器启动失败，文件被锁定的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
Rabbitmq 3.6.5 启动失败.如何解决?
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)
推荐答案
您在数据库升级过程中遇到了问题，看看发生了什么检查日志会很有趣
you have had a problem during the database upgrade, it would be interesting see what happened checking the logs
顺便说一句，为了快速解决这个问题，删除你的 mnesia 目录就足够了.
BTW To solve quickly the problem is enough to remove your mnesia directory.
目录通常位于 /var/lib/rabbitmq/mnesia ，查看 此处了解详情.
The directory is usually located in /var/lib/rabbitmq/mnesia , check here for detail.
注意
通过删除 mnesia 目录，您将丢失所有消息
By removing the mnesia directory you will lose all your messages
这篇关于Rabbitmq 服务器启动失败，文件被锁定的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
