Ping is crtical on cloudapp

[Naveed]

Thank you everyone for your help and support.

I have tried the suggested way and it did not work for me.
I have even tried it by changing it to host_alive_http for ping service.

Still ping service is down and host is showing down as well.

Screenshots are attached.

Kindly suggest something.

[Naveed]

After making changes on ping service.

Below message is

CRITICAL - Socket timeout after 10 seconds

I have tried with different timeout values but did not work.

[root@AXmonitor vmn]# /usr/local/nagios/libexec/check_http -H daxvsi.cloudapp.net -N -p 80 -t 1
CRITICAL - Socket timeout after 1 seconds
[root@AXmonitor vmn]# /usr/local/nagios/libexec/check_http -H daxvsi.cloudapp.net -N -p 80 -t 10
CRITICAL - Socket timeout after 10 seconds
[root@AXmonitor vmn]# /usr/local/nagios/libexec/check_http -H daxvsi.cloudapp.net -N -p 80 -t 20
CRITICAL - Socket timeout after 20 seconds
[root@AXmonitor vmn]# /usr/local/nagios/libexec/check_http -H daxvsi.cloudapp.net -N -p 80 -t 60
CRITICAL - Socket timeout after 60 seconds
[root@AXmonitor vmn]#

[lmiltchev]

Well, the check could have worked if you didn't have port 80 filtered...

Code: Select all

[root@localhost libexec]# nmap daxvsi.cloudapp.net -p 80

Starting Nmap 6.47 ( http://nmap.org ) at 2016-07-12 11:17 CDT
Nmap scan report for daxvsi.cloudapp.net (13.68.20.130)
Host is up (0.0010s latency).
PORT   STATE    SERVICE
80/tcp filtered http

Nmap done: 1 IP address (1 host up) scanned in 0.35 seconds

Azure doesn't allow inbound ICMP and your choice of open ports is somewhat limited. In fact, it seems like you have only two open ports - 3389 and 5666. You could use any of these ports to set up a check:

Code: Select all

[root@localhost libexec]# ./check_tcp -H daxvsi.cloudapp.net -p 5666
TCP OK - 0.050 second response time on daxvsi.cloudapp.net port 5666|time=0.049702s;;;0.000000;10.000000

however, this is not going to be a good solution. Your NRPE service may be stopped. The check will fail, but this won't mean that the host is down...

Some suggest running psping against a specific TCP port, which is essentially the same thing we did above...

But using the Sysinternals PsPing tool, which allows you to test connectivity to a specific TCP port, you can successfully test connectivity from within the Azure VM to port 80 on an internet site.

https://blogs.msdn.microsoft.com/mast/2 ... nectivity/

[Naveed]

Thank you!

Ping through port 5666 is successful.

One important question is that why still my host is showing down?

All of its services are running fine but it is showing down?

Kindly suggest something.

Thank you!

[rkennedy]

Thank you!

Ping through port 5666 is successful.

One important question is that why still my host is showing down?

All of its services are running fine but it is showing down?

Kindly suggest something.

Thank you!

The default host check is a PING. Ping does not happen through port 5666.

You need to change the host check from being check_ping, to something else that will work, since Azure does not allow ping traffic. You can do so by clicking Configure -> Core Config Manager -> Hosts -> Find that host -> Change the check_command associated with it.

[Naveed]

Very helpful...

My host status is green now.

Thank you very much!

[rkennedy]

Are we good to mark this thread as resolved?

[Naveed]

It worked for me...
But I have seen another problem here....

My VM is down, but ping and few port services are still up.

Screenshot is attached.

[rkennedy]

Take a look at /var/log/messages on the client machine, and see why they are erroring out. Open up a SSH session, and run tail -f /var/log/messages. You'll want to go to each service, click the 'Advanced' tab, and then 'Force a check' on the service. Now, look at everything that appeared in the SSH terminal while the tail was running, and post it here for us to review.

For the record, your ping check is doing the same thing as the NRPE check on port 5666. You can probably just delete it.

[Naveed]

I will update you after testing this...

Thank you!