"Check For Output Payload Errors" step produces "Insertion failed with error"

[Matthew Eames]

Hi,

we have a 10 node Windows cluster. Pattern Launcher: Windows OS - Servers is kicked off for each node but the pattern fails on all nodes - payload processing fails on the Check For Output Payload Errors step, producing the following repetitive output "Insertion failed with error,". 

thanks in advance

Matt

[Rahul Priyadars]

So its failing for even 1 Windows Server. Is its happening only for the set of 10 Windows Node or Other Windows Node also?

You can try running the pattern in Debug Mode and see if it helps?

Regards

RP

[SiD2]

Hi @Matthew Eames,

Not sure of why the indices removed, but you can check for the detailed error code from IRE as here it doesn't provide much details.

There can be a chance that this issue you see might not be related to indices removal, so you can try below approach for getting more details on the error.

Use "Identification Simulation" in your instance with existing payload option to check the detailed error description. You can get the payload from the pre sensor script or can use the ecc queue input entry for the pattern execution.

Please mark the appropriate responses as Correct/Helpful so that this thread gets closed and helps others with the same question in the future.

[Ashutosh Munot1 · Accepted solution]

Hi,

I would say that there are duplicate relationship for this CI for same CI. So delete the relationships for this CI and re-discover this.

Thanks,
Ashutosh

[Matthew Eames]

Thanks Ashutosh, that was indeed the answer. The amount of duplicate relationships was excessive, and, given the number of nodes on the cluster creating a large input payload, this had the knock on effect of filling the available error buffer in the Horizontal Discovery Log with repetitive error "Insertion failed..." for each relationship and preventing getting to any log detail to determine what the root cause was.

That root cause was eventually identified from MULTI_MATCH errors in the log, but we only got there after adding the system property "glide.cmdb.logger.source.identification_engine" with the type "string" and value of "debugVerbose" and checking the "syslog" table with "Source" = "identification_engine". 

Caveat for anyone doing this, verbose is VERY verbose, remove this property ASAP after debugging or your identifications will spam your logs.

thanks

Matt

[pratiksha5]

What do you mean by deleting the relations?