Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

RabbitMQ plugin - Queues are not discovered

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.6
  • Fix Version/s: 4.6, 4.x Sprint 28
  • Component/s: Plugins
  • Environment:
    Hyperic server 4.6.0-EE-247 on CentOS 5.4 x64 with embedded Postgres DB
    - Hyperic agent 4.6.0-EE-247 on RHEL 5.4 x64 running RabbitMQ 2.5.1 running SSL
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

RabbitMQ plugin - Queues are not discovered

RabbitMQ Queues are not being auto-discovered in Hyperic UI. Exchanges and Virtual Hosts are auto-discovered and report Availaibility and Metrics.

Expected Result:
Queues are auto-discovered and report Availability and Metrics

Actual Result:
Queues are not auto-discovered

Steps to Reproduce:

  1. Install and start agent on platform running RabbitMQ running HTTPS
  2. Log into Hyperic
  3. Add platform to inventory from AIQ
  4. Configure RabbitMQ as necessary including import of SSL cert into keystore
  5. Note server availability and metrics collect
  6. Note Exchanges and Virtual Hosts auto-discovered and show availability and metrics
  7. No existing Queues are not auto-discovered
  8. Add additional Queues to RabbitMQ
  9. Note Queues are not auto-discovered

Additional Information:
Restarting RabbitMQ or running manual auto-discover does not help.

Activity

Hide
German Laullon added a comment -

Are the queues Durables?

Show
German Laullon added a comment - Are the queues Durables?
Hide
German Laullon added a comment -

please, attach the agent.log with debug level.

Show
German Laullon added a comment - please, attach the agent.log with debug level.
Hide
Frederic Calindas added a comment -

Sorry forgot previous attachement. See uploaded 'agent.log' with debugging enabled.

# rabbitmqctl list_queues
Listing queues ...
Test Queue 5
Test Queue 2 1
...done.

Show
Frederic Calindas added a comment - Sorry forgot previous attachement. See uploaded 'agent.log' with debugging enabled. # rabbitmqctl list_queues Listing queues ... Test Queue 5 Test Queue 2 1 ...done.
Hide
German Laullon added a comment -

Both queue are no durable... so no auto-discover. You can mark "nodurable" option.

2011-07-22 17:54:01,441 DEBUG [CollectorThread] [HypericRabbitAdmin] [/api/queues/%2F] -(200)*> [RabbitQueue{name=Test Queue, durable=false, messageStats=null, vhost=/, idleSince=Fri Jul 22 13:50:11 EDT 2011, messages=5, consumers=0, messagesReady=5, messagesUnacknowledged=0, memory=10352}, RabbitQueue{name=Test Queue 2, durable=false, messageStats=null, vhost=/, idleSince=Fri Jul 22 13:51:32 EDT 2011, messages=1, consumers=0, messagesReady=1, messagesUnacknowledged=0, memory=7864}]

Show
German Laullon added a comment - Both queue are no durable... so no auto-discover. You can mark "nodurable" option. 2011-07-22 17:54:01,441 DEBUG [CollectorThread] [HypericRabbitAdmin] [/api/queues/%2F] -(200)*> [RabbitQueue{name=Test Queue, durable=false, messageStats=null, vhost=/, idleSince=Fri Jul 22 13:50:11 EDT 2011, messages=5, consumers=0, messagesReady=5, messagesUnacknowledged=0, memory=10352}, RabbitQueue{name=Test Queue 2, durable=false, messageStats=null, vhost=/, idleSince=Fri Jul 22 13:51:32 EDT 2011, messages=1, consumers=0, messagesReady=1, messagesUnacknowledged=0, memory=7864}]
Hide
Frederic Calindas added a comment -

Created durable queues which were properly auto-discovered.

Checking the box 'nodurable' to discover non-durable queues sucessfully discovered non-durable queues.

Show
Frederic Calindas added a comment - Created durable queues which were properly auto-discovered. Checking the box 'nodurable' to discover non-durable queues sucessfully discovered non-durable queues.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    2 years, 39 weeks, 5 days ago