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
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.
Heya
I am running Nagios with snmptraps being caught in the usual
passive/volitile check method.
The big downside with this setup is that those traps will never clear. I
have to manually submit a passive check to clear them, which is
annoying.
So I want to build an active check that I can use t
Heya All
Running Nagios 2.0b6. (yes I know I should upgrade, but I tweaked the
CGI's and am too lazy to have to re-do all my tweaks when I upgrade)
Management is concerned about people acking problems, and then
forgetting about them. They also prefer emails to looking at the GUI. So
what I have
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
ho
Title: Service time out immediately sets hard state?
Heya
Running Nagios 2.0b6.
I have a service check that runs fine most of the time, but occasionally (about once a day) the check takes too long to run, and hits the Service check timeout limit.
It appears that hitting this limit is tr
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, yo
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-es
why is recommended to keep it off unless you really know what you are
doing.
> -Original Message-
> From: Ivan Fetch [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 23, 2006 12:37 PM
> To: Andrew Laden
> Cc: nagios-users@lists.sourceforge.net
> Subject: RE: [Nagios-users] Difficulty
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)
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.
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.
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
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 th
> > > > > 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
> -Original Message-
> From: Steve Shipway [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 17, 2006 4:08 PM
> To: 'Andrew Laden'; nagios-users@lists.sourceforge.net
> Subject: RE: [Nagios-users] Disabling GIF image for passive checks
>
> > > W
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Marc Powell
> Sent: Tuesday, January 17, 2006 3:46 PM
> To: nagios-users@lists.sourceforge.net
> Subject: RE: [Nagios-users] Disabling GIF image for passive checks
>
>
>
> > -Original Messa
I had a similar problem with passive checks and freshness
checking when I upgraded to 2.0. I am guessing (though no one ever responded
when I asked the list before) That they changed the logic. Before a stale check
would trigger an active check in all cases regardless of the check period. Now
?
From: Andrew Laden
[mailto:[EMAIL PROTECTED] Sent: Thursday, December 08, 2005
11:06 AMTo: nagios-users@lists.sourceforge.netSubject:
[Nagios-users] Passive service freshness check syntax
Did the methodology for passive service freshness
checks change at some point.
I have my
Title: Passive service freshness check syntax
Did the methodology for passive service freshness checks change at some point.
I have my config set up as
Check_period none
passive_checks_enabled 1
Active_checks_enabled 1
Which if I recall was to allow active c
When the parent dies (actaully gets a sigkill from the nagios stop) it
forwards that signal to all its children. You need to ignore that signal in
your script. How you do it depends on the shell.
"man trap" for more info.
> -Original Message-
> From: enrico fanti [mailto:[EMAIL PROTECT
21 matches
Mail list logo
