Page 1 of 3
Nagios not showing correct Datastore size
Posted: Mon Jan 23, 2017 11:19 am
by bosecorp
Team,
When I run the below command to check the data store capacity I am getting the below output
# /usr/local/nagios/libexec/check_esx3.pl -H "10.101.28.24" -f "/usr/local/nagiosxi/etc/components/vmware/usmadcevm04_bose_com_auth.txt" -l "VMFS" -s dce-Paging_2 -c99.90% -w99%
ESX3 CRITICAL - dce-Paging_2=2095915.00 MB (99.95%) | dce-Paging_2=99.95%;99;99.9
# /usr/local/nagios/libexec/check_esx3.pl -H "10.101.28.24" -f "/usr/local/nagiosxi/etc/components/vmware/usmadcevm04_bose_com_auth.txt" -l "VMFS" -s dce-Paging_1 -c99.90% -w99%
ESX3 OK - dce-Paging_1=218141.00 MB (10.40%) | dce-Paging_1=10.40%;99;99.9
When I go tot Nagios GUI it is showing me the screen as attached and when I check the datastore in VMware it is showing me different value as attached in the file.
e.g. when I try to convert the dce-Paging_1 free space 218141.00 MB to GB it is showing me as 218 GB, but in VMware it is showing me free space as 207 GB (screenshot in the attached file)
We are running Nagios XI.
Re: Nagios not showing correct Datastore size
Posted: Mon Jan 23, 2017 5:13 pm
by avandemore
Is your question dce-paging_2 or dce-paging_1?
What version of the SDK is installed on XI and what VMware version are you connecting too?
This may simply be something like the VMware front-end is calculating space slightly differently.
Re: Nagios not showing correct Datastore size
Posted: Thu Jan 26, 2017 11:47 am
by bosecorp
It is not just for dce-paging_2 or dce-paging_1 but for rest of other drives as well.
How to find the SDK version installed on Nagios.
VMware version is ESXi 5.1.
Re: Nagios not showing correct Datastore size
Posted: Thu Jan 26, 2017 12:03 pm
by dwhitfield
Running find / -name *vmware* should find it for you.
If you find nothing with that, you can try find / -name *VMware*, but the extracted files should be lower case.
Re: Nagios not showing correct Datastore size
Posted: Thu Jan 26, 2017 6:39 pm
by bosecorp
I am not able to find the SDK version for VMware.
When I tried to find the SDK version for vmware using "find / -name *vmware* " I am getting the output for all the file names.
Code: Select all
# find / -name *vmware*
find: `/home/vi1013091': Permission denied
find: `/home/gc6927': Permission denied
find: `/home/gc2851': Permission denied
find: `/home/el872784': Permission denied
/lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/misc/vmware_balloon.ko
/lib/modules/2.6.32-431.5.1.el6.x86_64/kernel/drivers/misc/vmware_balloon.ko
/etc/selinux/targeted/modules/active/modules/vmware.pp
/etc/vmware-tools
/etc/vmware-tools/vmware-user.desktop.old.2
/etc/vmware-tools/vmware-tools
/etc/vmware-tools/vmware-user.Xresources
/etc/vmware-tools/scripts/vmware
/etc/vmware-tools/vmware-user.desktop.old.1
/etc/vmware-tools/vmware-tools-prelink.conf
/etc/vmware-tools/vmware-user.desktop.old.0
/etc/vmware-tools/vmware-tools-libraries.conf
/etc/vmware-tools/vmware-user.desktop
/etc/prelink.conf.d/vmware-tools-prelink.conf
/etc/udev/rules.d/99-vmware-scsi-udev.rules
/etc/xdg/autostart/vmware-user.desktop
/etc/init/vmware-tools.conf
/etc/modprobe.d/vmware-tools.conf
/etc/vmware-vcli
/etc/dracut.conf.d/vmware-tools.conf
/etc/vmware-viperl
/etc/ld.so.conf.d/vmware-tools-libraries.conf
/ubstmp/linux/CentOS/centos-6.2-x64-virtual-machine-org/vmware-0.log
/ubstmp/linux/CentOS/centos-6.2-x64-virtual-machine-org/vmware.log
/ubstmp/linux/misc_images/nagioslogserver-2015r1.2-vmware-64.zip
/ubstmp/bob/IBM DSA/ubslnx1/7979AC1_KQCYMZ7_20110317-132900/vmware_esxi.html
/ubstmp/bob/IBM DSA/ubslnx1/7979AC1_KQCYMZ7_20120103-125635/vmware_esxi.html
/ubstmp/bob/IBM DSA/derbydb/7946AC1_KQWCKBD_20110317-141705/vmware_esxi.html
/ubstmp/bob/IBM DSA/audio1/794632U_99B0462_20110317-144117/vmware_esxi.html
/ubstmp/bob/IBM DSA/audio2/794632U_99B0459_20110317-144346/vmware_esxi.html
/ubstmp/bob/IBM DSA/audiomst/794632U_99B0450_20110317-144430/vmware_esxi.html
/ubstmp/bob/IBM DSA/corpcomm/7947AC1_KQPCWNF_20110317-161120/vmware_esxi.html
/ubstmp/bob/IBM DSA/corpcomm/7947AC1_KQPCWNF_20130802-125905/vmware_esxi.html
/ubstmp/bob/IBM DSA/corpcomm/7947AC1_KQPCWNF_20120502-105808/vmware_esxi.html
/ubstmp/bob/IBM DSA/cvsvn01/7978BDU_99K3498_20110317-162407/vmware_esxi.html
/ubstmp/bob/IBM DSA/cvsvn02/7978BDU_99K3523_20110317-162445/vmware_esxi.html
/ubstmp/bob/IBM DSA/eclddev/794632U_99B5590_20110318-102216/vmware_esxi.html
/ubstmp/bob/IBM DSA/ecldprod/794632U_99B1558_20110318-102236/vmware_esxi.html
/ubstmp/bob/IBM DSA/klocwork/79787AU_99F4607_20110318-133421/vmware_esxi.html
/ubstmp/bob/IBM DSA/madeflow1/797971U_99D0210_20110318-133930/vmware_esxi.html
/ubstmp/bob/IBM DSA/madeflow2/797971U_99D0136_20110318-133934/vmware_esxi.html
/ubstmp/bob/IBM DSA/madeflow2/797971U_99D0136_20111214-154811/vmware_esxi.html
/ubstmp/bob/IBM DSA/madeflow2/797971U_99D0136_20120103-123911/vmware_esxi.html
/ubstmp/bob/IBM DSA/madeflow2/797971U_99D0136_20120202-124512/vmware_esxi.html
/ubstmp/bob/IBM DSA/rumblesvn/7978AC1_KQHAV24_20110318-134758/vmware_esxi.html
/ubstmp/bob/IBM DSA/rumblesvn/7978AC1_KQHAV24_20120103-111634/vmware_esxi.html
/ubstmp/bob/IBM DSA/rumblesvn/7978AC1_KQHAV24_20120202-124519/vmware_esxi.html
/ubstmp/bob/IBM DSA/sig-dev/7978AC1_KQHAV23_20110318-134806/vmware_esxi.html
/ubstmp/bob/IBM DSA/poly1/vmware_esxi.html
/ubstmp/bob/IBM DSA/ubslnx2/883721Y_KKTTP4Y_20120810-142841/vmware_esxi.html
/ubstmp/bob/IBM DSA/ccdev/883715U_KQGCF4F_20120202-122829/vmware_esxi.html
/ubstmp/bob/IBM DSA/ccdev/883715U_KQGCF4F_20120116-141204/vmware_esxi.html
/ubstmp/bob/IBM DSA/ccdev/883715U_KQGCF4F_20120202-141337/vmware_esxi.html
/ubstmp/bob/IBM DSA/ccdev/883715U_KQGCF4F_20120202-155406/vmware_esxi.html
/ubstmp/bob/IBM DSA/ccdev/883715U_KQGCF4F_20120206-123918/vmware_esxi.html
/ubstmp/bob/IBM DSA/klocwork.bose.com/79787AU_99F4607_20121107-090425/vmware_esx i.html
/ubstmp/bob/IBM DSA/eclddev.bose.com/794632U_99B5590_20130130-132740/vmware_esxi .html
/ubstmp/bob/IBM DSA/ecldprod.bose.com/794632U_99B1558_20130130-134228/vmware_esx i.html
/ubstmp/jeff/ccdev/883715U_KQGCF4F_20121126-095041/vmware_esxi.html
/ubstmp/Emmanuel/NagiosXI/IconsOrig/vmware2.gd2
/ubstmp/Emmanuel/NagiosXI/IconsOrig/vmware2.gif
/ubstmp/Emmanuel/NagiosXI/IconsOrig/vmware2.png
/ubstmp/Emmanuel/NagiosXI/IconsOrig/vmware.gd2
/ubstmp/Emmanuel/NagiosXI/IconsOrig/vmware.gif
/ubstmp/Emmanuel/NagiosXI/IconsOrig/vmware.png
/ubstmp/Emmanuel/NagiosXI/vmware-Perl-SDK
/ubstmp/Emmanuel/NagiosXI/nagiosxi/subcomponents/xiwizards/wizards/vmware.zip
/ubstmp/Emmanuel/NagiosXI/nagiosxi/nagiosxi/basedir/html/includes/components/nag ioscore/ui/images/logos/vmware.gd2
/ubstmp/Emmanuel/NagiosXI/nagiosxi/nagiosxi/basedir/html/includes/components/nag ioscore/ui/images/logos/vmware2.png
/ubstmp/Emmanuel/NagiosXI/nagiosxi/nagiosxi/basedir/html/includes/components/nag ioscore/ui/images/logos/vmware2.gif
/ubstmp/Emmanuel/NagiosXI/nagiosxi/nagiosxi/basedir/html/includes/components/nag ioscore/ui/images/logos/vmware2.gd2
/ubstmp/Emmanuel/NagiosXI/nagiosxi/nagiosxi/basedir/html/includes/components/nag ioscore/ui/images/logos/vmware.png
/ubstmp/Emmanuel/NagiosXI/nagiosxi/nagiosxi/basedir/html/includes/components/nag ioscore/ui/images/logos/vmware.gif
When I tried to find the SDK version for vmware using "find / -name *VMware*" still getting the same output
Code: Select all
# find / -name *VMware*
find: `/home/vi1013091': Permission denied
find: `/home/gc6927': Permission denied
find: `/home/gc2851': Permission denied
find: `/home/el872784': Permission denied
/etc/cups/ppd/VMware_Virtual_Printer.ppd
/ubstmp/bob/VMwareTools-8.3.12-493255.tar.gz
/ubstmp/bob/vms/VMwareTools-9.0.10-1481436.tar.gz
/ubstmp/jeff/VMware vCenter Converter Standalone Client.lnk
/ubstmp/jeff/VMware vSphere Client.lnk
/ubstmp/jeff/VMware vSphere Client (2).lnk
/ubstmp/Emmanuel/NagiosXI/vmware-Perl-SDK/VMware-vSphere-Perl-SDK-6.0.0-2503617.x86_64.tar.gz
/ubstmp/Emmanuel/NagiosXI/vmware-Perl-SDK/VMware-vSphere-Perl-SDK-6.0.0-2503617.i386.tar.gz
Can you please let me know how to find the SDK version for VMware.
Re: Nagios not showing correct Datastore size
Posted: Fri Jan 27, 2017 12:35 pm
by dwhitfield
bosecorp wrote:
/ubstmp/Emmanuel/NagiosXI/vmware-Perl-SDK/VMware-vSphere-Perl-SDK-6.0.0-2503617.x86_64.tar.gz
/ubstmp/Emmanuel/NagiosXI/vmware-Perl-SDK/VMware-vSphere-Perl-SDK-6.0.0-2503617.i386.tar.gz
Looks like 6.0.0 is downloaded.
I wonder if you'd have better luck using
https://exchange.nagios.org/directory/P ... re/details
You could also try updating the version of the plugin you are using.
Re: Nagios not showing correct Datastore size
Posted: Fri Jan 27, 2017 1:56 pm
by bosecorp
Does this mean that there is an issue with the existing Plug-in that we are using.
Re: Nagios not showing correct Datastore size
Posted: Fri Jan 27, 2017 3:11 pm
by avandemore
The plugin makes use of the the SDK. For best results, you should have the SDK match the VMWare version you are connecting too.
Ultimately though the data you're comparing is almost an apples to oranges situation. We don't know how VMWare calculates their data. Different things can impact this eg 1000 vs 1024 space calculations, reservations, etc.
Do you have any reason to suspect the Nagios plugin is reporting inaccurate data other than the difference a separately reporting tool is giving?
Re: Nagios not showing correct Datastore size
Posted: Thu Feb 02, 2017 12:20 pm
by bosecorp
I tried installing perl-Nagios-Plugin-0.35-2.el6.rf.noarch and then when I try to run the ./check_esx3-0.5.pl it gives me the below error message.
root@nagmonusdev1:(02-02 11:43): /tmp
# ./check_esx3-0.5.pl
/usr/bin/perl: symbol lookup error: /usr/local/lib64/perl5/auto/XML/LibXML/Common/Common.so: undefined symbol: Perl_Tstack_sp_ptr
Re: Nagios not showing correct Datastore size
Posted: Thu Feb 02, 2017 12:39 pm
by dwhitfield
Please run the following
Code: Select all
yum clean all
yum erase perl-XML-SAX-Base-1.04-1.el6.rf.noarch
yum install perl-XML-SAX -y
yum install perl-Nagios-Plugin libuuid* perl-XML-LibXML -y
If the erase command doesn't work, I wouldn't worry about it. Please post any new errors (or if you have the same error)