Facing plugin timeout while checking the VMware

[Uday Kumar]

Hi, Can anyone help out me please.

[root@ubandi]# ./check_vmware_api.pl -H 172.26.140.201 -u xxxx -p xxxxx -l cpu -s usage -w 80 -c 90

CHECK_VMWARE_API.PL UNKNOWN - plugin timed out (timeout 30s)
..

Even after changing t value to 60 or 120, getting same error. But the same plugin is working for other VMwares.

[rkennedy]

What is the output of nmap 172.26.140.201?

[Uday Kumar]

Hi Keneddy,

Please find the output of nmap

[root@ ubandi]# nmap 172.26.140.201

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2016-05-19 11:34 AEST
Interesting ports on 172.26.140.201:
Not shown: 1665 filtered ports
PORT STATE SERVICE
22/tcp closed ssh
1720/tcp open H.323/Q.931
3389/tcp open ms-term-serv
6000/tcp closed X11
6001/tcp closed X11:1
6002/tcp closed X11:2
6003/tcp closed X11:3
6004/tcp closed X11:4
6005/tcp closed X11:5
6006/tcp closed X11:6
6007/tcp closed X11:7
6008/tcp closed X11:8
6009/tcp closed X11:9
6017/tcp closed xmail-ctrl
6050/tcp closed arcserve

Nmap finished: 1 IP address (1 host up) scanned in 20.194 seconds

[tgriep]

The plugin uses port 443 "https" to connect to the VMWare server but in your nmap output, it didn't show that the port is open.
You may want to check to see if that is the correct server and that there is not a firewall blocking the traffic from the Nagios system to the VMWare server.

[Uday Kumar]

Thanks Team,


My problem has been solved .After enabling the 443 port i bm able to monitor all my ESXi hosts..

[rkennedy]

Great to hear! Thanks for letting us know the resolution.

Closing this one out, and marking it as resolved.