<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello!<div><br></div><div>(Reposted+edited since I forgot to join the list first)<br><br>I'm trying to move my actual (working) RabbitMQ node to another, less<br>loaded, server (actually another VM, hidden from internet, which will<br>also have a memcache).<br><br>So after setting up a barebone 64b Debian6 from a netinst and adding<br>RabbitMQ repo and installing it I got a working node.<br><br>Problem is, the management plugin seems to die, bringing down the<br>daemon with it after a couple of seconds (immediatly after start,<br>rabbitmq_ctl status does list plugins, two seconds later it's dead<br>already):<br><br>[... end of output launched from cli <a href="http://pastebin.com/rQGBDbF8">http://pastebin.com/rQGBDbF8</a> ]<br>broker running<br>** Found 0 name clashes in code paths<br>Erlang has closed<br>{"Kernel pid<br>terminated",application_controller,"{application_start_failure,rabbitmq_management,<br>{bad_return,{{rabbit_mgmt_app,start,[normal,[]]},{'EXIT',{timeout,<br>{gen_server,call,[rabbit_mochiweb_registry,<br>{add,rabbit_mgmt,#Fun<rabbit_mochiweb.2.78160903>,#Fun<rabbit_mochiweb.<br>5.23044403>,{[109,103,109,116],<br>[77,97,110,97,103,101,109,101,110,116,58,32,87,101,98,32,85,73]}}]}}}}}}"}<br>_____________<br>[... end of <a href="mailto:rabbit@mqcache.log">rabbit@mqcache.log</a> ]<br>=INFO REPORT==== 18-Jul-2011::17:57:27 ===<br>Management agent started.<br><br>=INFO REPORT==== 18-Jul-2011::17:57:27 ===<br>Management plugin started.<br>HTTP API: <a href="http://mqcache:55672/api/">http://mqcache:55672/api/</a><br>Management UI: <a href="http://mqcache:55672/mgmt/">http://mqcache:55672/mgmt/</a><br><br>=INFO REPORT==== 18-Jul-2011::17:57:32 ===<br> application: rabbitmq_management<br> exited: {bad_return,<br> {{rabbit_mgmt_app,start,[normal,[]]},<br> {'EXIT',<br> {timeout,<br> {gen_server,call,<br> [rabbit_mochiweb_registry,<br> {add,rabbit_mgmt,<br> #Fun<rabbit_mochiweb.2.78160903>,<br> #Fun<rabbit_mochiweb.5.23044403>,<br> {"mgmt","Management: Web UI"}}]}}}}}<br> type: permanent<br><br>=INFO REPORT==== 18-Jul-2011::17:57:32 ===<br>stopped TCP Listener on [::]:5672<br><br>Crash dump was written to: erl_crash.dump<br>Kernel pid terminated (application_controller)<br>({application_start_failure,rabbitmq_management,{bad_return,<br>{{rabbit_mgmt_app,start,[normal,[]]},{'EXIT',{timeout,{gen_server,call,<br>[rabbit_mochiweb_reg<br><br><br>All plugin files are there, I even compared the CRCs with my actual<br>RabbitMQ installation (which is another VM, just internet wise +<br>apache/mysql/etc...) . It's an independant node, no clustering,<br>replication, nothing special involved. Installing plugins one after<br>another boils it down to rabbitmq_management alone being the culprit.</div><div><br>As said, it's a fresh and updated Deb6 64b 2 CPUs, 2Gigs of RAM.<br>Erlang R14A (erts-5.8)<br>RabbitMQ 2.5.1<br># md5sum *.ez<br>2602dd3df87fa4c7dedd6eb3192b0c19 amqp_client-2.5.1.ez<br>07f3b87ccb1d03d479a4277014a7e017 mochiweb-1.3-rmq2.5.1-git9a53dbd.ez<br>69aa2c17ebfff7bdf141d8df0b358631 rabbitmq_management-2.5.1.ez<br>4165b7d2aeeeeae9239b173b5e803c89 rabbitmq_management_agent-2.5.1.ez<br>0cd0b60bd8b9019fd9dbea08f667a697 rabbitmq_mochiweb-2.5.1.ez<br>2c7fddc210317a054c97b43e13d38ced webmachine-1.7.0-rmq2.5.1-<br>hg0c4b60a.ez<br><br>The only diff I can imagine is that no queues/exchanges have ever been<br>created yet, and there's already an admin user created on it.<br><br>Has anyone encountered this? Erlang is a bit chinese to me, I might<br>have missed an obvious message somewhere, but I can't figure it out<br>yet :-)<br><br>Thanks in advance,<br><br>JaXX</div></body></html>