nrpe CheckEventLog

[Mark Elsen]

> Thanks for the reply.
>
> I fear the main problem here is the lack of knowledge that's sat in-between my chair and my pc :)
>
> I've edited the ini file on the server to allow both arguments and nasty chars and restarted the service.
>
> If I use the -a switch after -c checkEventLog all I get back is 'CHECK_NRPE: Received 0 bytes from daemon... blah, blah blah...'
>
> To me, that's suggests something isn't right on my windows server end, but what?
>
>

 As far as NSC config file on windows server 2003 is concerned I have :

;# COMMAND ARGUMENT PROCESSING
;  This option determines whether or not the NRPE daemon will allow
clients to specify arguments to commands that are executed.
allow_arguments=1
;
;# COMMAND ALLOW NASTY META CHARS
;  This option determines whether or not the NRPE daemon will allow
clients to specify nasty (as in |`&><'"\[]{}) characters in arguments.
allow_nasty_meta_chars=1


  For the rest this, probably, only, means that there is a syntax
conflict pending. Trial and error should lead to pinpointing the
problem
  Als remember the versioning issue.


M.

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null