Nagios Support Forum

Re-installed and made the changes. It is still not working.

Check the attached logs.

Here you go: uname -a Linux hanjin 4.10.0-40-generic #44-Ubuntu SMP Thu Nov 9 14:49:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux cat /etc/*release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty DISTRIB_DESCRIPTION="Ubuntu 17.04" NAME="Ubuntu" VERSION="17.04 (Z...

Turned debugging off and restarted the services. The ncpa_passive.log is showing this error: 2018-01-09 11:31:21,817 7722 INFO Running check: processes --warning 300 --critical 400 2018-01-09 11:31:21,959 7722 INFO Running check: disk/logical/|/used_percent --warning 80 --critical 90 2018-01-09 11:3...

Hi @tgriep

I reverted the ncpa.cfg since I didn't had them in the first place. And restarted the services. It is still trying to connect every second.

@tgriep see attached.

Thanks for the clarification npolovenko . Yes, I can curl it and it seems to work curl http://54.165.9.118/nrdp/. <strong>Submit Nagios Command:</strong><br> <form action="" method="get"> <input type="hidden" name="cmd" value="submitcmd"> Token: <inp...

Hi npolovenko , After some investigation heere are the results for Nmap. nmap 54.165.9.118 -p 80 Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-05 10:42 EST Nmap scan report for NAGIOS (54.165.9.118) Host is up (0.032s latency). PORT STATE SERVICE 80/tcp open http Nmap done: 1 IP address (1 host...

Attached few logs files, let me know if you need more.

Hi @ npolovenko

I'm getting: on both ports.

I checked the inbound rules on Nagios Core in AWS, and I made it open for both ports and still.

See attached log file.