Failed to start RabbitMQ broker

6,704 views
Skip to first unread message

Keeshia San Pascual

unread,
Jul 6, 2017, 2:10:26 AM7/6/17
to rabbitmq-users
Hi experts,

I would like to seek your advice on the error that we are experiencing with rabbitmq-server.service.
This was working smoothly before and we've been using it for months along with Sensu-Enterprise but when we reboot our system (Ubuntu 16.04) and tried to start rabbitmq-server.service with systemctl start rabbitmq-server, it failed w/ error message:

Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.

it's same with rabbitmqctl -n rabbit@flosensu1 start_app command:

DIAGNOSTICS

===========

 

attempted to contact: [rabbit@flosensu1]

 

rabbit@flosensu1:

  * connected to epmd (port 4369) on flosensu1

  * epmd reports: node 'rabbit' not running at all

                  no other nodes on flosensu1

  * suggestion: start the node

 

current node details:

- node name: 'rabbitmq-cli-83@flosensu1'

- home dir: /var/lib/rabbitmq

- cookie hash: cq9DLBg0TJau+dwZYiCnEA==

We have also tried to remove /var/log/rabbitmq/* to reset the node but it's still not working. 
ps -ef | grep rabbit

floadmin  2550  2401  0 02:55 pts/1    00:00:00 systemctl status rabbitmq-server.service
floadmin  2554  2401  0 02:56 pts/1    00:00:00 tail -f rab...@flosensu1.log
floadmin  2556  2401  0 02:57 pts/1    00:00:00 tail -f rab...@flosensu1-sasl.log
floadmin 15408  2401  0 07:01 pts/1    00:00:00 grep --color=auto rabbit

I've attached rab...@rabbitmq.log, rab...@rabbitmq-sasl.log just and the status for systemctl for references. 

systemctl status

Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.
admin@ flosensu1:/var/lib/rabbitmq$ systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2017-07-06 06:23:17 BST; 9s ago
  Process: 13769 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
  Process: 13408 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE)
 Main PID: 13408 (code=exited, status=1/FAILURE)

Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]:   * epmd reports: node 'rabbit' not running at all
Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]:                   other nodes on rabbitmq: ['rabbitmq-cli-85']
Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]:   * suggestion: start the node
Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]: current node details:
Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]: - node name: 'rabbitmq-cli-85@flosensu1'
Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]: - home dir: /var/lib/rabbitmq
Jul 06 06:23:17 flosensu1 rabbitmqctl[13769]: - cookie hash: cq9DLBg0TJau+dwZYiCnEA==
Jul 06 06:23:17 flosensu1 systemd[1]: Failed to start RabbitMQ broker.
Jul 06 06:23:17 flosensu1 systemd[1]: rabbitmq-server.service: Unit entered failed state.
Jul 06 06:23:17 flosensu1 systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.

 

journalctl -xe

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:                      [tcp_listener_sup]}}}},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:         [{rabbit_networking,start_listener0,5,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_networking.erl"},{line,294}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_networking,'-start_listener/5-lc$^0/1-0-',5,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_networking.erl"},{line,282}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_networking,start_listener,5,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_networking.erl"},{line,282}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_networking,'-boot_ssl/1-lc$^0/1-0-',3,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_networking.erl"},{line,142}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_networking,boot_ssl,1,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_networking.erl"},{line,142}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_networking,boot,0,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_networking.erl"},{line,128}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_boot_steps,'-run_step/2-lc$^1/1-1-',1,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_boot_steps.erl"},{line,49}]},

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:          {rabbit_boot_steps,run_step,2,

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:              [{file,"src/rabbit_boot_steps.erl"},{line,49}]}]}}

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]: Log files (may contain more information):

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rab...@rabbitmq.log

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rab...@rabbitmq-sasl.log

Jul 06 06:39:00 flosensu1 rabbitmq-server[14614]: {"init terminating in do_boot",{could_not_start,rabbit,{{case_clause,{error,{{shutdown,{failed_to_start_child,{ranch_listener_s

Jul 06 06:39:00 flosensu1 rabbitmq-server[14614]: [{file,"src/rabbit_boot_steps.erl"},{line,49}]}]}}}

Jul 06 06:39:00 flosensu1 rabbitmq-server[14614]: init terminating in do_boot ()

Jul 06 06:39:00 flosensu1 rabbitmq-server[14614]: [1B blob data]

Jul 06 06:39:02 flosensu1 rabbitmq-server[14614]: Crash dump is being written to: erl_crash.dump...done

Jul 06 06:39:02 flosensu1 systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: Stopping and halting node rabbit@rabbitmq ...

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: Error: unable to connect to node rabbit@rabbitmq: nodedown

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: DIAGNOSTICS

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: ===========

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: attempted to contact: [rabbit@rabbitmq]

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: rabbit@rabbitmq:

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]:   * connected to epmd (port 4369) on rabbitmq

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]:   * epmd reports: node 'rabbit' not running at all

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]:                   other nodes on rabbitmq: ['rabbitmq-cli-68']

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]:   * suggestion: start the node

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: current node details:

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: - node name: 'rabbitmq-cli-68@flosensu1'

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: - home dir: /var/lib/rabbitmq

Jul 06 06:39:04 flosensu1 rabbitmqctl[14833]: - cookie hash: cq9DLBg0TJau+dwZYiCnEA==

Jul 06 06:39:04 flosensu1 systemd[1]: Failed to start RabbitMQ broker.

-- Subject: Unit rabbitmq-server.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit rabbitmq-server.service has failed.

--

-- The result is failed.

 

rabbitmq.conf

[{rabbit, [

     {ssl_listeners, [5671]},

     {ssl_options, [{cacertfile,"/etc/rabbitmq/ssl/cacert.pem"},

                    {certfile,"/etc/rabbitmq/ssl/cert.pem"},

                    {keyfile,"/etc/rabbitmq/ssl/key.pem"},

                    {versions, ['tlsv1.2']},

                    {verify,verify_peer},

                    {fail_if_no_peer_cert,true}]}

    ]},

    {rabbitmq_management, [{listener, [{port, 15672}]}]}

].

Truly appreciate your response. :)






rabbit@rabbitmq.log
rabbit@rabbitmq-sasl.log

Gabriele Santomaggio

unread,
Jul 6, 2017, 3:08:51 AM7/6/17
to rabbitmq-users

the problem is:
=ERROR REPORT==== 6-Jul-2017::04:25:32 === Failed to start Ranch listener {acceptor,{0,0,0,0,0,0,0,0},5671} in ranch_ssl:listen([{port, 5671}, true}]) for reason eaddrinuse (address already in use)

the server can't bind the port 5671, most likely the port is already used. 

-
Gabriele

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rabbit@rabbitmq.log

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rabbit@rabbitmq-sasl.log

Michael Klishin

unread,
Jul 6, 2017, 5:09:29 AM7/6/17
to rabbitm...@googlegroups.com
Not just likely, the error says "eaddrinuse" ;) Another running process
(likely a RabbitMQ node but could be something else) is already bound to port 5671.



--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Keeshia San Pascual

unread,
Jul 12, 2017, 12:16:49 AM7/12/17
to rabbitmq-users
Hi,

Thanks for your response.! :) Managed to make it work by changing the port to 5673 because the previous port (5671) was being used by another application. Although, I've tried to uninstall the application that was using 5671, rabbitmq still won't start so changing the port does the trick.

Many Thanks!

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rabbit@rabbitmq.log

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rabbit@rabbitmq-sasl.log

Michael Klishin

unread,
Jul 12, 2017, 5:28:19 AM7/12/17
to rabbitm...@googlegroups.com
This means uninstalling the app did not shut down the instance that is using the port.

Anyhow, there's nothing wrong with using a non-standard port as long as your
team/apps/libraries are aware of it :)

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

snigdha kadam

unread,
Jul 20, 2018, 4:26:48 AM7/20/18
to rabbitmq-users

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rabbit@rabbitmq.log

Jul 06 06:38:59 flosensu1 rabbitmq-server[14614]:    /var/log/rabbitmq/rabbit@rabbitmq-sasl.log

 I have same problem. Could you please help me solve it?
 
Reply all
Reply to author
Forward
0 new messages