We have a monitoring script that monitors rabbitmq queues and sends notification if message count is more than a threshold. Today the script stopped working. Followed below steps to troubleshoot issue:
- Logged in into first rabbitmq node and ran rabbitmqctl list_queues. It hung for 60 seconds and threw below output:
rabbit@rmq-node1 ~]$ rabbitmqctl list_queues
Timeout: 60.0 seconds …
Listing queues for vhost / …
name messages
q1 0
q2 0
{:badrpc, {:timeout, 60.0, “Some queue(s) are unresponsive, use list_unresponsive_queues command.”}}
- As suggested by above output, ran rabbitmqctl list_unresponsive_queues . It too appeared hung.
- The cluster has 7 nodes. So, thought of checking if the command hangs in other nodes as well. Surprisingly it didn’t hang in one of the nodes. We hypothesized that this node has network connectivity issues with other nodes. The ping commands to other nodes were failing but pings from other nodes to this problematic node was succeeding.
- After infra team resolved issue, we could run rabbitmqctl list_queues successfully.
Author Profile

Latest entries
- August 23, 2023How we reduced SOA OSB provisioning from 4 days to 4 hours
- May 23, 2023rabbitmqRabbitmq Connection Error: javax.net.ssl.SSLHandshakeException: Invalid ECDH ServerKeyExchange signature
- March 24, 2023rcuSOA Suite 12.2.1.4 installation: Got exception when auto configuring the schema component(s) with data obtained from shadow table
- March 9, 2023rabbitmqNot able to start Rabbitmq Cluster: Cannot declare a queue ‘~s’ on node ‘~s’: ~255p