I'll probably do away with the time exclusion as it still isn't working. I have one service that went critical during the exclusion which has a 24x7 check but 4-5:30 notification exclusion and now I can't make it send a notice. I disabled notifications for that service and enabled again; also restarted Nagios and still won't send a notice. It's configured to send on the second attempt and every hour after.
Current Status: CRITICAL (for 0d 3h 19m 46s) Status Information: HTTP CRITICAL: HTTP/1.1 503 Service Temporarily Unavailable Performance Data: Current Attempt: 2/2 (HARD state) Last Check Time: 08-26-2008 07:49:16 Check Type: ACTIVE Check Latency / Duration: 0.077 / 0.078 seconds Next Scheduled Check: 08-26-2008 07:52:16 Last State Change: 08-26-2008 04:31:10 Last Notification: N/A (notification 0) Is This Service Flapping? NO (0.00% state change) In Scheduled Downtime? NO Last Update: 08-26-2008 07:50:51 ( 0d 0h 0m 5s ago) Active Checks: ENABLED Passive Checks: ENABLED Obsessing: ENABLED Notifications: ENABLED Event Handler: ENABLED Flap Detection: ENABLED -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Angliss Sent: Monday, August 25, 2008 7:29 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] checks,notifications don't work after time period exception On Mon, 25 Aug 2008 13:38:28 -0400, "Seth Simmons" <[EMAIL PROTECTED]> wrote: >The system date is correct and Nagios is showing the correct day and >time on the status page. If I stop Nagios, I don't see any other Nagios >processes running. The two templates here have not been touched. I >looked at both and have 24x7 for all times which is the default. I just >modified the time definitions as you have it listed and I'll see what >happens tonight. There are also no custom time settings in nagios.cfg; >all the settings related to time zone, etc are commented out. I had a similar issue. I tried excluding a time slot between 0300, and 0600 due to large DB loads causing website performance issues (backups, indexing, and such). When the start of the exception rolled around, nagios would just stop checking that service, and would only restart on a forced manual check, or restart of the nagios service. I ended up changing the theory to continue checking 24x7, but only alert when outside the exception. Not that it helps the issue, but it stopped the symptoms. I never got around to really digging into the issue any deeper. It did give me the added benefit of knowing when the server was actually down during the maintenance window, and when it was just being slow. This was handy for management purposes so they could calculate if they need more head count. -- Jon Angliss ------------------------------------------------------------------------ - 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 ------------------------------------------------------------------------- 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
