Reports showing no data after migrating data collector from RHEL6 to RHEL7
The following errors can be seen within the Data Collector's /opt/IMDataCollector/apache*/data/log/karaf.log:
ERROR | eadpool-thread-5 | 2019-09-05 17:34:43,838 | DCMRegistrationManager | ller.impl.DCMRegistrationManager 238 | ager.core.collector.impl | | Exiting out of registration because we encountered an error while trying to register this collector with the DA: collectorID = xxxxxx:a4834bb7-c3c3-4abf-9060-3fd68f8302e2 tenantItemID = 1 ipDomainID = Default Domain ipDomainItemID = 2 dcVersion = 126.96.36.1993 INFO | adpool-thread-47 | 2019-09-05 17:34:48,863 | DCMRegistrationManager | ller.impl.DCMRegistrationManager 230 | ager.core.collector.impl | | onRegistration: collectorID = xxxxxx:a4834bb7-c3c3-4abf-9060-3fd68f8302e2 tenantItemID = 1 ipDomainID = Default Domain ipDomainItemID = 2 dcVersion = 188.8.131.523 ERROR | adpool-thread-47 | 2019-09-05 17:34:48,876 | DCMRegistrationManager | ller.impl.DCMRegistrationManager 559 | ager.core.collector.impl | | The Data Collector is currently monitoring 1092 devices and cannot be re-assigned: xxxxxx:a4834bb7-c3c3-4abf-9060-3fd68f8302e2
This is likely due to the prior Data Collector still being registered to the Data Aggregator so the new version of it is unable to register and continue.
Release : 3.7
Component : IM Reporting / Admin / Configuration
1. Stop activemq and dcmd on all affected Data Collectors
2. Stop activemq and dadaemon on the Data Aggregator
3. Start dadaemon on the Data Aggregator
4. Start dcmd on each Data Collector, one by one, while monitoring /opt/IMDataAggregator/apache*/data/log/karaf.log to ensure the Data Collector successfully registers before moving onto the next one if there is more than one.