DX Infrastructure Management

 View Only

TEC TIP: cabi probe v3.0 deployment problems 

Aug 25, 2017 11:09 AM

Summary:

New deployment of the cabi probe (v3.0). The probe appeared to deploy successfully however, it didn’t extract any files or even attempt the jaspersoft installation. The cabi wasp probe also does not start and is in an error state (no port or pid). Also, no /c/ folder or tables in db, cabi dashboards not working in the UMP - cabi probe log file: 

 

Aug 21 17:59:27:032 [main, cabi] Login to NimBUS is OK 

Aug 21 17:59:27:032 [main, cabi] cabi is configured in inactive mode. 

Aug 21 17:59:27:032 [main, cabi] Changing probe state from 'INITIALIZING' to 'INACTIVE' 

Aug 21 17:59:27:032 [main, cabi] cabi_mode is inactive, probe will run but will not be active 

Aug 21 18:02:26:916 [attach_socket, cabi] changed the account name to be same as default organization; accountName=UIM 

Aug 21 18:02:26:916 [attach_socket, cabi] Error: Probe.cbEnsureUserExists - userSynchronizer was null 

 

Environment:

  • UIM 8.51
  • cabi probe v3.0
  • cabi robot 7.80
  • cabi wasp 8.51
  • SQL Server (using sa user in data_engine)

 

Instructions:

  1. Uninstall the cabi wasp probe:
  • If cabi is installed on a separate robot:

- delete wasp probe from IM or Admin Console

- delete directory C:\Program Files (x86)\Nimsoft\probes\service\wasp (on the cabi robot)

 

  • If cabi is installed along with UMP or UIM server:

- delete the cabijs app in wasp probe through probe utility.

 

  1. cabi probe:
  • deactivate the cabi probe from IM or Admin Console (do not delete it)
  • login to your database server and copy and execute commands specified at the following path:

- C:\Program Files (x86)\Nimsoft\probes\service\cabi\config\scripts\drop_tables\1.2\sqlserver (assuming sql server db)

  • Make sure that all script commands are run successfully.
  • Delete the cabi probe from IM or Admin Console

 

  1. cabi robot:
  • delete directory: C:\Program Files (x86)\Nimsoft\probes\service\cabi
  • delete C:\Program Files (x86)\Nimsoft\c

 

  1. Re-install cabi 3.0.0 probe:
  • Drag and drop cabi 3.0.0 and the latest version of uim_core_dashboards_pack onto the robot
  • Once it is green then go to Raw Configure and change the cabi_mode value to bundled. This triggers cabi installation; wait for the installation to complete.
  • Ensure the ump_cabi v3.0 package is deployed to the ump wasp robot.

 

Additional information:

Install or Upgrade for a Bundled CA Business Intelligence JasperReports Server - https://docops.ca.com/ca-unified-infrastructure-management/8-5-1/en/installing-ca-uim/ca-business-intelligence-with-ca-uim/installing-and-upgrading-ca-business-intelligence-jasperreports-server-with-ca-uim/install-or-upgrade-for-a-bundled-ca-business-intelligence-jasperreports-server

Statistics
0 Favorited
15 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Sep 26, 2017 05:07 AM

Hi Ashok,

 

Thanks for the update. The difference in my ticket might of been the customer attempting the install multiple times, the steps you mentioned were tried before completely cleaning out CABI and starting from scratch.

 

Kind regards, 

Ryan 

Sep 26, 2017 05:00 AM

Hi Ryan,

 

Yes, i was able to access CABI Home page directly and through UMP as well. Verified in local environment and also for one of the customer.

 

Thanks,
Ashok

Sep 26, 2017 04:32 AM

Hi Ashok, 

 

This sounds very similar to problem we faced, when you say "changed the cabi_mode to active then clicked on Apply. So probe got restarted and it started extracting the files and it was working fine." did this resolve the problem and allow you to access the cabijs web console and CABI dashboards? 

 

Kind regards, 
Ryan 

Sep 26, 2017 12:03 AM

Hi Ryan,

I have seen the below message for few customers when i tried to deploy the cabi version 3.00. So i have opened the CABI probe Raw configure and changed the cabi_mode to active then clicked on Apply. So probe got restarted and it started extracting the files and it was working fine.

[main, cabi] cabi_mode is inactive, probe will run but will not be active

 

Followed by deploying the packages (uim_core_dashboards_pack etc.) from archive.

 

Does these steps only for the error "cabi] Error: Probe.cbEnsureUserExists - userSynchronizer was null" ? or we need to follow them for "[main, cabi] cabi_mode is inactive, probe will run but will not be active" message also ?

 

Thanks,

Ashok

Related Entries and Links

No Related Resource entered.