nagios sending recovery emails before critical emails

[Petr Simek]

On Fri, 30 Jul 2004, Guillermo Padilla wrote:

> I don't quite understand what you mean by broken line.....

Some impossibility send email from nagios host to mailserver where Your
INBOX is located. This impossibility may be caused by failure that is
reported in this first email.


*------------------------------------------------------------------------*
|                          Petr Simek   APS JU                           |
|                             psimek at jcu.cz                              |
*------------------------------------------------------------------------*

> On Fri, 30 Jul 2004, Guillermo Padilla wrote:
>
> > I've seen this happen a few times where my nagios server will send a
> > recovery notification email and about 5 mins later it would send a
> > critical email for the same problem.
>
> > The Recovery emails have a timestamp that's after the critical email.
> > But I've just receive the recovery email before the critical.
>
> > Any Ideas why this weird action  happens?
>
> May be - broken line is between Your INBOX (where email is delivered)
> and nagios server. First email with critical message is not delivered
> immediately (line is broken) and is delayed in queue, next message with
> recover message is delivered immediately - line is OK. Then after some
> time is sent first message from mail queue .
>
> > -Guillermo

> |                          Petr Simek   APS JU





-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Nagios-users mailing list
Nagios-users at 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