DX Infrastructure Manager

Expand all | Collapse all

Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

Jump to Best Answer
  • 1.  Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 10-19-2017 02:57 PM

    Hi team,

     

    When I am installing UIM, I throw the following error. 

     

    2017-10-19 12:02:42,288 DEBUG pds.PDSController:send:177 [Thread-63] - Sending 'nametoip' with sid: null, timeout: 30000
    2017-10-19 12:02:43,321 WARN probe.ProbeController:waitForResponse:240 [Thread-63] - nametoip failed: (80) Session error, Unable to open a client session for 10.112.7.19:48000: Connection refused: connect
    2017-10-19 12:02:45,835 DEBUG pds.PDSController:send:177 [Thread-63] - Sending 'nametoip' with sid: null, timeout: 30000
    2017-10-19 12:02:45,835 DEBUG pds.PDSController:send:180 [Thread-63] - Command 'nametoip' response retrieved.
    2017-10-19 12:02:45,851 INFO probe.ProbeController:waitForResponse:235 [Thread-63] - ip_address: 10.112.7.19
    2017-10-19 12:02:45,851 INFO probe.ProbeController:waitForResponse:236 [Thread-63] - port: 48000
    2017-10-19 12:02:45,851 INFO impl.UIMServerConfigureController:waitForProbeToRespondCommon:3198 [Thread-63] - 'controller' probe successfully responded.
    2017-10-19 12:02:45,851 INFO impl.UIMServerConfigureController:waitForProbeToRespondCommon:3193 [Thread-63] - Waiting for 'hub' probe to respond.
    2017-10-19 12:02:45,851 DEBUG pds.PDSController:send:177 [Thread-63] - Sending 'nametoip' with sid: null, timeout: 30000
    2017-10-19 12:02:45,851 DEBUG pds.PDSController:send:180 [Thread-63] - Command 'nametoip' response retrieved.
    2017-10-19 12:02:45,976 INFO probe.ProbeController:waitForResponse:235 [Thread-63] - ip_address: 10.112.7.19
    2017-10-19 12:02:45,976 INFO probe.ProbeController:waitForResponse:236 [Thread-63] - port: 48002
    2017-10-19 12:02:45,976 INFO impl.UIMServerConfigureController:waitForProbeToRespondCommon:3198 [Thread-63] - 'hub' probe successfully responded.
    2017-10-19 12:02:45,976 INFO impl.UIMServerConfigureController:waitForProbeToRespondCommon:3193 [Thread-63] - Waiting for 'distsrv' probe to respond.
    2017-10-19 12:02:45,976 DEBUG pds.PDSController:send:177 [Thread-63] - Sending 'nametoip' with sid: null, timeout: 30000
    2017-10-19 12:02:46,101 WARN probe.ProbeController:waitForResponse:240 [Thread-63] - nametoip failed: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = 'distsrv'
    2017-10-19 12:02:48,616 DEBUG pds.PDSController:send:177 [Thread-63] - Sending 'nametoip' with sid: null, timeout: 30000
    2017-10-19 12:02:48,616 WARN probe.ProbeController:waitForResponse:240 [Thread-63] - nametoip failed: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = 'distsrv'
    2017-10-19 12:02:51,116 DEBUG pds.PDSController:send:177 [Thread-63] - Sending 'nametoip' with sid: null, timeout: 30000
    2017-10-19 12:02:51,116 DEBUG pds.PDSController:send:180 [Thread-63] - Command 'nametoip' response retrieved.
    2017-10-19 12:02:51,241 INFO probe.ProbeController:waitForResponse:235 [Thread-63] - ip_address: 10.112.7.19
    2017-10-19 12:02:51,241 INFO probe.ProbeController:waitForResponse:236 [Thread-63] - port: 48007
    2017-10-19 12:02:51,241 INFO impl.UIMServerConfigureController:waitForProbeToRespondCommon:3198 [Thread-63] - 'distsrv' probe successfully responded.
    2017-10-19 12:02:51,241 INFO impl.UIMServerConfigureController:startupNMS:603 [Thread-63] - NMS probes ready for further configuration tasks.
    2017-10-19 12:02:51,241 INFO impl.UIMServerConfigureController:startupNMS:605 [Thread-63] - EXIT
    2017-10-19 12:02:51,241 INFO impl.UIMServerConfigureController:doConfigure_nmsStartup:530 [Thread-63] - Successful execution NMS startup.
    2017-10-19 12:02:51,241 INFO impl.UIMServerConfigureController:initNMSSecurity:3095 [Thread-63] - Initializing NMS security.
    2017-10-19 12:02:51,241 INFO security.NimInstallSecurity:initHubSecurityForUser:72 [Thread-63] - Retrieving hub_info.
    2017-10-19 12:02:51,241 DEBUG pds.PDSController:sendPDSWithAddr:133 [Thread-63] - Sending 'get_info' with sid: null, timeout: 60000
    2017-10-19 12:02:51,257 DEBUG pds.PDSController:sendPDSWithAddr:138 [Thread-63] - Command 'get_info' response retrieved.
    2017-10-19 12:02:51,257 INFO security.NimInstallSecurity:initHubSecurityForUser:74 [Thread-63] - Successfully retrieved hub info: PDS [ht={post_dropped=Element [buf=null, pds=null, tpds=null, type=1, value=0], lastrestart=Element [buf=null, pds=null, tpds=null, type=1, value=0], hubname=Element [buf=null, pds=null, tpds=null, type=7, value=BBUSPITBS01_hub], post_received=Element [buf=null, pds=null, tpds=null, type=1, value=0], sec_login_ok=Element [buf=null, pds=null, tpds=null, type=1, value=1], ssl_cipher=Element [buf=null, pds=null, tpds=null, type=7, value=DEFAULT], version=Element [buf=null, pds=null, tpds=null, type=7, value=7.80 [Build 7.80.3556, Jun 16 2015]], ssl_mode=Element [buf=null, pds=null, tpds=null, type=1, value=0], requests=Element [buf=null, pds=null, tpds=null, type=1, value=8], log_file=Element [buf=null, pds=null, tpds=null, type=7, value=hub.log], ispool=Element [buf=null, pds=null, tpds=null, type=7, value=yes], iNameThreads=Element [buf=null, pds=null, tpds=null, type=1, value=0], domain=Element [buf=null, pds=null, tpds=null, type=7, value=BBUSPITBS01_domain], license=Element [buf=null, pds=null, tpds=null, type=1, value=1], sec_ver=Element [buf=null, pds=null, tpds=null, type=1, value=0], expire=Element [buf=null, pds=null, tpds=null, type=1, value=1511064000], sessions=Element [buf=null, pds=null, tpds=PDS [ht={2=Element [buf=null, pds=PDS [ht={idle=Element [buf=null, pds=null, tpds=null, type=1, value=0], lastrequest=Element [buf=null, pds=null, tpds=null, type=7, value=12:02:51 PM 19 Oct 2017], address=Element [buf=null, pds=null, tpds=null, type=7, value=0.0.0.0/48002], state=Element [buf=null, pds=null, tpds=null, type=1, value=2], established=Element [buf=null, pds=null, tpds=null, type=7, value=12:02:44 PM 19 Oct 2017], type=Element [buf=null, pds=null, tpds=null, type=7, value=TCP]}], tpds=null, type=21, value=null], 1=Element [buf=null, pds=PDS [ht={idle=Element [buf=null, pds=null, tpds=null, type=1, value=4], lastrequest=Element [buf=null, pds=null, tpds=null, type=7, value=12:02:47 PM 19 Oct 2017], address=Element [buf=null, pds=null, tpds=null, type=7, value=10.112.7.19/50493], state=Element [buf=null, pds=null, tpds=null, type=1, value=2], established=Element [buf=null, pds=null, tpds=null, type=7, value=12:02:47 PM 19 Oct 2017], type=Element [buf=null, pds=null, tpds=null, type=7, value=TCP]}], tpds=null, type=21, value=null], 0=Element [buf=null, pds=PDS [ht={idle=Element [buf=null, pds=null, tpds=null, type=1, value=0], lastrequest=Element [buf=null, pds=null, tpds=null, type=7, value=12:02:51 PM 19 Oct 2017], address=Element [buf=null, pds=null, tpds=null, type=7, value=10.112.7.19/50506], state=Element [buf=null, pds=null, tpds=null, type=1, value=2], established=Element [buf=null, pds=null, tpds=null, type=7, value=12:02:51 PM 19 Oct 2017], type=Element [buf=null, pds=null, tpds=null, type=7, value=TCP]}], tpds=null, type=21, value=null]}], type=24, value=null], r_nns_records=Element [buf=null, pds=null, tpds=null, type=1, value=0], nrestarts=Element [buf=null, pds=null, tpds=null, type=1, value=0], uptime=Element [buf=null, pds=null, tpds=null, type=1, value=7], origin=Element [buf=null, pds=null, tpds=null, type=7, value=BBUSPITBS01_hub], post_sent=Element [buf=null, pds=null, tpds=null, type=1, value=0], sec_on=Element [buf=null, pds=null, tpds=null, type=1, value=1], hubaddr=Element [buf=null, pds=null, tpds=null, type=7, value=/BBUSPITBS01_domain/BBUSPITBS01_hub/BBUSPITBS01/hub], nns_records=Element [buf=null, pds=null, tpds=null, type=1, value=5], ldap=Element [buf=null, pds=null, tpds=null, type=7, value=no], sec_verify_failed=Element [buf=null, pds=null, tpds=null, type=1, value=0], hubip=Element [buf=null, pds=null, tpds=null, type=7, value=10.112.7.19], ldap_version=Element [buf=null, pds=null, tpds=null, type=7, value=1.22], sec_login_failed=Element [buf=null, pds=null, tpds=null, type=1, value=0], started=Element [buf=null, pds=null, tpds=null, type=1, value=1508428964], log_level=Element [buf=null, pds=null, tpds=null, type=1, value=0], sec_verify_ok=Element [buf=null, pds=null, tpds=null, type=1, value=0], tunnel=Element [buf=null, pds=null, tpds=null, type=7, value=no]}]

    ------------------------------------

    The host file has already been validated, and you have the following:

    10.112.7.19 BBUSPITBS01.bicentenariobu.com
    127.0.0.1 localhost
    ::1 localhost

    ---------------------------

    What can be?

    ---------------------------

    Thanks,

    Richard



  • 2.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 11-09-2017 11:09 AM

    Hello Richard_Briceno

    Is this problem already fixed?

    If yes, could you please mark as answered.

     

    Regards,



  • 3.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Broadcom Employee
    Posted 10-20-2017 09:07 AM

    Can you attach your uimserver_ia_install.log and uimserver_systemprerequisites.properties

    these would be located in:

    C:\tmp\ca_uim

    or /tmp



  • 4.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine
    Best Answer

    Posted 10-20-2017 05:17 AM

    Hi,

     

    I don't know the IP of the machines you're trying to install that on, but that message:

     

    10.112.7.19:48000: Connection refused: connect

     

    indicates the robot on 10.112.7.19 is not installed or not running. If it is, then a firewall or something is blocking the access.

     

    Which log it is exactly and what are you trying to do?



  • 5.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Broadcom Employee
    Posted 12-05-2017 08:28 AM

    I recently ran into this issue/same errors during an installation and the problem was caused by entering the wrong/changed password for the SA user.



  • 6.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 11-29-2017 03:13 PM

    Has this problem been fixed?  I am running into the same problem and would like to know how I can move forward.

     

    Thanks,

     

    RJ Jones



  • 7.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 11-29-2017 03:28 PM

    Hi Robert,

     

    My problem was for the Database user in the installation process. I was installing with a different SA user, and there were missing permissions on the new user.

    The customer finally decided to install with the SA user of BD.

    If you have a connection error I recommend you do the following:
    -Ping
    -Telnet
    If all is well, the telnet must answer you without problem. If you are using port 48000 by default, validate that there is no other application that occupies it.

    Tell me more about your mistake.

     

    Regards,

    Richard



  • 8.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 11-29-2017 04:03 PM

    Richard,

     

    Thanks for sharing that info.  Telnet and Ping is working fine between my hub and DB server.  I am able to create the DB during the initial phase of the install; but after about 37% the install times out.  After looking at another thread; I am thinking my issue is related to the UIM database connections to Sql 2014 not being supported over TLS 1.2 protocol.  I have asked the question over there as well, will hopefully get an answer soon.

     

    Thanks again for reaching out.

     

    Robert



  • 9.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 11-29-2017 04:12 PM

    Hi Robert,

     

    Are you using SA user or a different BD user?
    Did you check the CA UIM server host file?

     

    Regards,

    Richard



  • 10.  Re: Error Installation CA UIM 8.5.1 - Configuring probe Data_Engine

    Posted 11-29-2017 04:18 PM

    Hello there.

     

    We are using a user with SA permissions.  We also have the addresses for all the servers within our infrastructure (1 DB, 1 primary Hub and 2 secondary Hubs, 1 Portal) in the host file of every server just in case there is a DNS issue somewhere down the line.

     

    These are good questions; thanks for suggesting them.

     

    RJ