Watch4net: Collection of data from Smarts domains does not complete
search cancel

Watch4net: Collection of data from Smarts domains does not complete


Article ID: 307216


Updated On:





Watch4net collection of data from Smarts domains does not complete
The following entries seen in the Watch4net collecting log related to Smarts domain data collection:

INFO  -- [2013-04-03 15:23:46 BST] -- SmCollector::threadJob(): INCHARGE-AM-PM: starting polling...
WARNING  -- [2013-04-03 15:23:46 BST] -- SmDataIndicators::update(): INCHARGE-AM-PM: can't refresh class hierarchy for Smarts collector INCHARGE-AM-PM. Will retry later...
 at com.watch4net.smarts.SmUtils.tryAttach(
 at com.watch4net.smarts.SmUtils.attach(
 at com.watch4net.smarts.SmSafeRemoteBroker.attach(
 at com.watch4net.smarts.SmUtils.attach(
 at com.watch4net.apg.v2.collector.plugins.smarts.SmRemoteDmFactory.makeObject(
 at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(
 at com.watch4net.apg.v2.collector.plugins.smarts.SmTopologyManager.getRemoteDM(
 at com.watch4net.apg.v2.collector.plugins.smarts.SmTopologyManager.classExists(
 at com.watch4net.apg.v2.collector.plugins.smarts.SmDataIndicators.initializeStartClasses(
 at com.watch4net.apg.v2.collector.plugins.smarts.SmDataIndicators.update(
 at com.watch4net.apg.v2.collector.plugins.SmCollector.notifyListeners(
 at com.watch4net.apg.v2.collector.plugins.SmCollector.threadJob(
INFO  -- [2013-04-03 15:23:46 BST] -- SmPollingData::updateNextPollingDelay(): INCHARGE-AM-PM: polling completed in 0.0020s, next polling in 239.997s...

Watch4net cannot collect data from Smarts domains even though Watch4net Smarts collector configuration contains the FQDN of the Smarts broker host as in the following:



VMware Smart Assurance - SMARTS
VMware Smart Assurance - Watch4Net/M&R


In the error message above, "" indicates that the hostname configured for the Smarts broker host is invalid. If the configuration worked in the past but suddenly stopped, then there is most likely an issue resolving the name to an IP address either by DNS or with the entry in /etc/hosts.


If you encounter this issue, ensure the following:
  • The Smarts broker hostname is entered correctly in the Watch4net collector configuration. If you need to correct this entry in the configuration, you will need to restart the Watch4net Collector Manager for the change to take effect.
  • The hostname can be resolved to an IP address either by DNS or with an entry in /etc/hosts.