I have a "call home" script that detects an
errpt -a -1 -"Error on Hostname" type of entry into file errpt.dta and sends a copy of that file to a Qmail Server in a mailer.dta file.
Here's my problem - If a hardware error occurs in the "errpt" on ClientA the email is sent as it should to the Qmail Server - however, if the problem isn't resolved and the "monitoring" happens again - the repetitive message is sent to the Qmail Server.
How can we disseminate an actual "new, real" error from the "old, repeated" error? For instance, if a system has ssa disks and one of the disks fail - the error is reported, the cron tests again for any new messages and again sees the pdisk failure - We need a way to ignore that "old, repeated" message and only send a "new, real" error message if one exists.
I checked the FAQs and other posts but nothing seems to address this.
I can furnish all or parts of the script(s) if you need.
errpt -a -1 -"Error on Hostname" type of entry into file errpt.dta and sends a copy of that file to a Qmail Server in a mailer.dta file.
Here's my problem - If a hardware error occurs in the "errpt" on ClientA the email is sent as it should to the Qmail Server - however, if the problem isn't resolved and the "monitoring" happens again - the repetitive message is sent to the Qmail Server.
How can we disseminate an actual "new, real" error from the "old, repeated" error? For instance, if a system has ssa disks and one of the disks fail - the error is reported, the cron tests again for any new messages and again sees the pdisk failure - We need a way to ignore that "old, repeated" message and only send a "new, real" error message if one exists.
I checked the FAQs and other posts but nothing seems to address this.
I can furnish all or parts of the script(s) if you need.