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

More diagnostic information needed for "No agent found for <type_id>:<instance_id>" messages

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: Deprecated: Server
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

The following error occurs frequently in many environments:

2010-02-11 09:37:28,046 WARN [AgentScheduleSyncListener1] [org.hyperic.hq.measurement.server.session.MeasurementProcessorEJBImpl@134] No agent found for 3:16823

In most scenarios, the referenced entity id does not exist in the system, so it would appear a rogue agent is reporting this ID, which in turn causes an attempted reschedule of metrics. With the absence of any resource information, it's not possible to determine which agent is reporting the bad data without enabling debug logging on other classes.

Improvement request is to either:

1) Improve the logging of this so that the administration actionable steps to resolve the situation

or

2) Fix the code such that HQ automatically recovers from these warnings.

Activity

Hide
Ryan Morgan added a comment -

It would appear the source of these errors are SRN's sent back from an agent for non-existent entities. Within ReportProcessorEJBImpl we attempt to run an unschedule() on the metrics, which results in the "No agent found" since the resource no longer exists.

Show
Ryan Morgan added a comment - It would appear the source of these errors are SRN's sent back from an agent for non-existent entities. Within ReportProcessorEJBImpl we attempt to run an unschedule() on the metrics, which results in the "No agent found" since the resource no longer exists.

People

Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
    Last comment:
    4 years, 9 weeks, 4 days ago