Hi,
I am new to nagios and am have some major difficulties. The first was to find all the changes required to allow a script to receive an extra parameter, but that seems to be sorted.
The second is that the new parameter contains characters that seem not to be allowed mainly ' and []. I have tried escaping these but with degub on get a error message about illegal meta chars. I have to be able to pass these are they are par of the parameter, so how?
have seen lots of posts about NSClient, but cannot seem to find this as having been install.
I am using Linux.
Thanks for reading.
Complex arguments
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Complex arguments
Can you unpack this a bit for us? NSClient is generally used for monitoring Windows. What are you actually trying to monitor? The more detail you can give us, the better.Tractor boy wrote: have seen lots of posts about NSClient, but cannot seem to find this as having been install.
I assume you mean Nagios is running on Linux. What distro/version? cat /etc/*-release will be useful.I am using Linux.
Also, what version of Core are you running? Did you compile from source or install from distro repos? Distro repos can help you get going more quickly, but the compile process is not difficult, and will help us better assist you when you run into issues.
-
Tractor boy
- Posts: 5
- Joined: Thu Dec 08, 2016 7:16 am
Re: Complex arguments
Thanks for confirming NCClient is windows, which is why I cannot track it down on my Linux install.
In terms of the install, I didn't do it and have no idea how it was installed, but would assume precompiled as that's traditionally the more supported(able) approach so would hope/expect that to have been the way.
cat /etc/*-release produces
CentOS release 6.7 (Final)
CentOS release 6.7 (Final)
CentOS release 6.7 (Final)
What version of core. I am note aware of what was installed, so you would need to advise on how to obtain the version details.
The ticket happens to be the same in terms of the issue as another ticket that I have raised. Although they were very much worded differently. You have covered off the NSClient point so am thinking it worth closing this one and keeping with a single ticket.
In terms of the install, I didn't do it and have no idea how it was installed, but would assume precompiled as that's traditionally the more supported(able) approach so would hope/expect that to have been the way.
cat /etc/*-release produces
CentOS release 6.7 (Final)
CentOS release 6.7 (Final)
CentOS release 6.7 (Final)
What version of core. I am note aware of what was installed, so you would need to advise on how to obtain the version details.
The ticket happens to be the same in terms of the issue as another ticket that I have raised. Although they were very much worded differently. You have covered off the NSClient point so am thinking it worth closing this one and keeping with a single ticket.
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Complex arguments
It's more complicated than that: https://www.nsclient.org/tag/linux/Tractor boy wrote:Thanks for confirming NCClient is windows, which is why I cannot track it down on my Linux install.
Generally people find other options within Nagios are better for monitoring Linux. Newer versions of NSClient can be used as a stand alone. For probably obvious reasons, I don't know anyone that actually does that.
Easiest way is just to go to the Nagios landing page, assuming apache is serving things up.What version of core. I am note aware of what was installed, so you would need to advise on how to obtain the version details.
I'm happy to close it, but I don't want to mislead you about NSClient. There's no need to respond if you want to close. It can just lay dormant.You have covered off the NSClient point so am thinking it worth closing this one and keeping with a single ticket.
Re: Complex arguments
You should be able to turn them on with dont_blame_nrpe = 1The second is that the new parameter contains characters that seem not to be allowed mainly ' and []. I have tried escaping these but with degub on get a error message about illegal meta chars. I have to be able to pass these are they are par of the parameter, so how?
Code: Select all
ENABLING ARGUMENTS
------------------
To enable support for command argument in the daemon, you must
do two things:
1. Run the configure script with the --enable-command-args
option
2. Set the 'dont_blame_nrpe' directive in the NRPE config
file to 1.
Former Nagios Employee