Update failed with error: commit failed or was not attempted due to other errors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2021 12:05 PM
I am trying to discover Switch using pattern, but the discovery fails getting the error " Failed Exploring CI Pattern, Pattern name: Network Switch, To Check Pattern Log Press Here " I tried to debug and getting the expected out put from the pattern steps. This is not happening only specific Switches like N93180YC - FX Cisco. Please find the attached discovery error from pattern .
- Labels:
-
Discovery
- 4,380 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2022 07:43 AM
Please check logs of that ip address,
we have the same errors and when i checked the logs that ip address has duplicate Serial numbers. so you have to delete entire CI of that IP switch and before deleting export xml the record for safe side and check the Serial numbers if they are repeating check serial number and serial number type and re discover that IP and it should resolve.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2022 05:38 AM
I also have this error when discovering Routers. I looked into finding the existing record by CI, there was one there, exactly the same as what was in the discovery payload. Interestingly, the existing CI record shows that it's being updated by Discovery at the time that it errors out, so I haven't deleted the record. Would quite like to work out why it's complaining about not being able to update a record, or associate itself to the CI when it's clearly updating the correct target record.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2021 12:48 AM
I'm seeing this error in the "Amazon AWS S3" pattern too.
2021-11-22 02:10:45: Identifier: Identification CI Errors: Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error: Commit was not attempted due to other errors.,Update failed with error:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2021 11:31 AM
Out of interest, do you see anything in the system log or either of these tables at the time the commit fails? I came across them recently in a docs page and wondered if they contained anything useful when this fails...
cmdb_ire_incomplete_payloads
cmdb_ire_partial_payloads
Thanks,
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2022 02:44 AM
Hi Ragav,
Does your issue resolve, i have same issue in oracle db on unix pattern..?