Highlighted
New Member.
3797 views

HP uCMDB - Discovery warning during processing results

Hello,

I've been running the "Host Resources and Applications by WMI" package on uCMDB 9.05. There are quite a few warnings which I'm trying to understand. This could help me fix the issue and make sure the next run goes smooth.

Can someone share their expertise on the subject please.

<< Progress message, Severity: Warning>>
Warning during processing results: Bulk contains ignored CIs that were filtered by the probe. In order to resend all objects reported by this trigger CI, please clear jobs results cache. For details please check cmdb.reconciliation.log.

<< Progress message, Severity: Warning>>
Detected multiple updates in bulk - found attribute: service_operatingstatus on current CIT: windows_service with value: Running that is different from the existing value: Stopped - ignoring new value

Please find the attached cmdb.reconciliation.log

0 Likes
11 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: HP uCMDB - Discovery warning during processing results

It means, there are few CIs whcih are contradicting each other and hence being ignored by ucmdb.

This is the reason, why we are getting that error. It is indication to the ucmdb user that there are few CIs are not in the required format and with less information.

0 Likes
Highlighted
New Member.

Re: HP uCMDB - Discovery warning during processing results

Hi Bravi,

 

I appreciate your response.

 

I have two things in mind:

 

1: I thought clearing the probe cache before starting a discovery job would fix this, but it doesn't seem like it.

 

2: We're working with three probes right now and the IP-ranges between these probes are being moved constantly to balance the triggered CI count. So, do you think this could be a possible reason why we're seeing these warnings ?

 

Or, how would you go about solving this issue.

Kindly oblige.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: HP uCMDB - Discovery warning during processing results

Hi Bravi,

 

I am facing the same issue,If you got the solution kindly help to resolve this.

 

Thanks

Priyanka

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: HP uCMDB - Discovery warning during processing results

is there any exact solution about this??

0 Likes
Highlighted
New Member.

Re: HP uCMDB - Discovery warning during processing results

Hello,

 

It's been a while since I followed up on this thread. So a quick recap on the below warning;

<< Progress message, Severity: Warning>>
Warning during processing results: Bulk contains ignored CIs that were filtered by the probe. In order to resend all objects reported by this trigger CI, please clear jobs results cache. For details please check cmdb.reconciliation.log.

 

I feel we could fix the "Bulk Ignored CIs" warning by implementing the below mentioned setting.

 

Fail entire bulks due to invalid CIs: If a set of objects (for example, 1,000 objects) includes even one invalid CI (for example, a node cannot be identified because of missing topological information), the reconciliation engine drops the entire set and does not send it to the CMDB. This is the default behavior.

 

Solution:

Clear the check box to have the results sent to the CMDB with only the invalid CIs (and their topology) dropped from the results. In the above example, 999 objects would be processed. UCMDB displays an error message when you view the results.

 

i.e.,

 

1: Go to the job --> Edit Adapter --> Adapter Configuration tab --> Uncheck Fail entire bulks due to invalid CIs

2: Other thing that would help: Clear probe results cache: Go to the discovery job, deactivate it, right click and clear probe result cache and reactivate the job.

 

I've been doing the Option 2 quite often but it doesn't really seem to be solving a lot of such warnings. I'm still figuring out the possible downsides of implementing Option 1. Since we use Service Manager, I need to make sure that it doesn't affect anything.

 

Any thoughts on this theory will be much appreciated.

 

Thanks,

Praveen

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: HP uCMDB - Discovery warning during processing results

The option 1 is preferable. The only downside, that 999 CIs from the 1000 bulk will be sent one by one after the fuilure. It potentially will have performance implication, but it should be minor...

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Frequent Contributor.. Frequent Contributor..
Frequent Contributor..

Re: HP uCMDB - Discovery warning during processing results

Has one any got the solution for it.

<< Progress message, Severity: Error>>
Error processing results of discovery adapter, details Some Error occurred when processing Redundant results:
at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:322)
at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.handleResults(AbstractResultProcessRedundant.java:195)
at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant.internalDoProcess(ResultProcessDBRedundant.java:145)
at com.hp.ucmdb.discovery.library.results.resultprocess.AbstractResultProcessRedundant.doProcess(AbstractResultProcessRedundant.java:101)
at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcess.process(ResultProcess.java:23)
at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessChain.doProcess(ResultProcessChain.java:53)
at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResult(ResultSenderImpl.java:191)
at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResults(ResultSenderImpl.java:141)
at com.hp.ucmdb.discovery.probe.agents.probemgr.discoveryscheduler.ResultSenderImpl.processResults(ResultSenderImpl.java:119)
at com.hp.ucmdb.discovery.probe.services.dynamic.core.DynamicService.discover(DynamicService.java:83)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1206)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchAndIsProbeRestarting(JobExecuter.java:953)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:869)
at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:729)
Caused by: java.lang.Exception: Some Error occurred when save processing Redundant results
at com.hp.ucmdb.discovery.library.results.resultprocess.ResultProcessDBRedundant$UpdateResultsFilter.filterResultsBulk(ResultProcessDBRedundant.java:292)
... 13 more

 

0 Likes
Highlighted
Frequent Contributor.. Frequent Contributor..
Frequent Contributor..

Re: HP uCMDB - Discovery warning during processing results

Any update by anyone....

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: HP uCMDB - Discovery warning during processing results

Hi Praveen,

 

Thanks for the solutions as you said the clearing probe cache doesn't help in sortingout this issue so i went with the other option but for one job we can do this but in my environment i can see that in more than job. ALso that is not working in my environmnet i am getting the same error.

So did you get the permanent solution for this.If yes could you please share with us.

 

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: HP uCMDB - Discovery warning during processing results

Hello Dmitry.

Why would sending 999 CIs cause performance issues?

Is the bulk treated differently if not the complete set is sent? If the complete set (1000 CIs) was sent, would there be any performance issues?

Thank you.
Thodoros
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HP uCMDB - Discovery warning during processing results

@Theodore_x86 It is the way a batch is treated. You send 1000 CIs in one API call. If one of them however fails, the call is returned as not successful. Then the only way to find out which CI exactly is the problematic is to send them 1 by 1. This process takes significantly more time since you have the overhead of creating 1000 separate API calls instead of 1. 

Petko

Likes are appreciated!
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.