-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Earl, Bob
Sent: Wednesday, June 30, 2004 08:13
To: '[EMAIL PROTECTED]'
Subject: RE: [WhatsUp Forum] Alerts failed??As usual, I leave out important stuff - my notifications normally work great. In fact, the UP messages went out about 35 minutes later, causing quite a bit of confusion since the DOWN messages didn't make it.So other than getting "lucky" while testing, there isn't a way to find out what went wrong?Bob Earl
EDS - North Carolina Medicaid
4905 Waters Edge
Raleigh, NC 27606
Phone:919-816-3085
mailto:[EMAIL PROTECTED]-----Original Message-----
From: Mark Symons [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 29, 2004 5:29 PM
To: [EMAIL PROTECTED]
Subject: RE: [WhatsUp Forum] Alerts failed??Try this...Open your debug log and then open your Notification library and test the notification. Sure, you won't get any % variables resolving, but you'll see the important stuff such as a 550 response from the server. (550 would indicate invalid mailbox, meaning you should check the address used - but there are other failure responses as well).Mark SymonsIpswitch, IncAugusta GA-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Earl, Bob
Sent: Tuesday, June 29, 2004 15:15
To: [EMAIL PROTECTED]
Subject: [WhatsUp Forum] Alerts failed??Question - I just found a number of alert failures in my log, that look like this:
20040629 135356 Alert failed process N:3Com Switch F:768 A:SMTPMail/NetMonEmailOnly
20040629 135336 Alert failed process N:Router F:768 A:SMTPMail/NetMonEmailOnly
...I've checked the server's event logs, and nothing correlates with the failure times.
I've never seen these before, and as far as I know, the SMTP server it was trying to connect with was up and running - is there a way I can get more info about the failures?
Bob Earl
EDS - North Carolina Medicaid
4905 Waters Edge
Raleigh, NC 27606
Phone:919-816-3085
mailto:[EMAIL PROTECTED]
Title: Message
There
are errors that can cause transient failures. A full mailbox would be
an example... explaining an alert that worked last week, does not work
today, but starts working again tomorrow. Whatever the real
cause, it's likely to lie on the mailserver side and that's why the debug
log is important.
You
are correct in pointing out that this gives you the problem of needing to be
lucky when testing. Sure, you can write the debug log to disk
and then sit back until you get a failure in normal operation... but that might
result in gigabytes being logged before you hit paydirt.
The
causes of failure should be written to the Event log and I have updated the
existing defect in our database with your details.
Mark
Symons
Ipswitch, Inc
Augusta GA
- [WhatsUp Forum] Alerts failed?? Earl, Bob
- RE: [WhatsUp Forum] Alerts failed?? Mark Symons
- RE: [WhatsUp Forum] Alerts failed?? Earl, Bob
- RE: [WhatsUp Forum] Alerts failed?? Mark Symons
- RE: [WhatsUp Forum] Alerts failed?? Earl, Bob
- RE: [WhatsUp Forum] Alerts failed?? Szilveszter Csanyi
