Re: [Nagios-users] Question on Distributed Setup for hosts & hostgroups

2010-10-01 Thread Steven Kreuzer

On Oct 1, 2010, at 3:56 PM, steve f wrote:

> I am building a package to send out to 500 locations to set up a distributed 
> Nagios 3.2 environment.
> 
> I have scripts written that when the nagios package is dropped in a location, 
> the script creates a hosts.cfg & a hostgroup.cfg file on the remote 
> distributed server for the hosts he will monitor.
> 
> I just want to be 100 % sure that if  the central server is not doing active 
> checks, does the central server still have to have every remote host listed 
> in its hosts.cfg and the hostgroup.cfg files?

It does otherwise the central server won't know what to do with the check 
results that it receives.

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Nagios-users mailing list
Nagios-users@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

[Nagios-users] Time period Oddity

2009-05-26 Thread Steven Kreuzer
I have run into an issue regarding time periods and I am completely  
stumped.

I have created a time period called market-hours that goes from 9:30am  
to 4pm. In addition, I created a time period called market-holidays  
that contain a list of days that the stock market is closed. I  
excluded the
market-holidays timeperiod from the market-hours time period.

I have a series of checks that I want executed only during when the  
stock market is open. I added a new check into nagios, and its being  
scheduled for tomorrow at 9:30am. I took out the exclude portion
of the market-hours time period and then the new check gets scheduled  
to be checked without 5 minutes of the current time.

This is nagios 3.0.6
A copy of the relevant sections of the config can be found at: 
http://pastebin.com/me1941f5

Has anyone seen this issue before?

Also, can someone explain that the difference is between "name" and  
"timeperiod_name"? The documentation and example config seem to both  
make reference to the "name" directive for timeperiod
but it doesn't seem to be documented anywhere.

Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer


--
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
___
Nagios-users mailing list
Nagios-users@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


[Nagios-users] Alerting behavior at beginning of timeperiod

2009-02-26 Thread Steven Kreuzer
I have several processes that are started each morning from cron and  
then run until the early evening and are then killed.

For example, every weekday at 8:00am, a daemon is started and it runs  
until 6:30pm. A timeperiod of this particular process has been created
so between 08:00 and 18:30, nagios uses nrpe to check to make sure the  
process is in the process list and if not, it sends out an alert. For  
the
most part it works exactly as expected with the exception of the alert  
that is thrown in the morning.

I have been getting an alert each day that is timestamped a couple of  
seconds after 8:00am (Today was sent out at 8:00:06)
My guess as to what happens is that at exactly 8am the first check is  
done and the process might not have been fully started, or cron
started it a few seconds after the check is done.

However, I have nagios setup so that normal checks are scheduled to be  
performed every 5 minutes. If a check fails, another check is scheduled
for 1 minute after the first failed check and then if that check  
fails, an alert is sent out.

Nagios appears to be ignoring that. My guess as to what happens is  
that if the first check at the start of a timeperiod fails, it  
immediately sends out a alert. The issue seems to have
gone away after I changed the timeperiod to begin at 8:01am but I  
wanted to pick the brain of the community to see if this is an  
expected behavior or
something I need to look into more closely.

Many Thanks

--
Steven Kreuzer
http://www.exit2shell.com/~skreuzer


--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Alternating Notification Commands

2008-12-02 Thread Steven Kreuzer
I am trying to avoid that because it seems like it would get fairly  
difficult to manage and makes
the config alot more difficult to read, especially if you happen to  
have a whole bunch of
people who need to receive alerts.

But from what I can tell, this looks like the only possible solution

On Dec 2, 2008, at 2:41 PM, Seth Simmons wrote:

> You want to configure Nagios to send alerts by email during the day by
> sms the rest of the time?
> Why don't you just create 2 separate contact definitions, one for  
> email
> and one for sms with different time definitions?
>
> Would look something like this:
>
> define contact{
>   contact_namesysadmin-1
>   use generic-contact
>   alias   sysadmin workhours
>   host_notification_periodworkhours
>   service_notification_period workhours
>   host_notification_options   d,r
>   service_notification_optionsw,c,r
>   email   [EMAIL PROTECTED]
>   }
>
> define contact{
>   contact_namesysadmin-2
>   use generic-contact
>   alias   sysadmin after work
>   host_notification_periodafterwork
>   service_notification_period afterwork
>   host_notification_options   d,r
>   service_notification_optionsw,c,r
>   email   [EMAIL PROTECTED]
>   }
>
> define timeperiod{
>   timeperiod_name workhours
>   alias   Normal Work Hours
>   monday  08:00-16:59
>   tuesday 08:00-16:59
>   wednesday   08:00-16:59
>   thursday08:00-16:59
>   friday  08:00-16:59
>   }
>
> define timeperiod{
>   timeperiod_name afterwork
>   alias   Normal Work Hours
>   monday  17:00-24:00
>   tuesday 17:00-24:00
>   wednesday   17:00-24:00
>   thursday17:00-24:00
>   friday  17:00-24:00
>   saturday00:00-24:00
>   sunday  00:00-24:00
>   }
>
> define service{
>   use local-service
>   hostgroup_name  Linux
>   service_description Load Average
>   check_command   check_nrpe!check_load
>   max_check_attempts  2
>   check_interval  10
>   retry_interval  5
>   check_period24x7
>   notification_interval   60
>   first_notification_delay0
>   notification_period 24x7
>   contacts
> sysadmin-1,sysadmin-2
>   notification_optionsc,w,r
>   }
>
> As far as certain services sms only, use the 24x7 time period, create
> contact for the 24x7 time period and configure the service  
> accordingly.
>
>
> define contact{
>   contact_namesysadmin-3
>   use generic-contact
>   alias   sysadmin sms
>   host_notification_period24x7
>   service_notification_period 24x7
>   host_notification_options   d,r
>   service_notification_optionsw,c,r
>   email   [EMAIL PROTECTED]
>   }
>
> define service{
>   use local-service
>   hostgroup_name  linux
>   service_description Free Space on /
>   check_command   check_nrpe!check_root
>   max_check_attempts  2
>   check_interval  15
>   retry_interval  5
>   check_period24x7
>   notification_interval   60
>   first_notification_delay0
>   notification_period 24x7
>   contactssysadmin-3
>   notification_optionsc,w,r
>   }
>
> The way that is configured, any problems with load in your linux
> hostgroup will send notification by email during the day and by sms
> after hours/weekends.  The second example will send by sms at any time
> for any alerts with free space.
>
>
> -Original Message-
> From: Steven Kreuzer [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 2, 2008 2:08 PM
> To: nagios-users@lists.sourceforge.net

[Nagios-users] Alternating Notification Commands

2008-12-02 Thread Steven Kreuzer
Greetings-

In addition to the two included commands for sending notifications, I  
defined two new ones called notify-host-by-sms and notify-service-by- 
sms.

What I would like to do is configure nagios to have it send alerts by  
email during normal business hours and send alerts by sms the rest
of the time. I would also like to configure certain critical services  
to only alert by sms regardless of the time of day.

 From what I can tell, there does not appear to be a straight forward  
way to do this because "host_notification_commands" and  
"service_notification_commands" are defined under "contact". It looks  
like I would have to
create two contacts for each person, one with their email and one with  
their pager.

Is there any way around this?

Thanks

Steven Kreuzer
http://www.exit2shell.com/~skreuzer


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Nagios-users mailing list
Nagios-users@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