When replication fails and e-mail reporting is set, an e-mail about failed replication is sent every minute
When replication fails and e-mail reporting is set, an e-mail about failed replication is sent every minute.
This happened to me last night, generating 1020 e-mails for 3 datasets.
If I don't react to 3 or 6 e-mails, does it make sense to send another 1000+?
I think it would be reasonable to send 1 or 2 e-mails for an event, and then stop - sending more e-mails seems pointless to me.
Happens on FreeNAS-9.3-STABLE-201502142001
#1 Updated by Bidule0hm _ over 6 years ago
I'll just add the link to the original thread: https://forums.freenas.org/index.php?threads/replication-failed-email-notification-appear-once-a-minute.26417/
#3 Updated by Mieszko Ślusarczyk over 6 years ago
This is what I was getting for every replication task, every minute (3 tasks = 3 emails a minute):
The replication failed for the local ZFS (dataset name) because the command:
/usr/bin/ssh -i /data/ssh/replication -o BatchMode=yes -o StrictHostKeyChecking=yes -o ConnectTimeout=7
have returned an error code of 255
#7 Updated by Jan Örnstedt over 6 years ago
How about making a consolidation option. I.e let the admin choose how frequent he wants to get error messages. I.e Instant, Hourly, Daily, Weekly.
This would make life easier for low risk installs where it is not urgent to fix certain issues.
Perhaps consolidation per error category.
#8 Updated by Mieszko Ślusarczyk over 6 years ago
I agree the options are sometimes good - but why would you want to be notified every minute about one issue? If you would - something is wrong about your e-mail management, and you should pay more attention, about flagging/notifications for e-mails. There's no use for 1000 e-mails notifying you about the same problem, if you dnon't read them...
THis bug makes this notification system unusable, so I had o turn it off (and turn to reminders about checking system status manually).
#13 Updated by Josh Paetzel almost 5 years ago
- Status changed from Closed: Not To Be Fixed to Investigation
- Assignee changed from Wojciech Kloska to Josh Paetzel
- Seen in changed from to 9.3-STABLE-201505040117
So here's my take on that.
Since we can all agree that FreeNAS 10 is a ways away, and FreeNAS 9 isn't going anywhere for the time being, let's let the FreeNAS 9 team fix bugs in FreeNAS 9 that really make life miserable for people using FreeNAS 9 right now.
#25 Updated by Bartosz Prokop over 3 years ago
- Status changed from Screened to Closed: Not Applicable
After discussing this with my colleagues it looks like the snap/repl alert emails are now resent every hour.
Furthermore we're planning implementing the custom alerts filter/rules - I've attached a ticket number.
Considering facts above this ticket seems to be redundant.