ESX UNKNOWN - Cannot parse critical range: '$'

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
MouadMimouni
Posts: 6
Joined: Wed Jun 07, 2017 8:38 am

ESX UNKNOWN - Cannot parse critical range: '$'

Post by MouadMimouni »

Hello,

I have installed Nagios and I want to monitor esx servers, using the Plugin Check VMwre API, so I installed vSphere SDK for Perl, but when i log in on nagios I have the problem with the following message (ScreenShot)

Thank you for your reply
Attachments
Error Message (ScreenShot)
Error Message (ScreenShot)
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: ESX UNKNOWN - Cannot parse critical range: '$'

Post by lmiltchev »

Can you show us some of the failing checks, run from the command line, along with the output?
Be sure to check out our Knowledgebase for helpful articles and solutions!
MouadMimouni
Posts: 6
Joined: Wed Jun 07, 2017 8:38 am

Re: ESX UNKNOWN - Cannot parse critical range: '$'

Post by MouadMimouni »

Hello, Thank you for your reply,

when i run command line, i don't have any error messages

Thanks
Attachments
ab.PNG
ab.PNG (6.5 KiB) Viewed 2079 times
mdomanski
Posts: 23
Joined: Thu Dec 15, 2016 11:17 am

Re: ESX UNKNOWN - Cannot parse critical range: '$'

Post by mdomanski »

Could You please provide Your service and command definitions.
MouadMimouni
Posts: 6
Joined: Wed Jun 07, 2017 8:38 am

Re: ESX UNKNOWN - Cannot parse critical range: '$'

Post by MouadMimouni »

Hello,

Here are my configuration files

Thanks
Attachments
service.PNG
commands.PNG
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: ESX UNKNOWN - Cannot parse critical range: '$'

Post by tgriep »

One thing, verify that your $USER11$ and $USER12$ macros do not have an extra $ in the definition and if the password has a $ in it, enclose the password in single quotes.

Code: Select all

$USER12$='Pas$Word'
When you run the check from the command line, the "Possible Precedence" message should not be displayed and it also looks like it is a bug.
https://communities.vmware.com/thread/488747
You may want to try installing a different version of the VMWare Perl SDK of the fix suggested in the link.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked