Nagios Event Log NSCLIENT help

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.
me@work55
Posts: 44
Joined: Sun Jan 22, 2017 6:15 pm

Re: Nagios Event Log NSCLIENT help

Post by me@work55 »

[root@anakin ~]# /usr/local/nagios/libexec/check_nrpe -V
/usr/local/nagios/libexec/check_nrpe: invalid option -- 'V'

NRPE Plugin for Nagios
Copyright (c) 1999-2008 Ethan Galstad (nagios@nagios.org)
Version: 2.12
Last Modified: 03-10-2008
License: GPL v2 with exemptions (-l for more info)
SSL/TLS Available: Anonymous DH Mode, OpenSSL 0.9.6 or higher required
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: Nagios Event Log NSCLIENT help

Post by ssax »

That's a pretty old version of check_nrpe, please upgrade to the latest and try again:

Code: Select all

https://exchange.nagios.org/directory/Addons/Monitoring-Agents/NRPE--2D-Nagios-Remote-Plugin-Executor/details
me@work55
Posts: 44
Joined: Sun Jan 22, 2017 6:15 pm

Re: Nagios Event Log NSCLIENT help

Post by me@work55 »

I downloaded the newest version per your link

Will I have to worry about any other services defined that use nrpe?

Will the services I already have defined still work?

Really do not want to cause a major issue at this point

No one has gotten back on my last post with the nsclient ini files

I still believe that I have a config issue still in Nagios or the nsclient.ini
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Nagios Event Log NSCLIENT help

Post by rkennedy »

We are currently working through the issue at hand with your NRPE version which can affect your NSClient++ configuration file. Have you upgraded to the latest version and tested it out yet?

It should be backwards compatible as long as they're compiled the same way.
Former Nagios Employee
me@work55
Posts: 44
Joined: Sun Jan 22, 2017 6:15 pm

Re: Nagios Event Log NSCLIENT help

Post by me@work55 »

Not yet

But no one on here has replied about the newest nsclient.ini files I posted.


Thanks
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Nagios Event Log NSCLIENT help

Post by rkennedy »

rkennedy wrote:The problem is actually with the syntax, or NSClient++ - Nagios is only presenting the information. You may have better luck creating a thread over here directly - https://forums.nsclient.org/

If you try another version, does it work successfully? check_eventlog appears to be the newer version at this point, while checkeventlog is deprecated. This page may help you out - https://docs.nsclient.org/reference/win ... kEventLog/
Have you taken a chance to create a post on their forums? Your best bet for support is going to be the products forums.

From what I can tell, you posted your configuration files and @ssax made a suggestion. I'm not sure what you're referring to at this point.
Former Nagios Employee
me@work55
Posts: 44
Joined: Sun Jan 22, 2017 6:15 pm

Re: Nagios Event Log NSCLIENT help

Post by me@work55 »

I tried posting on that site and never get a responce
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios Event Log NSCLIENT help

Post by tgriep »

The file format between the 4.1.x and the 4.3.x nsclient.ini files are the same so you can stop the nsclient++ service on the Windows system, replace it with the old one and start it up.
That should work for your check.
Be sure to check out our Knowledgebase for helpful articles and solutions!
me@work55
Posts: 44
Joined: Sun Jan 22, 2017 6:15 pm

Re: Nagios Event Log NSCLIENT help

Post by me@work55 »

Nope that did not work
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios Event Log NSCLIENT help

Post by tgriep »

If you are using the nsclient.ini file from your earlier post, edit it and under this section

Code: Select all

[/settings/default]
Remove this line

Code: Select all

allowed ciphers = ADH
Then under this section
put the following.

Code: Select all

[/settings/NRPE/server]

put the following if it doesn't exist.

Code: Select all

ssl options = 
verify mode = none
insecure = true
allow arguments = true
allow nasty characters = true
use ssl = 1
port = 5666
extended response = 0

Save the file and restart the NSClient++ service.
If you still have errors, post the nsclient.log file so we can view it.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked