[rabbitmq-discuss] RabbitMQ won't start on RHEL 6.1
Dana Rea
danarea at gmail.com
Sat Jul 9 22:15:39 BST 2011
When starting rabbit, the network start fails (messages below). From
the messages, it seems like rabbit and epmd are both trying to connect
on 5672 since there's an 'eaddrinuse' message in the log file.
I installed RabbitMQ and Erlang using Fedora's EPEL 6 repo. Rabbit is
version 2.1.1 and Erlang is R14B.
Startup Messages:
Activating RabbitMQ plugins ...
*WARNING* Undefined function fdsrv:bind_socket/2
*WARNING* Undefined function fdsrv:start/0
*WARNING* Undefined function fdsrv:stop/0
*WARNING* Undefined function webmachine_resource:start_link/2
8 plugins activated:
* amqp_client-2.1.1
* erlang_smtp-0.0
* mochiweb-1.4.1
* rabbit_stomp-2.1.1
* rabbit_management-2.1.1
* rabbit_mochiweb-2.1.1
* rabbitmq_smtp_server-2.1.1
* webmachine-1.7.0
+---+ +---+
| | | |
| | | |
| | | |
| +---+ +-------+
| |
| RabbitMQ +---+ |
| | | |
| v2.1.1 +---+ |
| |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2010 LShift Ltd., Cohesive Financial Technologies
LLC., and Rabbit Technologies Ltd.
Licensed under the MPL. See http://www.rabbitmq.com/
node : rabbit at srv6
app descriptor : /usr/lib/rabbitmq/lib/rabbitmq_server-2.1.1/sbin/../
ebin/rabbit.app
home dir : /var/lib/rabbitmq
cookie hash : LohMTiS/RBnxf/P8CT1n0A==
log : /var/log/rabbitmq/rabbit at srv6.log
sasl log : /var/log/rabbitmq/rabbit at srv6-sasl.log
database dir : /var/lib/rabbitmq/mnesia/rabbit at srv6
erlang version : 5.8.1
starting file handle cache
server ...done
starting worker
pool ...done
starting
database ...done
starting codec correctness
check ...done
-- external infrastructure ready
starting exchange type
registry ...done
starting exchange type
topic ...done
starting exchange type
headers ...done
starting exchange type
fanout ...done
starting exchange type
direct ...done
starting statistics event
manager ...done
starting logging
server ...done
-- kernel ready
starting alarm
handler ...done
starting node
monitor ...done
starting cluster
delegate ...done
starting guid
generator ...done
starting memory
monitor ...done
-- core initialized
starting empty DB
check ...done
starting exchange
recovery ...done
starting management statistics
database ...done
starting queue supervisor and queue
recovery ...done
-- message delivery logic ready
starting error log
relay ...done
starting
networking ...BOOT
ERROR: FAILED
Reason: {{badmatch,
{error,
{shutdown,
{child,undefined,'rabbit_tcp_listener_sup_0.0.0.0:5672',
{tcp_listener_sup,start_link,
[{0,0,0,0},
5672,
[binary,
{packet,raw},
{reuseaddr,true},
{backlog,128},
{exit_on_close,false}],
{rabbit_networking,tcp_listener_started,
[]},
{rabbit_networking,tcp_listener_stopped,
[]},
{rabbit_networking,start_client,[]},
"TCP Listener"]},
transient,infinity,supervisor,
[tcp_listener_sup]}}}},
[{rabbit_networking,start_listener,4},
{rabbit_networking,'-boot_tcp/0-lc$^0/1-0-',1},
{rabbit_networking,boot_tcp,0},
{rabbit_networking,boot,0},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1},
{rabbit,run_boot_step,1},
{rabbit,'-start/2-lc$^0/1-0-',1},
{rabbit,start,2}]}
Erlang has closed
{"Kernel pid
terminated",application_controller,"{application_start_failure,rabbit,
{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',
{rabbit,failure_during_boot}}}}}"}
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller)
({application_start_failure,rabbit,{bad_return,{{rabbit,start,[normal,
[]]},{'EXIT',{rabbit,failure_during_boot}}}}})
Log:
=INFO REPORT==== 9-Jul-2011::17:11:50 ===
Limiting to approx 924 file handles (829 sockets)
=INFO REPORT==== 9-Jul-2011::17:11:50 ===
Memory limit set to 12844MB.
=INFO REPORT==== 9-Jul-2011::17:11:50 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index
=INFO REPORT==== 9-Jul-2011::17:11:50 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide
index
=ERROR REPORT==== 9-Jul-2011::17:11:50 ===
failed to start TCP Listener on 0.0.0.0:5672 - eaddrinuse
=ERROR REPORT==== 9-Jul-2011::17:11:50 ===
FAILED
Reason: {{badmatch,
{error,
{shutdown,
{child,undefined,'rabbit_tcp_listener_sup_0.0.0.0:5672',
{tcp_listener_sup,start_link,
[{0,0,0,0},
5672,
[binary,
{packet,raw},
{reuseaddr,true},
{backlog,128},
{exit_on_close,false}],
{rabbit_networking,tcp_listener_started,
[]},
{rabbit_networking,tcp_listener_stopped,
[]},
{rabbit_networking,start_client,[]},
"TCP Listener"]},
transient,infinity,supervisor,
[tcp_listener_sup]}}}},
[{rabbit_networking,start_listener,4},
{rabbit_networking,'-boot_tcp/0-lc$^0/1-0-',1},
{rabbit_networking,boot_tcp,0},
{rabbit_networking,boot,0},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1},
{rabbit,run_boot_step,1},
{rabbit,'-start/2-lc$^0/1-0-',1},
{rabbit,start,2}]}
=INFO REPORT==== 9-Jul-2011::17:11:51 ===
application: rabbit
exited: {bad_return,{{rabbit,start,[normal,[]]},
{'EXIT',{rabbit,failure_during_boot}}}}
type: permanent
More information about the rabbitmq-discuss
mailing list