CABI 4.10 install problems on 9.20

[Sam Green]

Hi community,

Does anyone have any experience of installation problems on a 9.20 build with CABI 4.10?

My environment is running on RHEL 7.8, with MySQL 5.6

I've done a full clean up several times (removing probes, running drop tables script etc), but it fails during installation.

I have a support ticket open, but just thought I'd throw it out there in case anyone has encountered similar issues.

CABI log attached.

Cheers!

------------------------------
CA - UIM administrator
------------------------------

Attachment(s)

CABI - 5th Failure.txt   22 KB 1 version

[Christopher Pearson]

As a general rule for install for bundled (what are you using):

-install wasp first
-copy over the certificate.pem and update robot with location and restart
-set data_engine path in wasp
-start wasp and verify port and pid
-install cabi probe

[Sam Green]

Thanks for getting back to me, I've tried it but the wasp fails to start..

"Max restarts reached for probe 'wasp' (command = <startup java>)

------------------------------
CA - UIM administrator
------------------------------

[Gene Howard]

this usually means the robot is not on 7.96 or higher.
or the pem file is not setup or correct so the wasp probe can not get the data_engine connection string.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Sam Green]

Thanks Gene,

The Robot is 9.20, I copied the pem file from the PHub to the Cabi Server, updated the cabi robot.cfg with the location and restarted the nimbus service..​

------------------------------
CA - UIM administrator
------------------------------

[Christopher Pearson]

-open the wasp configuration on your UMP machine
-copy the data_engine path from that to the wasp's configuration on the cabi machine

[Sam Green]

Hi Christopher,

That's what I did to avoid any typo's/mistakes :)

------------------------------
CA - UIM administrator
------------------------------

[Gene Howard]

set your wasp loglevel to 5 and logsize to 35000 and restart the robot.
Check the _wasp.log for errors

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Sam Green]

Thanks Gene,

Done that, although I don't understand why it's failing..

I'll attach the log in case you can see something in there.

Cheers,
Sam

------------------------------
CA - UIM administrator
------------------------------

Attachment(s)

WASP_Failure.txt   8 KB 1 version

[Gene Howard]

is this the _wasp.log or the wasp.log?

It looks like there might be a problem with the java jdbc driver.
Did you check the java version as root.
Make sure there is no other version installed in the path?
Also, try redeploying the java JRE and compare the files in the directory to the ones on the primary or ump.

Also did you make the following changes to your MYSQL installation?

MySQL Only

) If you are using MySQL for your CA UIM database, change the following default settings for your MySQL database so that the CA Business Intelligence dashboard deployment is successful:

• Set 

  max_allowed_packet=500M

   
• Set 

  innodb_log_file_size=356M

   
• Set

   table_definition_cache=2000

   

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Sam Green]

Hi Gene,

This was eventually worked out with support, KB article here for anyone else having issues:

https://knowledge.broadcom.com/external/article?articleId=194387


------------------------------
CA - UIM administrator
------------------------------

[Andrew Cooper]

I know it is linux but the cryptkey entry in the robot.cfg cannot have spaces in the path

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------