Apologies to hijack this question, but i'm facing the exact same problem and didn't want to create a separate question. My discovery finds 53 responding IPs and performs inventory on all 53 and successfully adds them to the device list. yet it never finishes and stays in "running state".
last lines of the discovery log are below:
Audited device at A.B.C.15 IP Audit finish on device A.B.C.15 Audited device at A.B.C.91 IP Audit finish on device A.B.C.91 Audited device at A.B.C.16 IP Audit finish on device A.B.C.16
Using Open-Audit Community 4.3.4 on Windows 10 Pro PC.
Appreciate the help.Add your comment...
Apologies for the delayed response. Confluence didn't let me know there was a question here.
Can you advise the last couple of log lines for that discovery?
Mark Unwin.Add your comment...
(new to Open-AudIT 4.3.3 running on Windows Server 2016)
Trying to scan one IP subnet, 251.0/24. Although the discovery seems to process all the addresses, it doesn't "finish" and stays in "running" status hours/days later with nothing new added to the log. Because of that, it prevents any other discovery from running. There is a similar question in the forums but was never answered: what process(es) do I stop in Task Manager to get out of this condition? My workaround has been to delete the discovery and create a new one but I don't want to do that every time.
Otherwise Open-AudIT is proving to be very useful to me. Thanks.