Auto-Discovery Job Never Finishes

[johnpickett]

Before I get flamed, I saw this post already:

http://support.nagios.com/forum/viewtop ... 16&t=25575

I am using the OVA appliance: http://assets.nagios.com/downloads/nagi ... 2.9-64.ova

Q: What version of Nagios XI are you using?
A: 2012R2.9

Q: Linux Distribution and version?
A: CentOS - 64-bit

Q: VMware Image or Manual Install of XI?
A: OVA [see above]

I don't believe my system is customized other than changing the root and config passwords and changing hostname/dhcp->static.

As this job started I saw the nmap commands cycling through (ps -aef | grep nmap) and then started to actually watch as it went through each ip (tail nmap* | grep xxx.xxx.xxx). It finished executing nmap about an hour ago but the Status animation is still going and there is no change in the other fields (Devices Found = N/A). I'm currently at a loss. Note, I'm using the trial version. My last team used Nagios Enterprise and I want to get it setup here to show them how useful it is.

[abrist]

You will need to upgrade the autodiscovery config wizard and component to their newest versions, then delete any old scans and start them over.

[johnpickett]

You will need to upgrade the autodiscovery config wizard and component to their newest versions, then delete any old scans and start them over.

Thanks. It actually eventually finished. I have no idea why it was taking so long after the nmap's seemed to finish. I would've reported back sooner but the post wasn't approved yet. Thanks again for your help.

[abrist]

If ports are filtered (not blocked) by a network device (like a firewall), the scan can take *significantly* longer than normal as each port checks waits for a timeout. I tend to suggest that it is best to scan in small blocks, like x.x.x.x/24.