Nagios Support Forum

Auto-Discovery Status is still going. This is day 4. Not happy.

something must not be kicking off correctly, can you run the following to verify a new job exists

scottwilkerson wrote:something must not be kicking off correctly, can you run the following to verify a new job exists

Code: Select all

ll /usr/local/nagiosxi/html/includes/components/autodiscovery/jobs/

The job I kicked off is run as the nagios administrator, and started on 2014-05-16 08:12:42

The files found in the directory you provided, above, are as follows:
-rw-r----- 1 nagios nagios 28927 May 16 08:12 aaoj3d.out
-rw-r----- 1 nagios nagios 0 May 16 08:09 aaoj3d.watch

The last few statements in the "aaoj3d.out" file is as follows:
"
OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 16.77 seconds
NMAP -> x.y.z.31
NMAP CMD: sudo /usr/bin/nmap -O -oX /usr/local/nagiosxi/tmp/nmapTMIkNU x.y.z.31 <--- EDITED

Starting Nmap 5.51 ( http://nmap.org ) at 2014-05-16 08:12 CDT
"

So, it appears that the job was working for x.y.z.0 through x.y.z.30, but the job has timed out upon doing x.y.z.31??

Having not been updated in 5 days, clearly something killed off the process that was running the job. At this point the only thing I can suggest would be to delete this job and re-run another.

scottwilkerson wrote:Having not been updated in 5 days, clearly something killed off the process that was running the job. At this point the only thing I can suggest would be to delete this job and re-run another.

This has been a problem for several weeks for the past (at least) two versions of the Auto-Discovery and we still are not seeing positive results.
NMAP on it's own works fine.
Whatever this component is attempting to do is not working correctly and needs to be corrected. There is no firewall/networking problems since all other services, systems, applications, etc. work fine in this environment/VLAN.
I will restart the Nagios XI server and will try only one more time.
After that, this is a problem that you will need to be more involved with and fix. We have paid for this product and for the support to have it work and get into production.
I will have our network persons monitor the network traffic when the job kicks off and runs.
I will report back with the results.
Thank you.

MERGED:

PhilG wrote:

scottwilkerson wrote:Having not been updated in 5 days, clearly something killed off the process that was running the job. At this point the only thing I can suggest would be to delete this job and re-run another.

This has been a problem for several weeks for the past (at least) two versions of the Auto-Discovery and we still are not seeing positive results.
NMAP on it's own works fine.
Whatever this component is attempting to do is not working correctly and needs to be corrected. There is no firewall/networking problems since all other services, systems, applications, etc. work fine in this environment/VLAN.
I will restart the Nagios XI server and will try only one more time.
After that, this is a problem that you will need to be more involved with and fix. We have paid for this product and for the support to have it work and get into production.
I will have our network persons monitor the network traffic when the job kicks off and runs.
I will report back with the results.
Thank you.

I deleted the previous Auto-Discovery Job before the server reboot.
I checked the log directory and the files appear to have been deleted automatically.
I rebooted the server and the server came back up with no issues.
I am running a new Auto-Discovery Job with the same IP range/VLAN, but this time did not allow to detect OS.
We are monitoring the process on the firewall.
I am monitoring the Nagios XI Auto-Discovery log file and am noting when an IP has been detected and logged.

I noted in the log file the following so far, below, but the job is still running at this time with no issues:


NMAP CMD: /usr/bin/nmap -oX /usr/local/nagiosxi/tmp/nmap8LLrYi x.y.z.9

Starting Nmap 5.51 ( http://nmap.org ) at 2014-05-22 08:48 CDT
Nmap scan report for x.y.z.9
Host is up (0.00041s latency).
Not shown: 994 closed ports

PORT STATE SERVICE
EDITED: 6 Ports detected and logged.

Nmap done: 1 IP address (1 host up) scanned in 990.88 seconds
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php on line 364
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php on line 364
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php on line 364
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php on line 364
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php on line 364
PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php on line 364

NMAP -> x.y.z.10
NMAP CMD: /usr/bin/nmap -oX /usr/local/nagiosxi/tmp/nmapPuG6Nt x.y.z.10

Starting Nmap 5.51 ( http://nmap.org ) at 2014-05-22 09:04 CDT

MERGED: Much better. It appears that a server reboot worked the magic.

The first job completed under 40 minutes or so.

I am running a couple of more jobs (this time with OS detection) on 2 different subnets and VLANs and will monitor those processes, then will report back.

I am curious about the Autodiscover_new.php errors, too, though.




UPDATE: Auto-Discovery appears to be working now. Thank you.
Will you be able to provide a response about the error(s) found in Autodiscover_new.php that I provided above (error bolded one post up) and then we can close this issue?

Being that /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php is an encrypted file, only Scott or the devs can really look at it. I'll see if I can get one of them to chime in.

tmcdonald wrote:Being that /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php is an encrypted file, only Scott or the devs can really look at it. I'll see if I can get one of them to chime in.

I know you guys are busy, but any chance that this can be checked? Thank you.

Just wanted to give you heads up. Our developers are looking at this issue as we speak. We need some more time for testing but we will make a post as soon as we have a solution for you.

lmiltchev wrote:Just wanted to give you heads up. Our developers are looking at this issue as we speak. We need some more time for testing but we will make a post as soon as we have a solution for you.

Any update regarding this? Thank you.

The wizard and component are 2 different things.

The component should be at version 2.04 and can be downloaded from
http://library.nagios.com/library/produ ... -component

this is the part that actually does the scan.

One thing to note, after upgrading the component you will have to delete and re-run the scan...