Page 3 of 4
Re: check_vmfs command
Posted: Tue Oct 11, 2016 6:33 pm
by Box293
Maybe try installing libxml through yum:
Re: check_vmfs command
Posted: Wed Oct 12, 2016 3:36 pm
by scheema31
okay perfect, looks like that inslled the folowoing:
Installed:
perl-libxml-perl.noarch 0:0.08-19.el7
Dependency Installed:
perl-XML-Parser.x86_64 0:2.41-10.el7
now do i need to go back and run ./vmware-install.pl, how do i know this has been installed, ran through many steps just trying to put this together.
the origonal command/issue is still present
Code: Select all
#/usr/local/nagios/libexec/check_vmfs.sh -S #.#.#.81 -V /vmfs/volumes/VM-10GDATASTORE-1
which: no vmkfstools in (/root/perl5/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
CRITICAL - /usr/local/nagios/libexec/check_vmfs.sh: line 161: --username: command not found
Thanks,
Re: check_vmfs command
Posted: Wed Oct 12, 2016 3:40 pm
by dwhitfield
Yes, you need to rerun ./vmware-install.pl. The which error is telling you it can't find the application.
It's possible that it would be installed and not in path, but it sounds like we still need to install. If you still have the issue once you get through ./vmware-install.pl, we'll start digging for the actual install path.
Re: check_vmfs command
Posted: Wed Oct 12, 2016 4:12 pm
by scheema31
okay re-ran the ./vmware-install.pl command, it installed most of the pre-requisite Perl modules but still getting error on following:
#CPAN not able to install following Perl modules on the system. These must be installed manually for use by vSphere CLI:
Class::MethodMaker 2.10 or newer
UUID 0.03 or newer
XML::LibXML::Common 0.13 or newer
XML::LibXML 1.63 or newer
ive already tried installing using
#cpan App::cpanminus
#cpanm Module::Name
also through yum
#yum install -y perl-libxml-perl
Re: check_vmfs command
Posted: Wed Oct 12, 2016 4:20 pm
by tgriep
What OS and version is the Nagios server running?
Run these commands to install the Perl Modules and see if the VMWare PERL SDK will install now.
Code: Select all
yum erase perl-XML-SAX-Base -y
yum install perl-XML-SAX --exclude=perl-XML-SAX-Base -y
yum install perl-Nagios-Plugin libuuid* perl-XML-LibXML
Re: check_vmfs command
Posted: Wed Oct 12, 2016 4:24 pm
by avandemore
You got about as far as I did originally but at that point it really became apparent the
VCLI isn't meant to run on RHEL/CentOS 6/7. So my next question would have been does the Nagios plugin work with a newer version of VCLI as they are available and apparently easier to install. Since this plugin is not in the scope of support, I would say either try the installation with a newer CLI or an old OS eg CentOS 5.
Re: check_vmfs command
Posted: Wed Oct 12, 2016 4:27 pm
by dwhitfield
But note that CentOS 5 loses support in March.
Re: check_vmfs command
Posted: Wed Oct 12, 2016 4:41 pm
by Box293
Or you could try another plugin like box293_check_vmware. It uses a vMA appliance that already has all the pre-requisites loaded and saves all of this hassle.
box293_check_vmware can be downloaded here:
http://exchange.nagios.org/directory/Pl ... re/details
Detailed manual will get you up and running fast.
Re: check_vmfs command
Posted: Fri Oct 14, 2016 5:32 pm
by scheema31
thanks Box293, im using your plugin suggestion.
i have installed the plugin and now im just stuck on Step:
Configure vMA Credentials > vCenter Server Credentials,
Type
~/box293_check_vmware.pl --server 192.168.1.211 --check
vCenter_Name_Version
and press Enter
after issuing this command on my vMA the cosole just shuts down
thanks
Re: check_vmfs command
Posted: Sun Oct 16, 2016 7:56 pm
by Box293
I'm not sure what is going on here.
scheema31 wrote:Type
~/box293_check_vmware.pl --server 192.168.1.211 --check
vCenter_Name_Version
and press Enter
Perhaps the minus sign you are using is the cause. It's a tilde ~ symbol which is usually on the key next to the 1 key on your keyboard. Or maybe you typed it correctly and it's the forum that is not correctly displaying the symbol.
Before you press Enter to execute the command perhaps take a screenshot so we can see exactly what is going on.
You may also want to try directly on the console instead of inside an ssh session.