Resolving Data Collectors connections issues - Linux specific
Perform the following steps to resolves the data connections issues:
Verify that the tomcat-agent and apache services are running on the portal.
Verify that the key file is generated when the data collector was created.
On the portal, perform wget to the URL of the data receiver. The expected response is:
Index.htmlfile.Note:
This step bypasses the network and validates that the data receiver is up and running.
On the data collector, verify that the data receiver URL resolves via NSLOOKUP. If not then specify the data receiver IP address and name to the data collector's host file.
Verify using wget from the data collector that a response back, index.html page, is received. If not then ,verify if the firewall is blocking the access to port 80/443, depending upon configurations.
Execute the command ../mbs/bin/updateconfig. The expected response is: quick return to the command prompt. If not then: verify that the /opt/aptare/datarcvrconf/collectorConfig.global.properties on the portal has the correct URL.
Execute the checkinstall. If there is initial communication but errors, confirm the data collector name, passcode, and URL are correct.
Examine the
<Data Collector home>/mbs/conf/collector.propertiesfile and verify that the collector name, collector password, and URL were specified appropriately during the installation.Verify that the collector service is started, and Watchdog is running.
Ensure the understanding that if the portal is running a later upgrade than the GA data collector that upgrade will initiate right after DC connects, and the data collector will go offline for a period during the upgrade.