Ok, I¹ve manage to thoroughly confuse my self with service escalations.
Here is an example of my configs:
--service_definitation:
define service{
use generic-service
host_name box1,box2
service_description
I recently upgraded from Nagios2 to version3, and it¹s running beautifully.
All except for the WAP interface. I¹ve searched the web, and the archives
and haven¹t found anything that might help.
When my users go to the wap interface (which worked GREAT under v2) and try
to acknowledge a problem (e
I was working on this again, and I enabled all notifications for the
hosts/services that we had disabled, and the emails to $ stopped.
As soon as I disabled the notifications again, the emails to $ started. Any
idea?
On 6/16/08 10:14 AM, "ROBERT SMALL" <[EMAIL PROTECTED]> wr
As a new note, I nuked the /var/spool/nagios/dead.letter this morning, and
just looked at it again. The vast majority of emails there (all of 'em
addressed to $) are for hosts/services that we have notifications disabled.
Robert
On 6/14/08 9:35 AM, "ROBERT SMALL" <[EMAIL
No, nothing strange, I sent my contacts to some of the other admins at the
office and they all said they were fine. This is happing on both of my
nagios boxes...
On 6/13/08 3:49 PM, "Marc Powell" <[EMAIL PROTECTED]> wrote:
>
> On Jun 13, 2008, at 1:24 PM, ROBERT SMALL w
s - Network Group
> JELD-WEN, Inc.
> Information Systems
> [EMAIL PROTECTED]
>
>
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of ROBERT SMALL
> Sent: Friday, June 13, 2008 10:44 AM
> To: Nagios Users Mailinglist
> Subject: [Nagios-users] Nagios v3 &a
I have lots of messages in my nagios installation being sent to $.
I have searched my contacts and other configs and cannot find it. We all
get email and notifications but there are the occasional $ emails and I
found em stuck in /var/spool/nagios/dead.letter (freebsd).
Does anyone have any ide
I recently upgraded from Nagios2 to version3, and it¹s running beautifully.
All except for the WAP interface. I¹ve searched the web, and the archives
and haven¹t found anything that might help.
When my users go to the wap interface (which worked GREAT under v2) and try
to acknowledge a problem (e
