[Nagios-users] Nagios and DST changes

2007-02-07 Thread Andrew Laden 
Heya all.

 With the Daylight savings time change changing this year in the US,
management is going through a y2k style check of all our applications to
make sure that they wont have any issues when DST occurs in the middle
of march rather then the end.

I think that Nagios stores all its date info in seconds from Unix Epoch,
so the timezone should not affect anything (assuming that the underlying
OS has been patched with the new TZ info.

Can anyone thing of anywhere in Nagios that might break with the Time
zone change?

Thanks

-Andrew
-- 
_
This communication is intended only for the addressee(s) and may contain 
confidential information. We do not waive any confidentiality by misdelivery. 
If you receive this communication in error, any use, dissemination, printing or 
copying is strictly prohibited; please destroy all electronic and paper copies 
and notify the sender immediately.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
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] removing acknowledge comments associated with theservices or host from nagios

2007-01-26 Thread Andrew Laden 
I have a script that loads in the status and comments.dat file, and
looks for any services that are OK, that have acknowlege comments
associated with them, and the give the option to delete.

I don't consider this ready for prime time, so I havent thought about
putting it up on nagios exchange yet. But you are free to try to adapt
it.

Rename to complean.tar.gz, Unzip, untar, edit for your paths, and run
comclean.pl

-Andrew 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf 
 Of ankush grover
 Sent: Friday, January 26, 2007 9:14 AM
 To: Nagios Users Mailinglist
 Subject: [Nagios-users] removing acknowledge comments 
 associated with theservices or host from nagios
 
 hi friends,
 
 I have configured Nagios 2.6 in a Production Environment. 
 There are about 200 servers and about 1000 services which are 
 being monitored by nagios.
 
 I want to remove acknowledge comments associated with the 
 hosts or services  is there any command through which I can 
 achieve this.
 
 
 Thanks  Regards
 
 
 Ankush Grover
 
 --
 ---
 Take Surveys. Earn Cash. Influence the Future of IT Join 
 SourceForge.net's Techsay panel and you'll get the chance to 
 share your opinions on IT  business topics through brief 
 surveys - and earn cash 
 http://www.techsay.com/default.php?page=join.phpp=sourceforge
 CID=DEVDEV
 ___
 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
 
