Highlighted
GeertC
Bronze

OME - scheduled discovery not started because previous discovery still in progress

I see the following message in OME Application Logs

A scheduled discovery of all devices on a discovery range was not started because the previous discovery of that range is still in progress. If this condition continues, it is recommended that you increase the discovery cycle interval time. Scheduled time: 20170915T180002. The following managed devices are still undergoing discovery: 192.1.1.50 

in Discovery and Inventory Portal, there is no Running Task, in the Task Status view.
(all Tasks have the status Completed)

It seems that some task is stuck, but not displaying correctly?
Is there any way to troubleshoot what is going on? 
 

Grz,
Geert

0 Kudos
2 Replies

RE: OME - scheduled discovery not started because previous discovery still in progress

Hi, thanks for the query.

A discovery task can get stuck in very remote cases for any issues on target device. I would suggest you to restart OME services from "General Settings" page and re-trigger discovery.

Thanks,

Shivendra

GeertC
Bronze

RE: OME - scheduled discovery not started because previous discovery still in progress

Rebooting the service helped for getting the discovery working again, but always stopped at the same IP again.
After rebooting the affected iDrac several times, now the scan is no longer stuck on the IP :-)
Thanks

0 Kudos