[rabbitmq-discuss] 3.3.1 Management Console: "Not Found"
Greg Poirier
greg.poirier at opower.com
Tue May 20 17:49:41 BST 2014
I have a 3-node cluster running 3.3.1 with 2 disk and 1 ram node. The RAM
node (may be a red herring, not sure) is currently displaying only: "Not
Found" when I attempt to connect to the management console.
rabbitmqctl status says that the management plugin is up and running:
Status of node 'rabbit at dev-rabbitmq-1005' ...
[{pid,27060},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","3.3.1"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","3.3.1"},
{rabbit,"RabbitMQ","3.3.1"},
{os_mon,"CPO CXC 138 46","2.2.7"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.3.1"},
{webmachine,"webmachine","1.10.3-rmq3.3.1-gite9359c7"},
{mochiweb,"MochiMedia Web Server","2.7.0-rmq3.3.1-git680dba8"},
{mnesia,"MNESIA CXC 138 12","4.5"},
{amqp_client,"RabbitMQ AMQP Client","3.3.1"},
{ssl,"Erlang/OTP SSL application","4.1.6"},
{public_key,"Public key infrastructure","0.13"},
{crypto,"CRYPTO version 2","2.0.4"},
{asn1,"The Erlang ASN1 compiler version 1.6.18","1.6.18"},
{xmerl,"XML parser","1.2.10"},
{inets,"INETS CXC 138 49","5.7.1"},
{sasl,"SASL CXC 138 11","2.1.10"},
{stdlib,"ERTS CXC 138 10","1.17.5"},
{kernel,"ERTS CXC 138 10","2.14.5"}]},
{os,{unix,linux}},
{erlang_version,
"Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4]
[async-threads:30] [kernel-poll:true]\n"},
{memory,
[{total,89013360},
{connection_procs,812000},
{queue_procs,611688},
{plugins,300776},
{other_proc,9746376},
{mnesia,219952},
{mgmt_db,11840},
{msg_index,1086432},
{other_ets,6219592},
{binary,8045192},
{code,19622549},
{atom,2313537},
{other_system,40023426}]},
{alarms,[]},
{listeners,
[{clustering,9100,"::"},
{amqp,5672,"0.0.0.0"},
{'amqp/ssl',5671,"0.0.0.0"}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,4995638886},
{disk_free_limit,50000000},
{disk_free,27163828224},
{file_descriptors,
[{total_limit,65436},
{total_used,28},
{sockets_limit,58890},
{sockets_used,15}]},
{processes,[{limit,1048576},{used,349}]},
{run_queue,0},
{uptime,437829}]
...done.
The following is what's output to the browser:
Not found.
There are no errors in any of the RabbitMQ logs.
If it happens again, I will increase the log level in our configuration in
our dev environment and see if that produces any useful logs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140520/fee81679/attachment.html>
More information about the rabbitmq-discuss
mailing list