Tech Tip - After deployment, Tomcat probe doesn't show up in IM, neither in Admin Console.

Document created by David.Moya Employee on Oct 26, 2016Last modified by SamCreek on Dec 19, 2016
Version 4Show Document
  • View in full screen mode

After deployment of the tomcat probe to a robot installed in a Solaris OS, the probe doesn't show up in IM, neither in Admin Console. This same behavior was experienced also with the jboss probe, however, other probes like the zones probe could be successfully deployed, and it showed up in the AC and IM consoles.


In controller.log, you can find error messages like: 

 Oct 19 16:37:43:101 [0001] Controller: MyStringExpand (rm "probes/application/jboss/jar/nimsoft.jar" "probes/application/jboss/jar/nimsoft-eb-jsr160.jar" "probes/application/jboss/jar/Twofish.jar")... 

Oct 19 16:37:43:103 [0001] Controller: Pre-install command rm "probes/application/jboss/jar/nimsoft.jar" "probes/application/jboss/jar/nimsoft-eb-jsr160.jar" "probes/application/jboss/jar/Twofish.jar" returned 512 exited with 2 

Oct 19 16:37:43:104 [0001] Controller: inst_execute - pre-install failure; installation of section SOLARIS in package tomcat aborted 

Oct 19 16:37:43:104 [0001] Controller: SREPLY: status = 7(temporarily out of resources) ->192.***.***.xx/59430 


and in distsrv.log: 


Oct 19 07:02:32:939 [6684] distsrv: unzip - zipfile not found for C:\Program Files (x86)\Nimsoft/archive/ 

Oct 19 07:02:33:124 [6684] distsrv: Dependency check error: Unable to find any version of package jre_solaris on /domain/hub/unknown 



jre_solaris was installed in the system.

CA UIM 8.47 + Solaris 10

Defined probe pre-requisites were preventing a successfully install of the probe in the robot.