Solving Auto-Discovery Problems

Refer to the sections below if you have trouble with resource discovery.

Removed Resources Not Rediscovered

If you delete a resource, and then immediately scan the platform, it is possible that the deleted resource will not be rediscovered during that scan.

In Hyperic, the resource deletion process is asynchronous. If you delete many resources at once, if the the deletion of a resource is not complete when the next scan is performed, the agent will find the resource already exists, and not report it as new or changed.

Discovered Resources Not Imported

If a resource still appears in the Auto-Discovery Portlet after you clicked Add to Inventory to import it to inventory, you can use HQ Health to troubleshoot the problem. Use the available database queries to check the autoinventory queue - if the resource you wish to add appears in the queue, use the Purge Autoinventory Queue action. Initiate an auto-discovery scan and try importing the resource after it is re-discovered.

Auto-Discovering WebLogic Server on Linux and Solaris

To auto-discover a WebLogic Server instance on Linux or Solaris, the Hyperic Agent must be able to read its current working directory /proc/$pid/cwd. To ensure that the agent has sufficient privileges, you can:

  • Run the Hyperic Agent as the same user that runs the WebLogic Server Administration Server,

  • Run the Hyperic Agent as root, or

  • Under Solaris 10 only, grant the agent account permission to read /proc/$pid/ files within the Solaris 10 Least Privilege Model (LPM). For instructions, see Configure Agent Account Privileges under Solaris 10.

For additional information about solving problems with auto-discovery of WebLogic Server, see WebLogic Server.

Auto-Discovering Server Types on Solaris

A Hyperic Agent can fail to auto-discover some types of servers running under Solaris for a combination of reasons.

Solaris limits the length of the publicly-viewable process arguments struct member to 80 bytes, which can result in truncation of process arguments that the agent needs to read. To obtain all arguments, the agent will attempt to access the process address space file{{/proc/$pid/as}}and fail, if it lacks permission.

If the Hyperic Agent does not auto-discover servers under Solaris, run the agent as root, or grant the agent account permission to read /proc/$pid/ files within the Solaris 10 Least Privilege Model (LPM). For instructions, see Configure Agent Account Privileges under Solaris 10 in Getting Started with vFabric Hyperic.