VMware Cloud Community
ScottyB_hyperic
Contributor
Contributor

Hyperic Agent - Platform not appearing in autodiscovery

Hi,

I have two identical windows servers both of which I have installed a Hyperic agent (4.4.0)

Both installed successfully
The first one appeared in the Autodiscovery on the server.
The 2nd one didn't
I can see no reason why the 2nd would not appear.

I restarted the agent, also uninstalled and re-installed it - no joy.

The only difference I see is in the agent.log

Both appear to kick off a "ConfigPopulateThread" thread

but the non autodiscovered one seems to stop there - whereas the successfully registered one logs successful registers

Please see below

SUCCESSFULLY Autodiscovered

2011-12-23 09:07:55,717 INFO [Thread-0] [MeasurementCommandsServer] Registering Measurement Commands Service with Agent Transport
2011-12-23 09:07:55,780 INFO [Thread-0] [MeasurementCommandsServer] Measurement Commands Server started up
2011-12-23 09:07:55,780 INFO [Thread-2] [ConfigPopulateThread] Starting config populate thread
2011-12-23 09:07:55,795 INFO [Thread-0] [LiveDataCommandsServer] Registering Live Data Commands Service with Agent Transport
2011-12-23 09:07:55,795 INFO [Thread-0] [LiveDataCommandsServer] Live Data Commands Server started up
2011-12-23 09:07:55,795 INFO [Thread-0] [AgentTransportLifecycleImpl] Agent is not using new transport.
2011-12-23 09:07:55,967 INFO [Thread-0] [AgentDaemon] Agent started successfully
2011-12-23 09:07:55,967 INFO [WrapperStartStopAppMain] [AgentConnection] 127.0.0.1:2144 -> agent:ping
2011-12-23 09:07:56,264 INFO [WrapperStartStopAppMain] [AgentConnection] 127.0.0.1:2144 -> bizapp:getCAMServer
2011-12-23 09:07:56,467 INFO [main] [AgentConnection] 127.0.0.1:2144 -> bizapp:getCAMServer
2011-12-23 09:07:56,514 INFO [Thread-2] [ConfigPopulateThread] Received measurement configuration for Win32 '1:10017'
2011-12-23 09:07:56,514 INFO [Thread-2] [ConfigPopulateThread] Creating config track plugin 1:10017
2011-12-23 09:07:56,514 INFO [Thread-2] [ConfigTrackPlugin] init file watcher for: 1:10017
2011-12-23 09:07:56,514 INFO [Thread-2] [ConfigPopulateThread] Creating log track plugin 1:10017
2011-12-23 09:07:56,545 INFO [Thread-2] [RunnableTrackThread] RunnableLogThread started
2011-12-23 09:07:56,545 INFO [Thread-2] [ConfigPopulateThread] Received measurement configuration for FileServer File '3:15500'
2011-12-23 09:07:56,545 INFO [Thread-2] [ConfigPopulateThread] Creating log track plugin 3:15500
2011-12-23 09:07:56,670 INFO [Thread-2] [ConfigPopulateThread] Received measurement configuration for FileServer File '3:15500'
2011-12-23 09:07:56,670 INFO [Thread-2] [ConfigPopulateThread] Creating log track plugin 3:15500
2011-12-23 09:07:56,686 ERROR [Thread-2] [ConfigPopulateThread] Unable to create plugin: 3:15500 'FileServer File':Plugin name=3:15500 already exists
org.hyperic.hq.product.PluginExistsException: Plugin name=3:15500 already exists
at org.hyperic.hq.product.PluginManager.registerPlugin(PluginManager.java:354)
at org.hyperic.hq.product.PluginManager.createPlugin(PluginManager.java:435)
at org.hyperic.hq.product.PluginManager.createPlugin(PluginManager.java:407)
at org.hyperic.hq.measurement.agent.server.ConfigPopulateThread.run(ConfigPopulateThread.java:130)
2011-12-23 09:08:01,420 INFO [ScheduleThread] [CollectorThread] CollectorThread started
2011-12-23 09:08:40,060 INFO [Thread-1] [AutoinventoryCommandsServer] Autoinventory report successfully sent to server.

UNSUCCESSFULLY Autodiscovered

2011-12-23 09:06:22,140 INFO [Thread-0] [MeasurementCommandsServer] Registering Measurement Commands Service with Agent Transport
2011-12-23 09:06:22,140 INFO [Thread-0] [MeasurementCommandsServer] Measurement Commands Server started up
2011-12-23 09:06:22,140 INFO [Thread-2] [ConfigPopulateThread] Starting config populate thread
2011-12-23 09:06:22,156 INFO [Thread-0] [LiveDataCommandsServer] Registering Live Data Commands Service with Agent Transport
2011-12-23 09:06:22,156 INFO [Thread-0] [LiveDataCommandsServer] Live Data Commands Server started up
2011-12-23 09:06:22,156 INFO [Thread-0] [AgentTransportLifecycleImpl] Agent is not using new transport.
2011-12-23 09:06:22,296 INFO [Thread-0] [AgentDaemon] Agent started successfully
2011-12-23 09:06:22,296 INFO [WrapperStartStopAppMain] [AgentConnection] 127.0.0.1:2144 -> agent:ping
2011-12-23 09:06:22,578 INFO [WrapperStartStopAppMain] [AgentConnection] 127.0.0.1:2144 -> bizapp:getCAMServer
2011-12-23 09:06:22,765 INFO [main] [AgentConnection] 127.0.0.1:2144 -> bizapp:getCAMServer
end of log

Any ideas ?
Firewalls appear to have been setup correctly for both
Can I kick off the auto discover manually apart from just restarting the agent ?

Cheers
ScottyB
0 Kudos
1 Reply
ScottyB_hyperic
Contributor
Contributor

Never fear - the Magic Pixies visited over the Christmas break.

The server appeared at sometime on the auto-discovered list.

The agent.log still does the same thing when restarted though - so if anyone has any insight on that - it would be much appreciated.

Cheers,
ScottyB
0 Kudos