FglAMs are connected to the FMS but not listed in Agent Manager dashboard. This manifests as a UI issue only. Agents collect successfully.
FMS log shows an error similar to this:
2017-06-21 11:37:17.283 ERROR [http-exec-1948] org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/console].[Portal Servlet] - Servlet.service() for servlet [Portal Servlet] in context with path [/console] threw exception
java.lang.IllegalStateException: Error rendering part: rows in view: 'system:administration_agents_agenthost.agentHostsSummary' in top-level view: 'system:administration_agents_agenthost.agentManagers' for user: 'foglight'at com.quest.wcf.portal.components.MinimumComponent.renderFragment(MinimumComponent.java:110)
at com.quest.wcf.portal.impl.RequestProcessor.renderFragment(RequestProcessor.java:403)
at com.quest.wcf.portal.impl.RequestProcessor.process(RequestProcessor.java:229)
at com.quest.wcf.portal.impl.PortalServlet$1.run(PortalServlet.java:189)
at java.security.AccessController.doPrivileged(Native Method)
[...]
Caused by: java.lang.NullPointerException
[...]
2017-06-21 11:38:21.168 WARN [Data-3-thread-218] com.quest.nitro.service.agent.IncomingDataManager - Canonical data transform failed. Some agent data may be lost: java.lang.IllegalStateException: Error processing incoming data for node path: [FglAM::FglAM-Adapter-5_8_5_8/FglamPerformance-CDT-5_8_5_8/cdt.xml]/FglamClientPerformance: com.quest.nitro.service.topology.TopologyTypeNotFoundException: FglamClientInstance
[...]
This seems to be caused by missing FglamClientInstance Topology Type.
This can happen after an upgrade.
This can be resolved with a Reset of the FglAM-Adapter Cartridge.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center