Highlighted
Absent Member.. Absent Member..
Absent Member..
435 views

Node is been populated in HP uCMDB 10.11 CUP 5.450 UD CP 14.05.317

Jump to solution

Hello,

i am experiencing issues when I run any discovery Job because the Nodes are not been populated. However, after running discovery jobs, the related host are been generated.

I have an HA environment.

Your help will be much appreciated

Please can someone advise or assist?

Some of the probe Erorr log below

2016-09-21 09:18:25,525> [ERROR] [JobExecuterWorker-29:Databases TCP Ports_10.4.56.40] (DynamicService.java:88) - DynamicService failed processing tables on destination: 10.4.56.40(ID=4627575c5a3aa4ddcf9a6a9534d23571)
java.lang.NullPointerException
at com.hp.ucmdb.discovery.library.execution.impl.JythonFactory.freePhytonInterpreter(JythonFactory.java:135)
at com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.finishExecution(ExecutionEngineImpl.java:89)
at com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:99)
at com.hp.ucmdb.discovery.probe.services.dynamic.core.TablesProcessorUtil.processDestinationTables(TablesProcessorUtil.java:136)
at com.hp.ucmdb.discovery.probe.services.dynamic.core.DynamicService.discover(DynamicService.java:76)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1202)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launch(JobExecuter.java:946)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:870)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:733)
<2016-09-21 09:18:25,853> [ERROR] [JobExecuterWorker-28:Databases TCP Ports_10.14.24.106] (DynamicService.java:88) - DynamicService failed processing tables on destination: 10.14.24.106(ID=f666b82c5d022a2de523bb1f3974f8d3)
java.lang.NullPointerException
at com.hp.ucmdb.discovery.library.execution.impl.JythonFactory.freePhytonInterpreter(JythonFactory.java:135)
at com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.finishExecution(ExecutionEngineImpl.java:89)
at com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:99)
at com.hp.ucmdb.discovery.probe.services.dynamic.core.TablesProcessorUtil.processDestinationTables(TablesProcessorUtil.java:136)

Regards

Chris

 

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Node is been populated in HP uCMDB 10.11 CUP 5.450 UD CP 14.05.317

Jump to solution

HP Solution that resolved this issue

In reconciliation logs found these lines:

Caused by: java.lang.RuntimeException: Failed to calculate attribute attribute: name [root_iconproperties] type [string] isFactory [true] isUserUpdated [false] size limit [100]

We have found a similar case where the same error messages and issue was occurring. ( QCIM1H91002: Failed to calculate attribute attribute: name [root_iconproperties] type [string] isFactory [true] isUserUpdated [false] size limit [100] within class...)

We changed the configuration_item class in URM and CM_CLASS-->which contained the line <Attribute-Qualifier name="CALCULATED_ATTRIBUTE" is-factory="false" /> to be in comments.

We tried to comment it out, and restarted the UCMDB server while stopping the reader server.

This seemed to have resolved the issue.

View solution in original post

0 Likes
1 Reply
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Node is been populated in HP uCMDB 10.11 CUP 5.450 UD CP 14.05.317

Jump to solution

HP Solution that resolved this issue

In reconciliation logs found these lines:

Caused by: java.lang.RuntimeException: Failed to calculate attribute attribute: name [root_iconproperties] type [string] isFactory [true] isUserUpdated [false] size limit [100]

We have found a similar case where the same error messages and issue was occurring. ( QCIM1H91002: Failed to calculate attribute attribute: name [root_iconproperties] type [string] isFactory [true] isUserUpdated [false] size limit [100] within class...)

We changed the configuration_item class in URM and CM_CLASS-->which contained the line <Attribute-Qualifier name="CALCULATED_ATTRIBUTE" is-factory="false" /> to be in comments.

We tried to comment it out, and restarted the UCMDB server while stopping the reader server.

This seemed to have resolved the issue.

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.