Discovery ecc_queue inputs may remain stuck in ready state for different root causes.
KB0749610 ECC Queue Input records remain on "ready" state, and Discovery never completes - insertion to discovery_device_duplicate_ips or sys_mutex fails due to Unique Key violation
KB0722882 Discovering devices with multiple IP addresses in the same Discovery schedule causes it to time out
Steps to Reproduce
- Create a Discovery schedule to discover a device that has multiple IP addresses.
- Create "IP Range" and "Range sets" which discovers the IPs for the device, in order to trigger the discovery of the IP addresses on the device twice.
- Run a discovery.
- Open the stuck discovery status.
- Find the input stuck in state "Ready".
- Open table discovery_device_duplicate_ips
- Find the relevant record by source, use the IP address.
- Now that we have the discovery_device_duplicate_ips, make note of the CMDB CI.
- Use the CMDB CI now to filter discovery_device_duplicate_ips based on the CI and the discovery status.
- The new filter on discovery_device_duplicate_ips, using CMDB CI and discovery status number, will show all the IPs for this device on the discovery.
- There should only be one entry per IP address/Discovery Status.
- Make note of the duplicates. Navigate to the discovery schedule find the "IP Ranges" and "Range Sets" triggering discovery of the IP address.
- Update the "IP Ranges" and "Range Sets" accordingly to ensure that the discovery of the IP address is only triggered via either an "IP Range" or "Range Set".
Related Problem: PRB1370895