You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A node owner reported recently that they did not receive any notifications about a node going down. I am not sure if this was not sent of whether something blocks it being received either by our relay host or their mail server because something looks dodgy.
The text was updated successfully, but these errors were encountered:
I think these emails should go out from sown-monitor.ecs.soton.ac.uk. I can see that monitoring email is still being received from this server as I am on the monitoring alias and have received this email. Postfix is configured on sown-monitor but I cannot find a mail log (/var/log/mail.log is empty nothing is journalctl for postfix) to see what is going wrong.
This may be due to the node owner's email address being broken as it is an alias. They are looking into getting this fix but I have setup a secondary email address that gets notifications for this node. If it goes down again, the node owner should be able to confirm if email notfications are broken or not.
This looks to be down to a to address issue. This has been fixed but will require Ansible changes to ensure local changes are not overwritten. sown/ansible#50
A node owner reported recently that they did not receive any notifications about a node going down. I am not sure if this was not sent of whether something blocks it being received either by our relay host or their mail server because something looks dodgy.
The text was updated successfully, but these errors were encountered: