Introduction
Ce document décrit comment résoudre les problèmes lorsque vous vous connectez à l'interface utilisateur RabbitMQ.
Conditions préalables
Conditions requises
Aucune spécification déterminée n'est requise pour ce document.
Components Used
Les informations de ce document sont basées sur 4.7.X et 4.8.X.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Problème
Lorsque vous essayez de vous connecter à http://IP_address_of_AMQP:15672 via votre navigateur, vous recevez une erreur « refusé de vous connecter ».
Toujours sur la console RabbitMQ, voici ce que vous voyez :
[root@amqp ~]# rabbitmqctl status
Status of node rabbit@amqp ...
Error: unable to connect to node rabbit@amqp: nodedown
DIAGNOSTICS
===========
attempted to contact: [rabbit@amqp]
rabbit@amqp:
* connected to epmd (port 4369) on amqp
* epmd reports: node 'rabbit' not running at all
no other nodes on amqp
* suggestion: start the node
current node details:
- node name: 'rabbitmq-cli-3496@amqp'
- home dir: /var/lib/rabbitmq
- cookie hash: gsXBP8HgENjwAKcRmvMU6A==
Solution
1. Reconfigurer le nom d'hôte de la machine virtuelle (VM).
2. Réinstaller le lapin :
rm /etc/cliqr_modules.conf
yum remove -y wxGTK-g1-2.8.12-20.e17.x86_64
- Télécharger core_installer.bin :
chmod +x core+installer.bin
./core_installer.bin <os> <platform> rabbit
java -jar cco-installer.jar conn_broker-response.xml
- Redémarrer la machine virtuelle.
3. Ouvrez le port 15672 sur le pare-feu :
iptables -I INPUT 1 -p tcp --dport 15672 -j ACCEPT
service iptables save
service iptables restart
Vérification
Le produit escompté serait le suivant :
# netstat -atun | grep 15672
tcp 0 0 0.0.0.0:15672 0.0.0.0:* LISTEN
À partir d'une autre machine virtuelle, utilisez cette commande pour confirmer la connectivité :
telent IP_address_of_AMQP 15672
# rabbitmqctl status
]Status of node rabbit@haamqp2 ...
[{pid,1759},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","3.5.1"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.5.1"},
{webmachine,"webmachine","1.10.3-rmq3.5.1-gite9359c7"},
{mochiweb,"MochiMedia Web Server","2.7.0-rmq3.5.1-git680dba8"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","3.5.1"},
{rabbit,"RabbitMQ","3.5.1"},
{ssl,"Erlang/OTP SSL application","6.0"},
{public_key,"Public key infrastructure","0.23"},
{crypto,"CRYPTO","3.5"},
{asn1,"The Erlang ASN1 compiler version 3.0.4","3.0.4"},
{os_mon,"CPO CXC 138 46","2.3.1"},
{inets,"INETS CXC 138 49","5.10.6"},
{amqp_client,"RabbitMQ AMQP Client","3.5.1"},
{xmerl,"XML parser","1.3.7"},
{mnesia,"MNESIA CXC 138 12","4.12.5"},
{sasl,"SASL CXC 138 11","2.4.1"},
{stdlib,"ERTS CXC 138 10","2.4"},
{kernel,"ERTS CXC 138 10","3.2"}]},
{os,{unix,linux}},
{erlang_version,
"Erlang/OTP 17 [erts-6.4] [source-2e19e2f] [64-bit] [async-threads:30] [hipe] [kernel-poll:true]\n"},
{memory,
[{total,46019504},
{connection_readers,97704},
{connection_writers,19384},
{connection_channels,67928},
{connection_other,173656},
{queue_procs,165136},
{queue_slave_procs,0},
{plugins,501128},
{other_proc,13684160},
{mnesia,87752},
{mgmt_db,829016},
{msg_index,55056},
{other_ets,1144976},
{binary,1948544},
{code,22194354},
{atom,801697},
{other_system,4249013}]},
{alarms,[]},
{listeners,[{clustering,25672,"::"},{amqp,5672,"::"},{'amqp/ssl',5671,"::"}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,771738828},
{disk_free_limit,50000000},
{disk_free,6418993152},
{file_descriptors,
[{total_limit,3996},
{total_used,10},
{sockets_limit,3594},
{sockets_used,6}]},
{processes,[{limit,1048576},{used,267}]},
{run_queue,0},
{uptime,1622687}]
Vous devriez maintenant pouvoir ouvrir un navigateur Web sur http://IP_address_of_AMQP:15672 et lancer l'interface utilisateur de RabbitMQ. La connexion par défaut est cliqr/cliqr.
Commentaires