recurring downtime

Julie S. Lin jlin at livescribe.com
Fri May 13 21:56:08 CEST 2011


HI Chris

thanks so much I could have sworn I tried "smtp" vs "SMTP"
but seems to be working now!

  identical service descriptions matter I guess. :)

Julie S. Lin
System Administrator
jlin at livescribe.com
(510) 553 4912 (o)
(510) 367 5772 (c)



On May 13, 2011, at 11:52 AM, Chris Beattie wrote:

> Julie S. Lin wrote:
>>
>> I'm trying to set up recurring downtimes for automatic reboots  Below
>
> Have you considered scheduling host downtime instead?  There's one  
> fewer
> parameter to pass to the script.  I think the service name is the
> tripping point.  I was able to copypaste your command into a shell  
> on my
> Nagios  (with minor mods to work in my environment) and have it work.
>
> My services.cfg contains this:
>
> use                     standard_service
> name                    Disk_C
> service_description     Disk: C
> display_name            Disk: C
> check_command           check_nt_disk!C!85!95
>
> No matter what you use for the service name, it will show up in
> nagios.log.  However, it's only when I use Disk: C that the downtime
> shows up on the web page.  If I use Disk_C it does not.
>
> All the services for which I regularly schedule downtime happen to  
> have
> the same string for their name, service_description, and display_name.
> I didn't need to figure out which one I needed.  However, I did get
> tripped up setting service escalations the first time, because those  
> use
> the service_description and not the name.  It might be the same case  
> here.
>
> -- 
> -Chris
>
> ------
>
>
> Nothing in this message is intended to make or accept an offer or to  
> form a contract, except that an attachment that is an image of a  
> contract bearing the signature of an officer of our company may be  
> or become a contract. This message (including any attachments) is  
> intended only for the use of the individual or entity to whom it is  
> addressed. It may contain information that is non-public,  
> proprietary, privileged, confidential, and exempt from disclosure  
> under applicable law or may constitute as attorney work product. If  
> you are not the intended recipient, we hereby notify you that any  
> use, dissemination, distribution, or copying of this message is  
> strictly prohibited. If you have received this message in error,  
> please notify us immediately by telephone and delete this message  
> immediately.
>
> Thank you.
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> 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


------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
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





More information about the Users mailing list