Discovery schedule status sits in 'Active' state - doesnot mark 'Completed'

anish_kanchan
Kilo Explorer

We have recently deployed discovery, in our Geneva version instance.

We are able to successfully run discovery schedule and discover all required CIs

The only issue we are facing is - Discovery schedule status does not gets marked as 'Completed' rather sits there in Active status even after completing discovering all the defined rages.

The 'Completed' field also displays '0' count.

find_real_file.png

How can I say that the discovery is functioning as expected? - All the required CI are getting discovered as the provide ranges. Also the individual statues display the correct count. For eg. below is one of created CI status the started and completed count match and marks state as completed.

find_real_file.png

Can you please help me identify why is this issue? doug.schulze glenn.pinto ctomasi

5 REPLIES 5

petertjeerdsma
Kilo Contributor

Hi,



Look at the ECC queue and see if any records are still in the state of processing. We suffered this issue with the Unix Uptime probe after upgrading to Helsinki. Unfortunately we did not solve the issue of the probe itself, sometimes it works sometimes not, but as there was no real gain with this information we decided to disable the probe for the moment. After that all schedules complete.


Bogdan Tomov1
Tera Expert

Hi Anish,



Can you please check and show us the ECC Queue?


Also can you please tell us how many mid servers do you have? Sometimes if the MID server is upgrading it`s software the ECC Queue is not being processed.


Can you share a screenshot of the MID servers and to which MID server you have assigned the Discovery?


JBark
Tera Expert

What have set for max run time for the discovery schedule?


doug_schulze
ServiceNow Employee
ServiceNow Employee

Anish,



First a little background.   The complete state of a discovery schedule is derived from a Business Rule that checks when the started and completed numbers are equal, its a pure numbers game..



What your screen shot shows is a surprisingly high number of started but none completed.   As Bogdan mentioned above, what are the state of the ECC queue entries? Your midservers up and functioning?



And what the heck are those ~4 thousand entries in the first place!