Nagios Support Forum

Looks like this is definitely nmap problem even with the latest database it cant detect windows with IIS web server running nmap -v -Pn -O "my server" - Windows 2012 R2 Device type: WAP|general purpose Running (JUST GUESSING): Linksys embedded (89%), Linux 2.6.X (85%), HP HP-UX 11.X (85%) ...

current version 6.47 #yum update nmap Loaded plugins: fastestmirror Determining fastest mirrors epel/x86_64/metalink | 15 kB 00:00:00 * base: ftpmirror.your.org * epel: mirror.team-cymru.com * extras: ftpmirror.your.org * updates: ftpmirror.your.org base | 3.6 kB 00:00:00 epel | 5.3 kB 00:00:00 extr...

after I was able to scan subnet and services (https://support.nagios.com/forum/viewtopic.php?f=6&t=55520) I looked at the results and clicked NEXT I got error message Invalid service name '' on host my host name when I scrolled down to that host, I did not see anything that could cause it. servi...

Hello Nagios XI V 5.6.6 I did not use Auto Discover feature since v 4.x (2-3 years ago) My network configuration did not change (at least for the subnet I want to scan) I am trying it now, and noticing strange behavior. My Windows 2008R2 Detected as Cisco MDS 9509 switch (NX-OS 4.2) Server 2012 / 20...

It does not work on either 5.63 (Production) or 5.65 (Test) systems. Test systems has a job from 2016; results of that job show services. cd /usr/local/nagiosxi/html/includes/components/autodiscovery ls -l -rw-r--r--. 1 nagios nagios 12800 Aug 27 13:15 autodiscovery.inc.php -rw-r--r--. 1 nagios nagi...

Nagios XI v 5.63 / 5.65 Auto-discovery v 1.4.2 When I run new Auto-Discovery scan, it does not detect any services new.png I tried with custom ports empty and with 1-1000 value - no difference. When I look on results from older scans still saved (from 2016) I see that all services are detected and l...

That did the trick - everything is working now.

It sort of working. Inbound configuration did not change FROM address automatically as promised :) , no big deal, I changed it sending configuration to match. I simulated failure and got email with ---- Respond above this line ---- ***** Nagios XI Alert ***** Nagios has detected a problem with this ...

As I mentioned earlier, IMAP port was the 1st problem. Port Hint looks like port already entered, while it was blank The second problem was "!" character in mailbox password. "!" used as delimiter in Nagios, so after password change it stop giving Authentication errors. However, ...

I updated to 5.61 - same error. After taking 20th look, I relaized that IMAP port number need to be typed in, it looks like it prepopulated to 143, but it not. After typing the port number and testing, error changed to SECURITY PROBLEM: insecure server advertised AUTH=PLAIN Can not authenticate to I...