Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..
229 views

CMDB Population - Redundant Process Fail

jvm 2    | <2016-11-02 21:16:26,071> 1748051639 [ERROR] [JobExecuterWorker-2:DS_Population Windows Element A Pop] (ResultProcessDBRedundant.java:321) - Some Error occurred when processing Redundant results:
jvm 2    | java.lang.NullPointerException
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.arePropertyValuesSame(ResultProcessDBRedundant.java:429)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.compareAttrsMaps(ResultProcessDBRedundant.java:411)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.checkVolatileAttrsAreSame(ResultProcessDBRedundant.java:404)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.handleSameIDAndHashWithDiffVolatileAttrs(ResultProcessDBRedundant.java:357)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.access$400(ResultProcessDBRedundant.java:45)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:262)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.handleResults(AbstractResultProcessRedundant.java:195)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.internalDoProcess(ResultProcessDBRedundant.java:145)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.doProcess(AbstractResultProcessRedundant.java:101)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcess.process(ResultProcess.java:23)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessChain.doProcess(ResultProcessChain.java:53)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResult(ResultSenderImpl.java:191)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResults(ResultSenderImpl.java:141)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.sendAndClearResults(AdapterService.java:682)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.sendAndClearChangesResults(AdapterService.java:520)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runPopulateChangesAdapter(AdapterService.java:1262)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runChangesOnPopulateChangesAdapter(AdapterService.java:1318)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runQueriesOnPopulateChangesAdapter(AdapterService.java:1137)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runQueries(AdapterService.java:354)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runDiscovery(AdapterService.java:198)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.discover(AdapterService.java:149)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1206)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchAndIsProbeRestarting(JobExecuter.java:953)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:869)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:729)
jvm 2    | <2016-11-02 21:16:26,075> 1748051643 [ERROR] [JobExecuterWorker-2:DS_Population Windows Element A Pop] (ResultSenderImpl.java:156) - Error processing results of discovery job DS_Population Windows Element A Pop
jvm 2    | Some Error occurred when processing Redundant results:
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:322)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.handleResults(AbstractResultProcessRedundant.java:195)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.internalDoProcess(ResultProcessDBRedundant.java:145)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.doProcess(AbstractResultProcessRedundant.java:101)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcess.process(ResultProcess.java:23)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessChain.doProcess(ResultProcessChain.java:53)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResult(ResultSenderImpl.java:191)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResults(ResultSenderImpl.java:141)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.sendAndClearResults(AdapterService.java:682)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.sendAndClearChangesResults(AdapterService.java:520)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runPopulateChangesAdapter(AdapterService.java:1262)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runChangesOnPopulateChangesAdapter(AdapterService.java:1318)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runQueriesOnPopulateChangesAdapter(AdapterService.java:1137)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runQueries(AdapterService.java:354)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runDiscovery(AdapterService.java:198)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.discover(AdapterService.java:149)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1206)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchAndIsProbeRestarting(JobExecuter.java:953)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:869)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:729)
jvm 2    | Caused by: java.lang.NullPointerException
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.arePropertyValuesSame(ResultProcessDBRedundant.java:429)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.compareAttrsMaps(ResultProcessDBRedundant.java:411)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.checkVolatileAttrsAreSame(ResultProcessDBRedundant.java:404)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.handleSameIDAndHashWithDiffVolatileAttrs(ResultProcessDBRedundant.java:357)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.access$400(ResultProcessDBRedundant.java:45)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:262)
jvm 2    | 	... 19 more
jvm 2    | <2016-11-02 21:16:26,079> 1748051647 [ERROR] [JobExecuterWorker-2:DS_Population Windows Element A Pop] (ResultSenderImpl.java:157) - Some Error occurred when processing Redundant results:
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:322)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.handleResults(AbstractResultProcessRedundant.java:195)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.internalDoProcess(ResultProcessDBRedundant.java:145)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.doProcess(AbstractResultProcessRedundant.java:101)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcess.process(ResultProcess.java:23)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessChain.doProcess(ResultProcessChain.java:53)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResult(ResultSenderImpl.java:191)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResults(ResultSenderImpl.java:141)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.sendAndClearResults(AdapterService.java:682)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.sendAndClearChangesResults(AdapterService.java:520)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runPopulateChangesAdapter(AdapterService.java:1262)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runChangesOnPopulateChangesAdapter(AdapterService.java:1318)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runQueriesOnPopulateChangesAdapter(AdapterService.java:1137)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runQueries(AdapterService.java:354)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runDiscovery(AdapterService.java:198)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.discover(AdapterService.java:149)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1206)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchAndIsProbeRestarting(JobExecuter.java:953)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:869)
jvm 2    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:729)
jvm 2    | Caused by: java.lang.NullPointerException
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.arePropertyValuesSame(ResultProcessDBRedundant.java:429)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.compareAttrsMaps(ResultProcessDBRedundant.java:411)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.checkVolatileAttrsAreSame(ResultProcessDBRedundant.java:404)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.handleSameIDAndHashWithDiffVolatileAttrs(ResultProcessDBRedundant.java:357)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.access$400(ResultProcessDBRedundant.java:45)
jvm 2    | 	at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:262)

A couple of my population job are failing with the above error message. The error didn't say much more as to why it fail or which Ci it fail on. Anyway to resolve this as it just making the jobs failed.

 

Thank you,

0 Likes
7 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CMDB Population - Redundant Process Fail

Hello,

Would it be possible to attached the probe-error.log please?

Thanks,

MICRO FOCUS Software Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Please hit the Kudo botton, if you find this post useful.
0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: CMDB Population - Redundant Process Fail

There isn't anything in the probe-error log beside the error below. 

<2016-11-01 21:42:56,637> [ERROR] [JobExecuterWorker-2:DS_Population DM to PM_Level 1 Windows Pop] (ProcessIPTypeStamperHandler.java:52) - Failed updating IP tag
java.lang.NullPointerException

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CMDB Population - Redundant Process Fail

Hello Ctruong,

This is a known issue recently reported. Do you use 10.30? Please open a support case and ask for a fix.

Best Regards,
Nikola

------------------------
Nikola Todorov
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: CMDB Population - Redundant Process Fail

We are not on 10.30.

We are on 10.22 CUP  Cp 20.

 

Can you please link me to the KM for this issue.

Thank you,

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: CMDB Population - Redundant Process Fail

Hello,

can I ask why you opted for population and not push?

As we saw before, push integration performs better and it's more stable.

Was this tested in parallel on your env?

Kind regards,

Bogdan

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: CMDB Population - Redundant Process Fail

Population allow us to set reconciliation priority on several node. With the push we can't control reconciliation priority.

Populaion was also alot more stable for us during our initial test. Push worked well for job that are below 300k-400k.

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: CMDB Population - Redundant Process Fail

Any Advice on how to troubleshoot this? I would this go away one day then come back the next. Sometime when I do full push after the failure it would go through and sometime it would fail with the same error. 

The only error I see is 

(ProcessIPTypeStamperHandler.java:52) - Failed updating IP tag

What does this error mean anyway? 

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.