Unable to Troubleshoot Discovery Identification Engine Error

[Nicholas Blanch]

Attempting to run discovery on an Oracle Exadata platform, we are receiving the following Identification Error:

----

2020-08-28 06:44:54: Identification Engine errors: See [code]<a href="/nav_to.do?uri=/$identificationLogs%3Fcontext_id%3D332c121b1b7a1c90a415c9522a4bcbc1" target="_blank"><u>Identification Logs</u></a>[/code] for more info.

Proposed solution:
In case the discovered CI is included CI (such as Tomcat WAR) check if there are multiple records with name 'Contains::Contained by' in cmdb_rel_type table.
Found multiple dependent relation items [{"parent":3,"child":0,"type":"Contains::Contained by"}] and [{"parent":1,"child":0,"type":"Contains::Contained by"}] in payload
Page number : 3/3

----

I've investigated Ref/Rel between cmdb_ci_memory_module and Linux CI in the discovery pattern, and have been unable to troubleshoot.  The IE logs have the following error:

1 : 2020-08-28 08:57:02 : Error : identification_engine : MULTIPLE_DEPENDENCIES Found multiple dependent relation items [{"parent":3,"child":0,"type":"Contains::Contained by"}] and [{"parent":1,"child":0,"type":"Contains::Contained by"}] in payload

9 : 2020-08-28 08:57:03 : Error : identification_engine : Detected error while processing payload from ServiceWatch
10 : 2020-08-28 08:57:03 : Error : identification_engine : Input = {"items":[{"className":"cmdb_ci_memory_module","values":...

Any troubleshooting help would be greatly appreciated!

[jcanjura]

Hi, 

Did you find a solution for this issue?
We're facing the same problem and I tried to completely delete the server CI (so no relationships in the picture) but now we can't re-discover the server due to this error.

Thanks
Juan

[jcanjura]

Hi, 

Did you find a solution for this issue?
We're facing the same problem and I tried to completely delete the server CI (so no relationships in the picture) but now we can't re-discover the server due to this error.

Thanks
Juan

[jcanjura]

I found a way to get more information about those errors.

Let's say this is the error:

----

2020-08-28 06:44:54: Identification Engine errors: See [code]<a href="/nav_to.do?uri=/$identificationLogs%3Fcontext_id%3D332c121b1b7a1c90a415c9522a4bcbc1" target="_blank"><u>Identification Logs</u></a>[/code] for more info.

Proposed solution:
In case the discovered CI is included CI (such as Tomcat WAR) check if there are multiple records with name 'Contains::Contained by' in cmdb_rel_type table.
Found multiple dependent relation items [{"parent":3,"child":0,"type":"Contains::Contained by"}] and [{"parent":1,"child":0,"type":"Contains::Contained by"}] in payload
Page number : 3/3

----

1. Get the SysID shown in the Horizontal Discovery log, in the example "332c121b1b7a1c90a415c9522a4bcbc1" (make sure you don't copy the "3D", that's part of the HTML format.

2. Go to System Log (System Logs > System Log > All)

3. Filter the log with "Source = Identification_engine" AND "Created on Today" (that will make the search quicker).

4. Search for that SysID in the "Message" field on the list (e.g. *332c121b1b7a1c90a415c9522a4bcbc1).

5. That will give you more information of the real issue, in my case was some duplicate CIs in the Memory Module table.

I hope this helps.

[Radu Pintilii1]

For anyone having this problem, check out this Knowledge article on HI: KB0860236

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0860236

This fixed it for me exactly for Oracle Exadata platform.

The offender was "OSs - Pre Sensor" - Pattern Pre/Post Script.

[peterdelf]

I'm seeing a similar error message in the Linux Server pattern -

Identification Engine Payload Sanitization

2022-07-15 06:54:18: : There is problem to build the Sanitized Payload: Identification Engine errors: See [code]<a href="/nav_to.do?uri=/$identificationLogs%3Fcontext_id%3D75f01b40977c55d48f2fb0771153af51" target="_blank"><u>Identification Logs</u></a>[/code] for more info.


	Proposed solution:
	In case the discovered CI is included CI (such as Tomcat WAR) check if there are multiple records with name 'Contains::Contained by' in cmdb_rel_type table.
Found multiple dependent relation items [{"parent":2,"child":0,"type":"Contains::Contained by","sys_rel_source_info":{}}] and [{"parent":1,"child":0,"type":"Contains::Contained by","sys_rel_source_info":{}}] in payload
 

I've imported the updated SA prescript record from KB0860236 but this has not made any difference.  I've also tried to sync patterns to MID servers and try again without success.