[rabbitmq-discuss] Problems starting 2.4.0 on OS X w/ mgmt plugins
Jon Brisbin
I'm using the Homebrew install of RabbitMQ 2.4.0 and the latest-and-greatest management plugins. When I start the broker, it gives me some warnings and then stops loading. When I hit ^C twice, it continues to start the broker.
The management plugin seems to be working, but it just won't start cleanly. It didn't do this originally, but has started doing it now every time. Don't know if I subsequently installed something it doesn't like or what...
Here's my console output:
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
6 plugins activated:
* amqp_client-2.4.0
* mochiweb-1.3
* rabbit_management-2.4.0.1
* rabbit_management_agent-2.4.0
* rabbit_mochiweb-2.4.0
* webmachine-1.7.0
^C
BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
(v)ersion (k)ill (D)b-tables (d)istribution
^C
^^^^^^^^
This is where I kill it...then it continues on fine...
+---+ +---+
| | | |
| | | |
| | | |
| +---+ +-------+
| |
| RabbitMQ +---+ |
| | | |
| v2.4.0 +---+ |
| |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2011 VMware, Inc.
Licensed under the MPL. See http://www.rabbitmq.com/
node : rabbit@jbrisbin
app descriptor : /usr/local/Cellar/rabbitmq/2.4.0/lib/rabbitmq/erlang/lib/rabbitmq-2.4.0/ebin/rabbit.app
home dir : /Users/jbrisbin
config file(s) : (none)
cookie hash : XseAPjfnLNBJwJJ074sjQw==
log : /usr/local/var/log/rabbitmq/rab...@jbrisbin.log
sasl log : /usr/local/var/log/rabbitmq/rab...@jbrisbin-sasl.log
database dir : /usr/local/var/lib/rabbitmq/mnesia/rabbit@jbrisbin
erlang version : 5.8.3
starting file handle cache server ...done
starting worker pool ...done
starting database ...done
starting codec correctness check ...done
-- external infrastructure ready
starting plugin registry ...done
starting auth mechanism cr-demo ...done
starting auth mechanism amqplain ...done
starting auth mechanism plain ...done
starting statistics event manager ...done
starting logging server ...done
starting exchange type direct ...done
starting exchange type fanout ...done
starting exchange type headers ...done
starting exchange type topic ...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 agent ...done
starting management statistics database ...done
starting queue supervisor and queue recovery ...done
-- message delivery logic ready
starting error log relay ...done
starting networking ...done
starting direct_client ...done
starting notify cluster nodes ...done
broker running
** Found 0 name clashes in code paths
I'm using R14B02 (Homebrew).
Logs show nothing of import, though I included them below for the sake of completeness.
Any ideas?
Thanks!
Jon Brisbin
http://jbrisbin.com
Twitter: @j_brisbin
rab...@jbrisbin.log:
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
Limiting to approx 156 file handles (138 sockets)
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
Memory limit set to 2852MB.
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
Management plugin upgraded statistics to fine.
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
Statistics database started.
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index
=WARNING REPORT==== 30-Mar-2011::14:11:32 ===
msg_store_persistent: rebuilding indices from scratch
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
started TCP Listener on 0.0.0.0:5672
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
started TCP Listener on 0.0.0.0:5672
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
Management agent started.
=INFO REPORT==== 30-Mar-2011::14:11:32 ===
Management plugin started.
HTTP API: http://jbrisbin:55672/api/
Management UI: http://jbrisbin:55672/mgmt/
Jonathan Brisbin
Any ideas?
Thanks!
Jon Brisbin
SpringSource (a division of VMware)
Twitter: @j_brisbin
rab...@jbrisbin.log:
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Matthias Radestock
Jon Brisbin wrote:
> 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
> 6 plugins activated:
> * amqp_client-2.4.0
> * mochiweb-1.3
> * rabbit_management-2.4.0.1
> * rabbit_management_agent-2.4.0
> * rabbit_mochiweb-2.4.0
> * webmachine-1.7.0
>
> ^C
> BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
> (v)ersion (k)ill (D)b-tables (d)istribution
> ^C
>
> ^^^^^^^^
> This is where I kill it...then it continues on fine...
Do you encounter the same behaviour w/o any plug-ins installed? I
suspect you do, but please check.
FWIW, I reckon rabbit gets stuck at
http://hg.rabbitmq.com/rabbitmq-server/file/rabbitmq_v2_4_0/src/rabbit_prelaunch.erl#l250
Does your hostname (jbrisbin) resolve? Is the epmd process running after
you have started rabbit for the first time? And can you connect to epmd
on your hostname ('telnet jbrisbin 4369')?
Regards,
Matthias.
Gavin M. Roy
Jon Brisbin
Simon MacMullen
> I still get the warnings, either way. But I don't think that's directly
> related to this network issue.
Those particular warnings are harmless - there are bits inside of
mochiweb and webmachine which are on code paths we never hit but which
reference code which is unlikely to be installed (fdsrv) or does not
exist (webmachine_resource).
I wanted to whitelist those particular warnings but it's a bit of a
contentious issue.
Cheers, Simon
--
Simon MacMullen
Staff Engineer, RabbitMQ
SpringSource, a division of VMware
Jon Brisbin
On Mar 31, 2011, at 10:30 AM, Simon MacMullen wrote:
> Those particular warnings are harmless - there are bits inside of mochiweb and webmachine which are on code paths we never hit but which reference code which is unlikely to be installed (fdsrv) or does not exist (webmachine_resource).
>
> I wanted to whitelist those particular warnings but it's a bit of a contentious issue.
Thanks for the clarification!
Jon Brisbin
http://jbrisbin.com
Twitter: @j_brisbin