[rabbitmq-discuss] Problems starting 2.4.0 on OS X w/ mgmt plugins
Gavin M. Roy
gmr at myyearbook.com
Thu Mar 31 15:45:40 BST 2011
For what it's worth, I run into this on OSX as well from time to time with
previous versions. When it happens, a CTRL-C where its hung gets things
I'll look for hostname resolution issues when/if I see it again.
On Thu, Mar 31, 2011 at 2:22 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:
> 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-220.127.116.11
>> * rabbit_management_agent-2.4.0
>> * rabbit_mochiweb-2.4.0
>> * webmachine-1.7.0
>> BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
>> (v)ersion (k)ill (D)b-tables (d)istribution
>> 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
> 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')?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss