2017-07-26 155 views
1

的RabbitMQ未能安装/启动Debian的拉伸

sudo apt-get install rabbitmq-server 

我击球失误时,该服务试图启动(也使用systemctl start时):

● rabbitmq-server.service - RabbitMQ Messaging Server 
    Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) 
    Active: failed (Result: exit-code) since Wed 2017-07-26 15:59:41 IDT; 4min 28s ago 
    Process: 17895 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait (code=exited, status=70) 
    Process: 17894 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE) 
Main PID: 17894 (code=exited, status=1/FAILURE) 

这是一个在systemctl status。在journalctl -xe

-- Unit rabbitmq-server.service has begun starting up. 
Jul 26 15:59:37 myhost rabbitmq[17895]: Waiting for [email protected] ... 
Jul 26 15:59:37 myhost rabbitmq[17895]: pid is 17903 ... 
Jul 26 15:59:40 myhost systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE 
Jul 26 15:59:41 myhost rabbitmq[17895]: Error: process_not_running 
Jul 26 15:59:41 myhost systemd[1]: rabbitmq-server.service: Control process exited, code=exited status=70 
Jul 26 15:59:41 myhost systemd[1]: Failed to start RabbitMQ Messaging Server. 
-- Subject: Unit rabbitmq-server.service has failed 
-- Defined-By: systemd 
-- Support: https://www.debian.org/support 
-- 
-- Unit rabbitmq-server.service has failed. 
-- 
-- The result is failed. 
Jul 26 15:59:41 myhost systemd[1]: rabbitmq-server.service: Unit entered failed state. 
Jul 26 15:59:41 myhost systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. 
+0

嗨!您可以发布位于'/ var/log/rabbitmq'中的RabbitMQ日志文件吗? –

+0

@ Jean-SébastienPédron对不起,我得到它的工作,所以他们现在不显示任何错误。我不知道他们,所以评论应该有助于其他人在这里看。 – kabanus

+0

好吧,很好,你解决了它:) –

回答

1

OK,这是一个粗略的一个:

  1. 确保您的主机名是正确的。您可以运行

    须藤主机--file的/ etc /主机名

    确保。如果它不改变它通过改变/etc/hostnamea.b.c.d应该足够了。

  2. 如果您在公司防火墙后面rabbitmq将无法​​连接到所有接口。更改/etc/rabbitmq/rabbitmq-env.conf,设置[email protected]。这对于开发已经足够了。

现在你可以通过sudo apt-get install --fix-broken来完成安装(会抱怨它被安排了更多的东西)。使用sudo rabbitmqctl status来确保节点正常运行 - 如果没有,它会清楚地说明。