SIM to uCMDB integration job failing

Running uCMDB 10.32.  trying to populate SIM devices (enclousures).   Have the SM integration adapter setup.  The integration job fails.

What steps can i take to troubleshoot?  What error logs can I look at?

  • Verified Answer



    at first it is good to click on the job status error line and check what error is reported to the UCMDB UI. Once you know what is there, you may go to the DFP and check probe-error.log as well as the *fcmdb* logs. Eventually you can enable communication log for the adapter and if lucky you will have information there as well. 

    But until you give us some hints what is the error, nobody in the forum can help you.


    Petko Popadiyski

    Freelance Microfocus CMS UCMDB Consulting

  • This is the only error from the logs that I see.


    jvm 1    | <2018-12-13 10:46:22,477> 52477128 [ERROR] [JobExecuterWorker-0:DS_HP SIM Integration_HP Systems Insight Manager_169.10.22.164] ( - ErrorMsgCode: 27
    jvm 1  
    jvm 1    |  at
    jvm 1    |  at$BlockDataInputStream.readInt(
    jvm 1    |  at
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.remote.ProcessCommunicator.readInt(
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.remote.JobWorkerCommunicator.readAction(
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.remote.RemoteDiscoveryComponent.communicateRemoteProcess(
    jvm 1    |  at
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchTaskRemotely(
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchAndIsProbeRestarting(
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(
    jvm 1    |  at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$

  • Hi Terrence,

  exception most probably means lack of connection to the SIM server. The DFP is either trying to connect to unreachable endpoint, or the protocol choice of http/https is mistaken.