Discovery stops In between ; doesn't complete

[Abhijeet Yadav]

Hi All,

We are running few discovery schedules. However, some of them are still in 'Active' state after 48 hours ! I don't see any changes in the Stared / completed probes number either. It just halts for infinite time. These are individual schedules,not dependant on each other.

I have proposed MID server config changes as,

<parameter name="threads.max" value="100"/>

<parameter name="threads.expedited.max" value="100"/>

<parameter name="threads.interactive.max" value="100"/>

Any other suggestions?

Thanks,

Abhijeet

[DaveHertel]

Hi -- I doubt this is a thread issue.  Something else is hanging the job -- if the responses aren't coming back within a few minutes, generally something else is getting in way.  I'm generalizing but....

I'd look a the IP's that have outbound probes but don't' have a corresponding inbound response.  These could be the troubling IPs.  Perhaps stack switches or something with really big payloads (just guessing).  If you can narrow down an IP that is a culprit try doing a single quick disco of that IP and see what happens to troubleshoot from there.  Also, what stage in discovery is the IP hanging... Shazzam?  ID/classifying?  some specific probe? etc..  these are clues that are more easily troubleshot when looking at a single IP that may be causing issues.

Hope this helps?

[Abhijeet Yadav]

Hi Dave,

Some probes are in Classifying, some say Active,could not classify.

I manually started the probes again from Ecc_queue but definitely not a solution. We are trying to divide the IP ranges and will run the schedule again to so if it makes the difference.

Thanks,

Abhijeet

[DaveHertel]

To narrow down scope of troubleshooting, focus on IPs that show Active.... these are IPs that definitely exist because some kind of response was received (which is why its deemed "active").  For those, the likely culprit is lack of credentials -- no guarantee, but very, very common issue.

Be sure whatever credentials you've defined work for X IP address.  Test the cred against that IP... if it works, run a quick discovery of just that IP.

Hope this helps?

[Ankush13]

Do a restart of the MID server service and those stalled ones should complete.