<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-GB link=blue vlink=purple> <div class=Section1> Considering this command is looking for “check_dummy” should I remove this then as it isn’t required? From what I have read of the documentation of this Nagios Appender. There is no plugin required for it as it is all done via jboss and through NSCA. I could be wrong on this matter as I find the documentation isn’t very clear.... <o:p></o:p> <o:p> </o:p> Thanks<o:p></o:p> <o:p> </o:p> Raymond<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: jonathan.wheeler@stfc.ac.uk [mailto:jonathan.wheeler@stfc.ac.uk] Sent: 25 March 2010 10:28 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Nagios Appender 1.5.1<o:p></o:p> </div> </div> <o:p> </o:p> The check_command for “define host” is the command used to check that the host is alive; this is not a default for service checks which require (usually) their own individual check_command.<o:p></o:p> <o:p> </o:p> Jonathan Wheeler e-Science Centre Rutherford Appleton Laboratory<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Raymond Setchfield [mailto:raymond.setchfield@seewhy.com] Sent: 25 March 2010 10:06 To: 'Nagios Users List' Subject: Re: [Nagios-users] Nagios Appender 1.5.1<o:p></o:p> </div> </div> <o:p> </o:p> Hi Jonathan<o:p></o:p> <o:p> </o:p> This part has also been added into nagios called VirtualHost.cfg<o:p></o:p> <o:p> </o:p> define host{<o:p></o:p> host_name production<o:p></o:p> alias production<o:p></o:p> address 127.0.0.1 ; we really don't care what the host ip is, because we're monitoring a 'virtual' server<o:p></o:p> notifications_enabled 0 ; Host notifications are not enabled<o:p></o:p> event_handler_enabled 0 ; Host event handler is not enabled<o:p></o:p> flap_detection_enabled 1 ; Flap detection is enabled<o:p></o:p> failure_prediction_enabled 1 ; Failure prediction is enabled<o:p></o:p> process_perf_data 1 ; Process performance data<o:p></o:p> retain_status_information 1 ; Retain status information across program restarts<o:p></o:p> retain_nonstatus_information 1 ; Retain non-status information across program restarts<o:p></o:p> notification_period workhours ; Send host notifications only during working hours<o:p></o:p> #notification_period 24x7 ; Send host notifications at any time<o:p></o:p> notification_period none ; Send host notifications never<o:p></o:p> active_checks_enabled 0 ; Active service checks are enabled<o:p></o:p> check_period 24x7 ; By default, Linux hosts are checked round the clock<o:p></o:p> check_command check_dummy ; This is a no-op plugin ... we aren't planning on using it<o:p></o:p> max_check_attempts 1 ; Check each Linux host 10 times (max)<o:p></o:p> notification_interval 120 ; Resend notification every 2 hours<o:p></o:p> notification_options d,u,r ; Send notifications about warning, unknown, critical, and recovery events<o:p></o:p> contact_groups server_admin ; Notifications get sent to the admins by default<o:p></o:p> }<o:p></o:p> <o:p> </o:p> define hostgroup{<o:p></o:p> hostgroup_name terminal<o:p></o:p> alias West Coast Production<o:p></o:p> members production<o:p></o:p> }<o:p></o:p> <o:p> </o:p> define service{<o:p></o:p> name virtual-passive-service ; The name of this service template<o:p></o:p> use generic-service ; Inherit default values from the generic-service definition<o:p></o:p> check_period none ; The service can be checked at any time of the day<o:p></o:p> is_volatile 0 ; The service is not volatile<o:p></o:p> max_check_attempts 1 ; Re-check the service up to 4 times in order to determine its final (hard) state<o:p></o:p> normal_check_interval 1 ; Check the service every 5 minutes under normal conditions<o:p></o:p> retry_check_interval 1 ; Re-check the service every minute until a hard state can be determined<o:p></o:p> contact_groups server_admin ; Notifications get sent out to everyone in the 'admins' group<o:p></o:p> notifications_enabled 1 ; Service notifications are enabled<o:p></o:p> notification_options w,u,c,r ; Send notifications about warning, unknown, critical, and recovery events<o:p></o:p> notification_interval 1 ; Re-notify about service problems every hour<o:p></o:p> #notification_period workhours ; Send host notifications only during working hours<o:p></o:p> notification_period 24x7 ; Notifications can be sent out at any time<o:p></o:p> retain_status_information 1 ; Retain status information across program restarts<o:p></o:p> retain_nonstatus_information 1 ; Retain non-status information across program restarts<o:p></o:p> check_freshness 0 ; Default is to NOT check service 'freshness'<o:p></o:p> freshness_threshold 1 ;<o:p></o:p> event_handler_enabled 0 ; Service event handler is enabled<o:p></o:p> flap_detection_enabled 1 ; Flap detection is enabled<o:p></o:p> failure_prediction_enabled 1 ; Failure prediction is enabled<o:p></o:p> process_perf_data 1 ; Process performance data<o:p></o:p> register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Thanks<o:p></o:p> <o:p> </o:p> Raymond<o:p></o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: jonathan.wheeler@stfc.ac.uk [mailto:jonathan.wheeler@stfc.ac.uk] Sent: 25 March 2010 09:54 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Nagios Appender 1.5.1<o:p></o:p> </div> </div> <o:p> </o:p> Well, there is no check_command defined in the configuration you have posted, but that also depends on the template virtual-passive-service.<o:p></o:p> <o:p> </o:p> Jonathan Wheeler e-Science Centre Rutherford Appleton Laboratory<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Raymond Setchfield [mailto:raymond.setchfield@seewhy.com] Sent: 25 March 2010 09:26 To: 'Nagios Users List' Subject: Re: [Nagios-users] Nagios Appender 1.5.1<o:p></o:p> </div> </div> <o:p> </o:p> Hi Robert & Martin<o:p></o:p> <o:p> </o:p> Here is the full config file from the HelloWorld.cfg<o:p></o:p> <o:p> </o:p> <o:p> </o:p> define service{<o:p></o:p> use virtual-passive-service<o:p></o:p> host_name production<o:p></o:p> service_description HelloWorldApplication<o:p></o:p> active_checks_enabled 0<o:p></o:p> passive_checks_enabled 1<o:p></o:p> normal_check_interval 5<o:p></o:p> retry_check_interval 3<o:p></o:p> check_period 24x7<o:p></o:p> contact_groups server_admin<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Thanks for your help<o:p></o:p> <o:p> </o:p> Raymond<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Robert Wolfe [mailto:rwolfe@i-evolve.com] Sent: 24 March 2010 18:00 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Nagios Appender 1.5.1<o:p></o:p> </div> </div> <o:p> </o:p> Perhaps if you could post the entire service definition.<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Raymond Setchfield [mailto:raymond.setchfield@seewhy.com] Sent: Wednesday, March 24, 2010 1:02 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Nagios Appender 1.5.1<o:p></o:p> </div> </div> <o:p> </o:p> Hi Folks<o:p></o:p> <o:p> </o:p> I am trying to follow the documentation on the Nagios Application Monitoring and I am having a few issues which if someone could help me resolve. I have copied the files VirtualHost.cfg and HelloWorld.cfg into my objects folder and pointed nagios.cfg to look at them. I have altered the files to suit my requirements etc. <o:p></o:p> <o:p> </o:p> Whilst doing the pre-flight checks it is flagging up an error; <o:p></o:p> <o:p> </o:p> Error: Service description, host name, or check command is NULL<o:p></o:p> Error: Could not register service (config file '/usr/local/nagios/etc/objects/HelloWorld.cfg', starting on line 16)<o:p></o:p> Error processing object config files!<o:p></o:p> <o:p> </o:p> When checking line 16 of the HelloWorld it is this;<o:p></o:p> <o:p> </o:p> define service{<o:p></o:p> <o:p> </o:p> This appears to me that there is nothing wrong with it at all, but for some reason Nagios doesn’t like it. Can someone please help me on why this isn’t working? Or possibly point me in the direction of some documentation on how to install this Appender properly? <o:p></o:p> <o:p> </o:p> Many Thanks<o:p></o:p> <o:p> </o:p> Raymond <o:p></o:p> </div> <o:p> </o:p> -- Scanned by iCritical. <o:p></o:p> <o:p> </o:p> </div> <o:p> </o:p> -- Scanned by iCritical. <o:p></o:p> <o:p> </o:p> </div> </body> </html>