snmpcollector not starting after upgrade to 4.15 & 5.01 - Connections could not be acquired from the underlying database!
search cancel

snmpcollector not starting after upgrade to 4.15 & 5.01 - Connections could not be acquired from the underlying database!

book

Article ID: 414973

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

After upgrading from 4.13 to 4.15 and then to 5.01, the following errors are seen during testing:

[SnmpCollectorMainExecution, snmpcollector] Current working directory:C:\Nimsoft\probes\network\snmpcollector 
[SnmpCollectorMainExecution, snmpcollector] Exception thrown initializing database: Connections could not be acquired from the underlying database! 

Environment

  • DX UIM 20.4.x / 23.4.x
  • snmpcollector 4.13 / 4.14 / 4.15 / 5.01

Cause

  • snmpcollector setup section-> 'configVersion' setting

Resolution

We noticed that if the configVersion value in the snmpcollector.cfg is 501 (or any other value that does not reflect the current version, e.g. if the current version is 4.13, the value should be set to 413), before upgrading to a higher version, otherwise the upgrade will fail. 

This is caused by the following key in the snmpcollector.cfg: 

configVersion=501

Notice there is no dot/period in the configVersion value.

To fix the issue, adjust this key in the .cfg file to the matching-current version value, and then try to upgrade.

Keep in mind to ensure and preserve a correct upgrade path (if from 4.13 to 5.01, you need to upgrade from 4.13 -> to 4.14 -> and then to 4.15 and then 5.01)