CA UIM snmpcollector probe not starting after install/upgrade

Document ID : KB000009314
Last Modified Date : 10/08/2018
Show Technical Document Details

snmpcollector not starting after install/upgrade

Error in snmpcollector.log shows:

Feb 01 10:42:44:718 [SnmpCollectorMainExecution, snmpcollector] Exception thrown initializing database: Connections could not be acquired from the underlying database!
Feb 01 10:42:44:719 [SnmpCollectorMainExecution, snmpcollector] stderr: Exception in thread "SnmpCollectorMainExecution"
Feb 01 10:42:44:720 [SnmpCollectorMainExecution, snmpcollector] stderr: java.lang.NoClassDefFoundError: Could not initialize class

- UIM 8.5.1- snmpcollector 3.43 or 3.44

This issue appears to be caused by

- internal database too busy to respond.
- corruption of internal database ( file.


Note :  We strongly encourage that you use snmpcollector probe latest hotfix available.

The latest hotfix can be found here.

The resolution is to perform the following steps:

1. Open snmpcollector in Raw Configure, add the below key to <setup> section and check if probe is started.


2. If above does not help, search any recent backups of taken. If you have,
deactivate probe, replace it with your backup, and start the probe.

3. If above does not help, deactivate probe and move the following files out of the snmpcollector probe directory:

   - all* files

Note that if you made any changes to the User defined property 1 fields of ifSpeeds, this info will be lost. Note also that by deleting the file, you will lose anything that was manually added, e.g., profiles were not pulled in through the discovery_server as well as any/all "User defined property 1" values you added at the device and component level.

4. Activate the snmpcollector probe

5. Query the discovery_server for the devices to monitor. Note that you may have to delete and re-enter the discovery_server info in the Discovery Filter before you rediscover all of your profiles. If profiles were manually added before, they will have to be manually added again.

6. snmpcollector should be working as expected now and respond properly to a restart or cold start. Check the logs after completing the above steps.

Additional Information:

Providing information to CA UIM Support:

- If you have backups of the snmpcollector files before the upgrade and currently (where it is corrupted), we can provide them to dev to try and find out why the install/upgrade is corrupting the file(s), so please attach the* files to the support case you opened.