Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate why node owner (up/down) emails not being received #92

Closed
drn05r opened this issue Mar 14, 2023 · 3 comments
Closed

Investigate why node owner (up/down) emails not being received #92

drn05r opened this issue Mar 14, 2023 · 3 comments
Assignees
Labels
bug Something isn't working monitoring Monitoring of the SOWN network using Icinga or other tools

Comments

@drn05r
Copy link
Member

drn05r commented Mar 14, 2023

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.

@drn05r drn05r added bug Something isn't working monitoring Monitoring of the SOWN network using Icinga or other tools labels Mar 14, 2023
@drn05r drn05r self-assigned this Mar 14, 2023
@drn05r
Copy link
Member Author

drn05r commented Mar 14, 2023

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.

@drn05r
Copy link
Member Author

drn05r commented Mar 14, 2023

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.

@drn05r
Copy link
Member Author

drn05r commented Apr 3, 2023

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

@drn05r drn05r closed this as completed Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working monitoring Monitoring of the SOWN network using Icinga or other tools
Projects
None yet
Development

No branches or pull requests

1 participant