NSClient++ Help (#1) - EventLogCheck? - mental disconnect (#541) - Message List
Sorry but I am just hitting a brick wall trying to get this setup.
In the nsc.ini I have
alias_event_log=CheckEventLog file=application file=system filter=new filter=out MaxWarn=1 MaxCrit=1 filter-generated=<2d filter-severity==success filter-severity==informational truncate=1023 unique descriptions "syntax=%severity% : %source%: %message% (%count%)"
If I run that using "nsclient++ /test" I get a result set that ends with eventlog: 7 > critical|'eventlog'=7;1;1;
So, on the command line of my nagios server I run:
/usr/lib/nagios/plugins/check_nrpe -H IP -t 10 -n -p 5666 -c CheckEventLog -a file=application file=system filter=new filter=out MaxWarn=1 MaxCrit=1 filter-generated=\<2d filter-severity==success filter-severity==informational truncate=1023 unique descriptions "syntax=%severity%: %source%: %message% (%count%)"
And get: error: TermDD: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client. (4), warning: EventLog?: The system uptime is 877811 seconds. (3), eventlog: 7 > critical|'eventlog'=7;1;1;
Cool beans.
Now I make the service definition
define service{
use generic-service host_name SomeHostSomeWhere? service_description EventLogChecker? check_command check_nrpeCheckEventLog!file=application file=system filter=new filter=out MaxWarn=1 MaxCrit=1 filter-generated=\<2d filter-severity==success filter-\
severity==informational truncate=1023 unique descriptions "syntax=%severity%: %source%: %message% (%count%)" "file=application file=system filter=in MaxWarn=1 MaxCrit=1 filter+generated=\<2d truncate=900 unique descriptions""
}
After restarting Nagios all I get is a socket timeout on the webpage and the nsclient.log shows: Could not read a full NRPE packet from socket, only got: 69
If someone could point out where I'm screwing it up that would be appreciated.
-
Message #1705
I would start with the guide doc/usage/nagios and make sure everything is correct.
off the top of my head it seems something is wrong in relation to the protocol. So could be SSL/NON SSL/payload_length/* issues maybe?
// Michael Medin
mickem04/14/10 13:35:44 (5 months ago)








