Socket Time Out error in the Amazon Ec2 Cloud Instance.

[rahul5028]

Here is the screenshot of service info from Configure -> Core Config Manager -> Click 'Services

Also following is the output when I run nmap windowsip on NagiosXI Ec2 Instance on Amazon AWS, Can You please guide where exactly the problem is and how we can rectify this issue?

[rkennedy]

Perfect, looks like you're using check_nt which will use port 12489.

The nmap should have been able to ping the host, and show us that port 12489. Because the Nagios machine can't even ping the 172.25.30.41 machine though, really makes me think this is a firewall issue. Can you please verify your Amazon settings?

[rahul5028]

On Amazon AWS we have open ports for 12489,5666 in the security Inbound rules(Refer below screenshot), Also we turned off firewall on windows server which we are trying to monitor.

Not sure where exactly the problem, It looks all configuration settings good. Could you please guide us to fix this issue.

[rkennedy]

Do you have security groups in play? This will be difficult because we don't know how your network is setup.

[rahul5028]

Security groups running on AWS Instance..I'm not sure which network setup you are talking about. Nagios Instance running on AWS and that Instance trying to communicate with our local windows server but its not happening.

[tgriep]

Lets see if running the nmap to port 12489 returns any information.
Login to your XI server and run the following and post the results.

Code: Select all

nmap 172.25.30.41 -p 12489

From your windows host, can you check the nsclient.log file for any errors and post them?
Can you upload your nsclient.ini or nsc.ini file from the Nsclient++ folder?

[rahul5028]

Please see all required information in below screenshots, Also It would be great if you guys guide us with some Instructions how we can setup nagios Instance properly on Amazon AWS Instead of spending lot of time for posting and reply.

[bwallace]

You have a network issue somewhere if Nmap cannot reach the target host and we cannot help you with that unfortunately.

Once you get that cleared up, we would be happy to assist and we can start by correcting your NSCLIENT.ini file -- you'll need to add the XI IP address seen in the screenshot to the ALLOWED HOSTS line. Keep in mind this has no influence on the Nmap results however.

[jolson]

Code: Select all

nmap -Pn -p 12489 172.25.30.41

Give the above a try - that will let us know for certain whether or not the port is open. Thanks!

[rahul5028]

Following is the output of nmap -Pn -p 12489 172.25.30.41, Can you please guide us if there are any customization that we need to do on AWS Amazon system.