Discovery Status stuck and stays in 'Starting ' state for Discovery Schedule.

[Santosh50]

Discovery Status stays in 'Starting ' state for Discovery Schedule.
But when i ran quick discovery, it is started and completed successfully.

[Aaron Duncan]

Not sure if this will help, but I found ours were stuck because the clone from production didn't preserve our lower level instance data and wiped the credentials and also altered the MID Server selection method. Once I corrected those, our Discovery started working again.

[jaredflanders]

I had two discovery schedules to this two me. We have some “imperva” appliances that I haven’t been able to figure out how to discover. The Imperva appliances tend to make the discovery schedules hand and time out. I now include the Imperva appliances in the global exclude list. While I was waiting for an admin to give me a new list of Imperva appliances, I had marked an IP range(s) in my Discovery Range Set(s) as false, so the rest of the ranges could be discovered. Once I had the new Imperva appliances updated in my global exclude list, I went back into the Discovery Range set(s) and marked the IP ranges(s) back to true.

The two discovery schedules that I had mark an IP range as false and then true would not run. They just stuck in “starting”.

I stopped MID server services and restarted. I rebooted the MID server. The two discovery schedules still would not run.

I rebuilt the two discovery schedules from scratch – coping line for line everything from the stuck schedules. The new names have (v2) behind the name. The new discovery schedules both run now.