I've read the help docs, like I said I have a working installation checking about 15 servers. I have a PING service that pings a host group. I can't do that with this because I'm checking a different string on each site, so i'm guessing it has to be separated out. Does this make sense?
<br><br><div><span class="gmail_quote">On 11/2/07, <b class="gmail_sendername">Hari Sekhon</b> <<a href="mailto:hpsekhon@googlemail.com">hpsekhon@googlemail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You need to reread the docs, this is the most basic of questions.<br><br><a href="http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#service">http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#service</a><br><br>
Hint: You are missing a service_description in the last block for one.<br>You should not have name in that last block either, you need host_name.<br><br>Read docs pls.<br><br>-h<br><br>Hari Sekhon<br><br><br><br>Jerad Riggin wrote:
<br>> I have a functioning nagios setup but I have a quick question. I am<br>> going through and adding website string checks so we can keep track of<br>> availability on one of our webservers.<br>><br>> So in
services.cfg I have<br>><br>> define service{<br>> name generic-service ; Generic<br>> service name<br>> active_checks_enabled 1 ; Active<br>
> service checks are enabled<br>> passive_checks_enabled 1 ; Passive<br>> service checks are enabled/accepted<br>> parallelize_check 1 ; Active
<br>> service checks should be parallelized (Don't disable)<br>> obsess_over_service 1 ; We should<br>> obsess over this service (if necessary)<br>> check_freshness 0 ; Default is
<br>> to NOT check service 'freshness'<br>> notifications_enabled 1 ; Service<br>> notifications are enabled<br>> event_handler_enabled 1 ; Service
<br>> event handler is enabled<br>> flap_detection_enabled 1 ; Flap<br>> detection is enabled<br>> process_perf_data 1 ; Process<br>> performance data
<br>> retain_status_information 1 ; Retain<br>> status information across program restarts<br>> retain_nonstatus_information 1 ; Retain<br>> non-status information across program restarts
<br>> register 0 ; DONT<br>> REGISTER THIS DEFINITION - NOT A REAL SERVICE, JUST A TEMPLATE!<br>> }<br>><br>> define service{<br>> use generic-service
<br>> name basic-service<br>> is_volatile 0<br>> check_period 24x7<br>> max_check_attempts 5<br>> &
nbsp; normal_check_interval 3
<br>> retry_check_interval 1<br>> notification_interval 15<br>> notification_period 24x7<br>> register 0<br>> }
<br>><br>> I then have as just one example:<br>><br>> define service{<br>> use basic-service<br>> name check-site4<br>> notification_options w,u,c,r
<br>> check_command check_http!site.com!20!"Home"<br>> register 0<br>> }<br>><br>><br>> My question is, you notice that I have the name as check-site4, and
<br>> then later on in the services.cfg I call up that checksite-4. Is this<br>> the correct way? Do I need to define a service for each host and then<br>> later on call it by name to execute the service check? Is this a bad
<br>> way of going about it?<br>><br>> Thanks,<br>><br>> Jerad<br>> ------------------------------------------------------------------------<br>><br>> -------------------------------------------------------------------------
<br>> This SF.net email is sponsored by: Splunk Inc.<br>> Still grepping through log files to find problems? Stop.<br>> Now Search log events and configuration files using AJAX and a browser.<br>> Download your FREE copy of Splunk now >>
<a href="http://get.splunk.com/">http://get.splunk.com/</a><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> Nagios-users mailing list
<br>> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users
</a><br>> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>> ::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br>