ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CABI installation is failing - UIM/UMP 20.1

book

Article ID: 188136

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After installing the bundled cabi on a new robot after upgrading UIM/UMP to 20.1, the cabi and wasp probes fail to start.  The only error that appears in the cabi.log file is:
Controller: Probe 'cabi' (command = <startup java>) returns no-restart code (42)

Cause

An older version of the cabi probe was installed on a different robot at one point in time.  This resulted in the creation of the cabi tables in the CA_UIM database which the 4.20 cabi installer detects.  This then prevents the cabi probe from installing the jaspersoft server and creating the cabijs webapp in the wasp on the CABI robot.

From the _cabi.log file the following indicates that the cabi probe detects that this is a new install:

Apr 05 12:50:13:425 [main, cabi] read from cfg: lastInstalledUimCabiBundleVersion=
Apr 05 12:50:13:425 [main, cabi] end getLastInstalledUimCabiBundleVersion(config=<not null>) return lastInstalledUimCabiBundleVersion=
Apr 05 12:50:13:432 [main, cabi] begin doesUimCabiBundleNeedsToBeUpgraded(lastVer=, cfgVer=7.1.1-u1)
Apr 05 12:50:13:432 [main, cabi] uim.cabi.bundle.version: at-least one out of lastVer= or cfgDdmVer=7.1.1-u1 is null or empty, so setting shdUpgrade=true
Apr 05 12:50:13:433 [main, cabi] end doesUimCabiBundleNeedsToBeUpgraded(lastVer=, cfgVer=7.1.1-u1) return shdUpgrade=true
Apr 05 12:50:13:433 [main, cabi] changing probe state from 'INITIALIZING' to 'INSTALLING_CABI'
Apr 05 12:50:13:434 [main, cabi] deleting the old cabi extracted dir: nimPath=/opt/nimsoft, dir=cabi
Apr 05 12:50:13:434 [main, cabi] begin deleteDirIfPresent(pathPrefix=/opt/nimsoft, dir=c)
Apr 05 12:50:13:434 [main, cabi] dirToDel=/opt/nimsoft/c
Apr 05 12:50:13:434 [main, cabi] deleting directory: /opt/nimsoft/c ... 
Apr 05 12:50:15:207 [main, cabi] ... done with deleting directory: /opt/nimsoft/c
Apr 05 12:50:15:208 [main, cabi] end deleteDirIfPresent(pathPrefix=/opt/nimsoft, dir=c) return isDeleted=true
Apr 05 12:50:15:208 [main, cabi] extracting cabi installer ...
Apr 05 12:53:31:377 [main, cabi] successfully extracted cabi installer at nimPath=/opt/nimsoft [time taken=3 minute(s) 16 second(s) (196169 ms)

But then when the probe checks the UIM database, it detects the the CABI tables have been previously installed:

Apr 05 12:53:31:415 [main, cabi] begin: checkIfTableExists() for table: jidashboard
Apr 05 12:53:31:415 [main, cabi] UimDBUtil normalizedProvideName=mysql
Apr 05 12:53:31:494 [main, cabi] end: checkIfTableExists() jidashboard : true
Apr 05 12:53:31:494 [main, cabi] begin: checkIfTableExists() for table: jiaccessevent
Apr 05 12:53:31:494 [main, cabi] UimDBUtil normalizedProvideName=mysql
Apr 05 12:53:31:502 [main, cabi] end: checkIfTableExists() jiaccessevent : true
Apr 05 12:53:31:503 [main, cabi] Results of check for existing JasperServer tables: isJIDashboardTblPresent=true isJIAccessEventTblPresent=true
Apr 05 12:53:31:503 [main, cabi] begin doCreateUpgradePropFileRequiredByCABIInstaller(cabiSchemaAlreadyInstalled=true)
Apr 05 12:53:31:503 [main, cabi] begin getCabiWebappVersion(cabiWebappDir=/opt/nimsoft/probes/service/wasp/webapps/cabijs)
Apr 05 12:53:31:503 [main, cabi] begin getCabiWebappVersion(cabiWebappDir=/opt/nimsoft/probes/service/wasp/webapps/cabijs) return version=null

This prevents the bundled cabi probe from completing the jaspersoft server install and cabijs wasp webapp configuration.

Environment

Release : 20.1

Component : UIM - CABI  4.20

Resolution

1.  Drop all of the CABI tables from the UIM database.  The database manager specific script with the SQL queries to drop these tables can be found in the <installPath>\nimsoft\probes\service\cabi\config\scripts\drop_tables\1.2\<db manager> directory on the CABI robot.  Make sure all 100 CABI tables are dropped from the CA_UIM database.  These tables consist of the following:

77 starting with ji%
11 starting with qrtz%
11 starting with quartz%
1  called profilingrecord

2.  Delete the cabi and wasp probes from the CABI robot
3.  Delete the cabi and wasp directories and their contents found under the <installPath>\Nimsoft\probes\service directory on the CABI robot
4.  Deploy the cabi probe to the CABI robot