-- 
_
This communication is intended only for the addressee(s) and may contain 
confidential information. We do not waive any confidentiality by misdelivery. 
If you receive this communication in error, any use, dissemination, printing or 
copying is strictly prohibited; please destroy all electronic and paper copies 
and notify the sender immediately.
‹nºEcomplean.taríXQoÛ6Ϋõ+®²‹Ù­+‰“I“vH¼-XÛ[EMAIL 
PROTECTED];æ?·ýgcËÙÝÝk;ûíý=ßj;;Û΃Yd´¹ŒÝUºSw(üÕ|·ÑimÇѓjß¿¡Óª­¹ŒZ—žß
E4µª–œ_B!e—žËþț
XX•ÙÔkÔiBm(.çãÁëþ¡eU‚PøPÿéìM§6óØ
zì×ÿ!fQˆÀˆŠíЪ0òk!ÞK9ÆÑÁ4¨wÈ
O'$†zC÷¥ˆ{¡†ôX'®œ¨^m±—L])ñ;Œ?»‹Û{þ¦Aö|¼‘žòŒ‚H¸ƒ  
ÔÙº-BUšl•Á$˜…ôዯLj}¬¶–û=ù¬ÆCØ«·ê½îóôµƒVRkØ84ZY™7§R©e
[Ü'|úHR`ÔóœÁ{GõÍg–¶9ům‘ìö0(äIøâxQÛJ˜a%ø³^’·ù7å-´†Â£«¢ÕUèøCF Å 
ö?u0a2ý=;ñ7Ø´ÙvƒÕð®}WdÉľï΄0~¶z¸[¼—ì*$S´'ŠÄ…ÈÃ4NJ˜ÊœÚÇr–¸7˜¢Y.¯Y4F(ä
 òBZ€3òڌ{À¢vù¤R_5/M_0”½ÆäØz/qNç³ÐãÁ¾Ü …
{7ŽÜÙ‚BspøÝÿ„dºÚâ«Ph7·¯¬(w9¡9pÁ_ 
Oâwv:„x‚´8Ž¼Ëy,¤¥ò©OŒÌ§ƒ;5G€Œ¤Ý9Ɏ?:æªÃ‰xaTëqäi[EMAIL PROTECTED]
¯¡¥`[ ªè˜u“œAå8rsT.”‹Ñw°)‹ß«–è–h^»)¶™‹C%q_;)Ý{VÈ   éô†fpÕ5CY°^
]–LÒCW{WâÔÒÃVH6é¡y¾^ÚZúNÒȚZòãc”i…Bf.I•p.é
.J •’˜’£©`YIÀÚZy÷ýiçâãäÅÅùŋ4ˆ«üÊ¿ÞuDò†Œ¦ÓWRÜ뒡•)[EMAIL 
PROTECTED]m©²¶Ôi{mŸZžäݪ˜è—ËH7ädäÚ¾%ˋ
÷ÊÐïɽ²J‡×ùÞ=,«{V®q®¦¹›³PºgMâÈ5Ê­5•²ÐþmuX ¬*+0•Ôh¦YIVˆõŒêë/ÌÉV¿ßywÚï[Ö÷¾Fÿo.é`*\3œ˜zÿÙßÝ]õþÓnïîñûÏîþöΎ³Cï?;û8öøþóð­ú$ÿTµ¬9˜ŸE„ñÁÁ›ÀÇØO#¾~*ÄsG©t¤­ŠùJtt
vë³µ¦Á¸…^ [EMAIL PROTECTED]   YÒÕ[EMAIL PROTECTED]
)—V²Äf*‹/ƒê
™Mºõ•²Õ
µÙqI“!g꩛–è;çµ6ª
[EMAIL PROTECTED]
µBÁýÖ¥À/çÝ÷]Ìù‡e£´¶ªË 
ŠAג”è]Îò˜Hâþč†l¿è®?ÆùÂKÜ©Œ÷òfÞPƒ„§ÌϕIz!ÊWôFE鵞AgåƊh11ó:
pñNxf#xmØ^V£)6^Ȕjª0Òëlm€uGý6]YѺ¹óx·LE   „`  ‘®%‰7þ¯`M7ρk
x3r¶i€Óãï2Y¾ºõ‰lJR
P®Kó#ƒæçëöܟ¢§¡÷²$®l[•réRѺ(»Êe:u¬7”™¸~2ðx–´Ÿ,Íù¦NÂMåtv#}eÔÀjýz‘ÇykÀ“pþk¾2M¨ 
°2énçâÃÙIçgÖ'c]6Ø×ué줯åՆ‚orì2¹;úö-Pî}«{½»ûá䞜›^Z?/²qG 'Þ(Ö/uzþéVw!fÁgñ
[EMAIL PROTECTED]'!ÂÆØ+ôîõ¯ggïè!1­ÈùŠÃÄ õñªån¡wŽþ²=ÌÈJûOþ§7ýڂ
Mú'çoßvÞ½?¤™ØËëfÁB^I¼Ðe
i#èijφcàÊA†X“¤µƒúÛD–’KŽ¾FoyÙ¬`uVŽ0ß»Z{lí±=¶ûkÿøNx-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
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] controlling notifications a bit better

2006-08-09 Thread Andrew Laden 



One thing to watch is that HOST alerts will get sent 
out as soon as the host is detected down. You can play with the retry settings. 
But you generally need to keep those short, as a host check supercedes all other 
checks, and nagios will essentially pause until it determines status of the 
host.

You can also play with escalations to delay checks. 
Have no notifications initially, and then use an escalation to send the alert 
later. This takes a little work to get right.


  
  
  From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Aaron 
  SeguraSent: Wednesday, August 09, 2006 12:09 PMTo: 
  nagios-users@lists.sourceforge.netSubject: Re: [Nagios-users] 
  controlling notifications a bit better
  
  
  Normal check 
  interval: 5 min
  Retry Check 
  interval : 5 min
  Max check attempts 
  : 2
  
  -or-
  
  Normal check 
  interval: 2 min
  Retry check 
  interval: 1 min
  Max check 
  attempts: 9
  
  -or- 
  
  
  (This is the one I 
  run on some services)
  Normal check 
  interval: 5 min
  Retry check 
  interval : 1 min
  Max check attempts: 
  6
  
  
  Something along those 
  lines should do itYay for math!
  
  
  
  
  
  From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Gavin CatoSent: Wednesday, August 09, 2006 12:47 
  AMTo: 
  nagios-users@lists.sourceforge.netSubject: [Nagios-users] controlling 
  notifications a bit better
  
  Hi,
  
  I want certain hosts/services to 
  only send an email alert if the host/service is down for 10 
  minutes.
  
  Ive tried playing with 
  max_check_attempts and the other obvious parameters but I still get email 
  alerts after only 1-2mins.
  
  Can anyone please show me a sample 
  config snippet or how they do it?
  
  Cheers
  
  Gav
  
  
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
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] escalations for passive checks?

2006-06-01 Thread Andrew Laden 
Escalations are based entirely on alert received/processed by nagios,
not on time.

For active checks, the time factors control how often the service is
checked, and therefore how often an alert is sent to nagios. 
For passive checks, this obviously doesn't hold.

If you want to get around this, you can try to craft an active check
that gets the current status of the item, and repeats it back to
nagios, thus creating another alert. I've never tried this though. 

 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf 
 Of Joel Brooks
 Sent: Thursday, June 01, 2006 4:21 PM
 To: nagios-users@lists.sourceforge.net; [EMAIL PROTECTED]
 Subject: [Nagios-users] escalations for passive checks?
 
 Hi list
 
 
 
 
 
 
 
 i'm messing around with passive checks so that i can integrate sec.pl=
   into nagios to make use of nagios' notification/escalation 
 capabilities .=
 
   it seems to me that nagios will only send one notification for=
   each passive check that gets added to the external commands file.=
 
   i had thought that it would use the whole notification/escalation=
   process after receiving a single CRITICAL event, but it doesn't=
   seem to do that.
 
 
 
 
 
 
 
 here's what i did:
 
 
 
 
 
 
 
 -defined a service (for testing) called 'passive':
 
 
 
 define service{
 
 
 
 use generic-service
 
 
 
 host_name   admin
 
 
 
 service_description passive
 
 
 
 is_volatile 1
 
 
 
 contact_groups  production-support
 
 
 
 notification_optionsw,u,c,r
 
 
 
 notification_interval   5
 
 
 
 max_check_attempts  1
 
 
 
 check_command   check_ping
 
 
 
 active_checks_enabled   0
 
 
 
 passive_checks_enabled  1
 
 
 
 }
 
 
 
 
 
 
 
 -define escalations for this service:
 
 
 
 define serviceescalation{
 
 
 
 host_name   admin
 
 
 
 service_description passive
 
 
 
 contact_groups  production-support
 
 
 
 first_notification  2
 
 
 
 last_notification   0
 
 
 
 notification_interval   5
 
 
 
 escalation_period   24x7
 
 
 
 escalation_options  w,u,c,r
 
 
 
 }
 
 
 
 
 
 
 
 define serviceescalation{
 
 
 
 host_name   admin
 
 
 
 service_description passive
 
 
 
 contact_groups  production-support,application-support
 
 
 
 first_notification  5
 
 
 
 last_notification   0
 
 
 
 notification_interval   5
 
 
 
 escalation_period   24x7
 
 
 
 escalation_options  w,u,c,r
 
 
 
 }
 
 
 
 
 
 
 
 define serviceescalation{
 
 
 
 host_name   admin
 
 
 
 service_description passive
 
 
 
 contact_groups  production-support,application-support
 
 
 
 first_notification  7
 
 
 
 last_notification   0
 
 
 
 notification_interval   3
 
 
 
 escalation_period   24x7
 
 
 
 escalation_options  c,r
 
 
 
 }
 
 
 
 
 
 
 
 -submit_passive_check:
 
 
 
 #!/bin/bash
 
 
 
 
 
 
 
 echocmd=/bin/echo
 
 
 
 cmdfile=/opt/nagios/var/rw/nagios.cmd
 
 
 
 datetime=`date +%s`
 
 
 
 cmdline=[$datetime] PROCESS_SERVICE_CHECK_RESULT;$1;$2;$3;$4
 
 
 
 `$echocmd $cmdline  $cmdfile`
 
 
 
 
 
 
 
 then the test:
 
 
 
 ./submit_passive_check admin passive 2 1
 
 
 
 
 
 
 
 this gets logged, and an alert goes out, but no further notifications=
   are sent.  escalations don't do anything because there is never=
   a second notification.
 
 
 
 
 
 
 
 if i do this:
 
 
 
 while true; do
 
 
 
  sleep 300
 
 
 
  echo 'submitting passive check...'
 
 
 
  ./submit_passive_check admin passive 2 1
 
 
 
 done
 
 
 
 
 
 
 
 then the notifications work as expected, and the escalations apply.
 
 
 
 
 
 
 
 why doesn't nagios continue to send notifications (and escalations)=
   after the single CRITICAL (non-OK state) event gets logged?  i'm=
   sure this is just my own confusion..
 
 
 
 
 
 
 
 nagios rox btw... great tool!
 
 
 
 
 
 
 
 thx,
 
 
 
 
 
 
 
 - Joel Brooks (joel.brooks)
 
 
 
 
 
 
 
 ---
 
 
 
 The mailing list archive is found here:
 
 
 
 http://www.nagiosexchange.org/nagios-users.34.0.html
 
 
 
   
 
 
 
 
 ---
 All the advantages of Linux Managed Hosting--Without the Cost 
 and Risk!
 Fully trained technicians. The highest number of Red Hat 
 certifications in the hosting industry. Fanatical Support. 
 Click to learn more
 http://sel.as-us.falkag.net/sel?cmd=lnkkid7521bid$8729dat1642
 ___
 Nagios-users mailing list

RE: [Nagios-users] is my syntax ok for escalation?

2006-04-19 Thread Andrew Laden 
Depends on what you are trying to accomplish. The syntax is fine assuming
nagios isnt complaining about it. What problem are you seeing?

What you have
Notify admins (1)
Wait 240 min (4 hours)
Notify admins (2)
Wait 240 min (4 hours)
Notify admin-escalate (3)
Wait 90 min (1.5 hours)
Notify admin-escalate (4)
Wait 90 min
Repeat to 10.
Notify admin-escalate (10)
Wait 90 min
Notify admin (11)
Wait 240 min
Repeat till the world ends.

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf 
 Of Tom Cruickshank
 Sent: Tuesday, April 18, 2006 10:35 PM
 To: nagios-users@lists.sourceforge.net
 Subject: [Nagios-users] is my syntax ok for escalation?
 
 Hello,
I'm trying to get escalation working on a service I have running.
 This is what I currently have.
 
 define serviceescalation{
 host_name   web3.host.com
 service_description Bacula Process
 first_notification  3
 last_notification   10
 notification_interval   90
 contact_groups  admin-escalate
 }
 
 define service{
 use generic-service
 host_name   web3.host.com
 service_description Bacula Process
 is_volatile 0
 check_period24x7
 max_check_attempts  3
 normal_check_interval   5
 retry_check_interval2
 contact_groups  admins
 notification_interval   240
 notification_period 24x7
 notification_optionsw,u,c,r
 check_command   check_nt_bacula!192.168.1.5
 }
 
 I know that the contact_groups 'admin-escalate' works since I 
 tried it in define service for contact_groups and it worked fine.
 
 Is there anything that I might of missed in defining my 
 serviceescalation?
 
 Would appreciate any assistance. Thanks!
 
  Tom
 
 
 --
 No virus found in this outgoing message.
 Checked by AVG Free Edition.
 Version: 7.1.385 / Virus Database: 268.4.4/318 - Release 
 Date: 4/18/2006
  
 
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting language
 that extends applications into web and mobile media. Attend 
 the live webcast
 and join the prime developer group breaking into this new 
 coding territory!
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720;
 dat=121642
 ___
 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
 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
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] Check_http with size and regex conditions ignoring size check.

2006-02-23 Thread Andrew Laden 
Title: Check_http with size and regex conditions ignoring size check.





I want to check a web page, and check both for a regex and for a minimum size.


However, it appears that the regex requirement overides the size. Eg. (names changes to protect the innocent)
check_http (nagios-plugins 1.4.1) 1.81


[EMAIL PROTECTED] check_http -H servername -p 8080 -u uri -r REGEX CHECK -m 60:100
HTTP OK HTTP/1.1 200 OK - 0.420 second response time |time=0.419695s;;;0.00 size=2405B;60;0;0


[EMAIL PROTECTED] check_http -H servername -p 8080 -u uri -m 60:100
HTTP WARNING: page size 2405 too large|size=2405B;60;0;0


Is this a bug in check_http?


-Andrew

RE: [Nagios-users] Difficulty with wildcards in serviceescalation

2006-02-21 Thread Andrew Laden 
There is a documentation error. You have to use real regex. A naked * by
itself is not a valid regex.

Try .*

-Andrew 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf 
 Of Ivan Fetch
 Sent: Monday, February 20, 2006 5:25 PM
 To: nagios-users@lists.sourceforge.net
 Subject: [Nagios-users] Difficulty with wildcards in serviceescalation
 
 Hello,
 
 
 I'm having difficulties with wildcards in a 
 serviceescalation, running nagios 2.0-stable.  It seems like 
 the documentation discusses doing exactly this, so perhaps my 
 trying to get this to work last minute is causing me to 
 overlook something...  Any ideas?
 
 
 # Limit notifications to a max of 5, the last one notifying everyone.
 define serviceescalation{
 host_name   *
 service_description *
 first_notification 5
 last_notification 0
 notification_interval 0
 contact_groups everyone
 }
 
 
 
 When verifying the config I get:
 
 Reading configuration data...
 
 Error: Could not find any host matching '*'
 Error: Could not expand hostgroups and/or hosts specified in 
 service escalation (config file 
 '/usr/local/nagios/etc/du/services.cfg', starting on line 154)
 
 
 
 I have this set in /usr/local/nagios/etc/nagios.cfg:
 use_regexp_matching=1
 use_true_regexp_matching=0
 # ... at the end of the file ...
 cfg_dir=/usr/local/nagios/etc/du
 # (which is where the services.cfg is read, which is where the 
 #serviceescalation is defined)
 
 
 
 Thanks,
 
 Ivan Fetch.
 '
 
 
 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep 
 through log files for problems?  Stop!  Download the new AJAX 
 search engine that makes searching your log files as easy as 
 surfing the  web.  DOWNLOAD SPLUNK!
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486;
dat=121642
 ___
 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
 


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
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] What did we recover from?

2006-02-03 Thread Andrew Laden 
Title: What did we recover from?





Is there some macro that we can use when a recovery alert was sent out to indicate what we recovered from? I.E. Warning, or Critical?

I am writing my own notification module, since the notification and escalation rules that nagios provides don't meet my needs. (I need much finer control of who gets noitified for what.)

The problem I am having is how to avoid sending recovery pages to people who didn't get the problem pages. I want to be stateless, so I can't track who was sent the page. The idea is to determine what level the recover is for (ie, critical or warn), see if the user would have gotten a page for that service/problem level, and if so, send the recovery page. 

I was thinking of playing with the $LASTSERVICE*$ macros, but cant figure out an algorithm that will work for both the 
OK - CRIT - OK, case and the OK - WARN - CRIT - WARN - OK case, vs the OK - WARN - OK case.


Any ideas?


-Andrew

RE: [Nagios-users] Nagios Escalations

2006-02-02 Thread Andrew Laden 
 Bringing it back to the list

 -Original Message-
 From: Jason Coleman [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, February 01, 2006 2:13 PM
 To: Andrew Laden
 Subject: RE: [Nagios-users] Nagios Escalations
 
 My apologies. I would like the groups listed in the 
 escalations contact_groups to be notified. However, they 
 never are in the current configuration that I have provided. 
 The initial alert is delivered to the group listed in the 
 service definition and that is it. From the outside, it 
 appears that nagios is not escalating the notification. 
 
 
 
Read your definiton. Are you waiting 12 hours for the 2nd escalation. I
think the notification interval of 720 may be the issues.

Notification 1 - linux engineers
720 minutes (12 hours)
Notification 2 - Linux Engineers
720 Minutes ( 12 hours)
Notification 3 - linux-engineers,network-engineers,windows-engineers
12 minutes
Notification 4 - big list
12 minutes.
Repeat to 1000

 
 -Original Message-
 From: Andrew Laden [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, February 01, 2006 10:18 AM
 To: Jason Coleman
 Subject: RE: [Nagios-users] Nagios Escalations
 
 Might help to say what errant behavior you are seeing. 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf 
 Of Jason 
  Coleman
  Sent: Wednesday, February 01, 2006 12:32 PM
  To: nagios-users@lists.sourceforge.net
  Subject: [Nagios-users] Nagios Escalations
  
  I am currently having trouble getting our escalations to 
 work. I have 
  read the documentation and tried experimenting with nagios, but I 
  still cannot get nagios to observe the escalation rules. Here is my 
  service definition that I am testing with:
  
  Service definition:
  
  define service{
  namegeneric-checkhttp
  use generic-service
  service_description Check HTTP
  is_volatile 0
  check_period24x7
  max_check_attempts  3
  normal_check_interval   1
  retry_check_interval1
  notification_interval   720
  contact_groups  linux-engineers
  notification_period 24x7
  notification_optionsw,u,c,r
  check_command   check_http
  register0
  }
  
  And here is the escalation definition:
  
  define serviceescalation{
  host_name   wwdw23img01
  service_description Check HTTP
  first_notification  3
  last_notification   1000
  notification_interval   12
  contact_groups
  linux-engineers,network-engineers,windows-engineers
  }
  
  Any help would be appreciated. Please let me know if I have 
 left out 
  information that is needed to assist.
  
  
  
  Jason Coleman
  Systems Engineer
  LRN - The Legal Knowledge Company
  1100 Glendon Ave, Suite 700
  Los Angeles, CA 90024
  tel: 310-209-5381
   
  /(bb|[^b]{2})/
  
  
  
  
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep 
 through log
 
  files for problems?  Stop!  Download the new AJAX search 
 engine that 
  makes searching your log files as easy as surfing the  web. 
  DOWNLOAD 
  SPLUNK!
  http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
  ___
  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
  
 


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
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: *** Detected as Spam *** Re: [Nagios-users] Disabling GIF ima ge for passive checks

2006-01-17 Thread Andrew Laden 
 With active checks enabled the icon is not presented. The
check_period
 of 'none' prevents them from actually being executed 
 by the host 
 receiving the passive checks.

That will also have the by-product of blocking freshness
   checks from
running, which are generally a good thing with passive checks.
   
   Not the case.  Freshness checks are run no matter what the 
   check_period and active_checks_enabled settings.  We use the 
   'check_period none' method here, and freshness checks 
 (resetting to 
   unknown is nothing in the last 10 mins) are definitely running. 
   (Nagios 1.2)
   
  
  That changed in 2.0 and up. (as per a recent mail thread)
 
 Well this method solves my GIF issue, but now I am confused 
 about the freshness checks. The online docs seem to indicate 
 that I want freshness checks on the central server to ensure 
 my distrubuted servers haven't failed or for some other 
 reason are not passively reporting. What am I missing here? 
 I'm running 2.0b5. Thanks.
 
In order for freshness checks to work in 2.0 and up, you have to set as
follows.
check_period 24x7
passive_checks_enabled   1
active_checks_enabled0 ; these are all passive checks
check_freshness  1
check_commandcheck-freshness-stale!Service report
not received within time period 
freshness_threshold  1800 ; Set your own number here

(My check-freshness-stale returns 2, and send the arg as the string.)

This is a change in 2.0 and up. In 1.x, A freshness check would be run even
of the service was outside the check period. In 2.x the freshness check will
only be run if the service is in its check period.

This means you will get the annoying gif in the status.cgi. Such services
being critical will also not show up in the tac cgi as an unhanded problem,
but rather as a disabled problem. For GUI users, this can be very
misleading. I hacked the tac.cgi to have them show up as unhandled problems.




---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
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] 2.0 upgrade, passive checks problem

2006-01-17 Thread Andrew Laden 
 Ethan...

 For some reason, these changes didn't get documented 
 previously. Here are the changes to freshness checking in 2.0:
 
 1.  The freshness_threshold must be non-zero if the 
 normal_check_interval option is zero.
 

What does a normal_check_interval of 0 mean/do? Does that mean that a
service wont be checked? If so, then this may solve the passsive freshness
check and annoying icons issue. 


 2.  Freshness checks can only occur during times that are 
 valid for the check_period timeperiod.
 
 Hope that helps.  I've just updated the documentation.


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
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