Ticket #390 (closed defect: invalid)

Opened 20 months ago

Last modified 18 months ago

Server 2008 x64 TBS: Stopped Critical

Reported by: dglose Owned by: mickem
Priority: 1 Milestone: 0.3.7
Component: CheckSystem Version: 0.3.7
Severity: Bugs Keywords:
Cc:

Description

I downloaded and installed v 0.3.8 (x64) which is supposed to fix this issue. I also added "CheckServiceState CheckAll? ignore-perf-data" to the NSC.ini file and I'm still getting this error (however may not have added it in the proper place).

I've attached a copy of NSC.ini.

Attachments

NSC.ini Download (11.6 KB) - added by dglose 20 months ago.

Change History

Changed 20 months ago by dglose

comment:1 Changed 20 months ago by mickem

Humm..

Is it supposed to fix that error? Not sure exactly what your problem is ?

But "CheckServiceState CheckAll?? ignore-perf-data" should not go in the config file.

It should go in your nrpe command line like so:

check_nrpe ... -c CheckServiceState -a CheckAll ignore-perf-data

Michael Medin

comment:2 Changed 20 months ago by dglose

Just to be sure, I uninstalled, then re-installed and I'm still getting the same error.

I am getting this error in the log's however:

2010-06-18 12:37:12: error:modules\NRPEListener\NRPEListener.cpp:393: Request contained arguments (not currently allowed, check the allow_arguments option). 2010-06-18 12:37:12: error:modules\NRPEListener\NRPEListener.cpp:365: NRPEException: Request contained arguments (not currently allowed, check the allow_arguments option).

Where do I change the NRPE command line? FYI, we are also using the same config file from our 2003 Servers (all working great!). Is there anything I can provide you that might help?

Thanks

comment:3 Changed 20 months ago by mickem

Read the nrpe guide: doc/usage/nagios/nrpe

Michael Medin

comment:4 Changed 20 months ago by dglose

Seems I've made another Linux community Faux Pas.

It's been a while since I was instructed to RTFM, which I will do.

I was wrongfully assuming that if a specific bug was thought to be fixed in a new release that the developer would want to know that the issue still remains and might want to figure out why. Especially if there were someone who would be willing to provide any information necessary to resolve it. I apologize for my assumptions. Thank you again.

comment:5 Changed 20 months ago by mickem

*sigh* firstly; sorry if I have offended someone but it is faster for me if you read and I don't spend time explaining things every time someone has a problem.

Secondly; As I tried to explain before I am not aware of which issue you are referring to.

Thirdly; This is not "unix community" in fact it is not even much of a community, mainly me trying to help out. But thus far you have (from what I can see) not provided any information at all.

Again, sorry if I am offensive, not my intention...

Michael Medin

comment:6 Changed 20 months ago by dglose

Michael,

Not offended, just a very busy SysAdmin? and am using your app on over 30 Servers, routers and the like. It's just that we are moving to 2008 and this bug has reared its ugly head. The fact that it was a known issue that was fixed is why I was coming to you. As far as providing you with info....if you tell me what you need, I'll provide it. I'd like this to benefit everyone.

Otherwise, I'll just tell it not to notify me until it gets fixed in future releases.

thank you again. Dave

comment:7 Changed 20 months ago by mickem

Could you give me your exact command? And the returned data (and what you were expecting).

From what I understand "one service" is reported incorrectly?

Also if you could refer me to which issue this was "previously reported as" that might be usefull...

Michael Medin

comment:8 Changed 18 months ago by mickem

  • Status changed from new to closed
  • Resolution set to invalid
  • Milestone set to 0.3.7

Closing since no feedback, reopen if this is an issue...

Note: See TracTickets for help on using tickets.