Discovery Schedule for Data Center Devices Not Completing After Yokohama Upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2025 01:45 AM
Hi everyone,
We recently upgraded to the Yokohama release and have encountered an issue with one of our Discovery Schedules targeting data center devices. The schedule starts as expected and the IP ranges are correctly configured, but the discovery process cancels near the end of the run.
Upon reviewing the logs and device statuses, we noticed that the devices which do not complete have their current activity stuck at "Updating CI". This behavior is new since the upgrade, and we haven't made any changes to the probes or patterns involved.
Has anyone else experienced similar behavior after upgrading to Yokohama? Any insights or suggestions would be greatly appreciated.
Thanks in advance!
- Labels:
-
Data Health Tools
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-05-2025 06:58 AM
Hi Dawn
The "threads.max" value on our side is already at 200, can you advise on the value you are using on your side?
Kind Regards
Kabelo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2025 01:54 AM
Hi Kabelo
Ours had defaulted to 25, so we changed it back to 100, which works quite well for us. We also added a credentialalias to the schedule . If your scheduled scans are still failing, have you considered making the ranges smaller to test? Perhaps a 50 ip schedule and check if that completes?
