FS#45556 - {archweb} Allow automated sending of mirror issue notification

Attached to Project: Arch Linux
Opened by Florian Pritz (bluewind) - Saturday, 04 July 2015, 21:12 GMT
Last edited by Kristian (klausenbusk) - Monday, 05 June 2023, 17:42 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'd like to be able to automate detection and handling of out of date or inaccessible mirrors, but the current APIs don't provide all the necessary information.

I'd like the following additional features:
- a link to each protocols status page (example: https://www.archlinux.org/mirrors/kernel.org/212/) e.g. in this json (https://www.archlinux.org/mirrors/kernel.org/json/). The link is in the HTML version of the page.
- the contact emails for a mirror
- a way to append info to the notes field of a mirror

The last two items are private information so they should use some form of authentication.
This task depends upon

Closed by  Kristian (klausenbusk)
Monday, 05 June 2023, 17:42 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please report upstream if this is still relevant: https://github.com/archlinux/aurweb.
Comment by Florian Pritz (bluewind) - Saturday, 24 June 2017, 15:47 GMT
Talking about this on IRC lead to the conclusion that it would be easier to just integrate the mail sending directly into archweb. Thus the changes above are not needed, but there needs to be some service that monitors the mirror check data and sends notifications like this:

- notify about "out of sync" if the lastsync time is older than 72hours
- notify about "unreachable" if the lastsync file could not be fetched for 24hours
- notify if the lastupdate file is 72 hours older than the lastupdate file on our master mirror

A potential improvement is to be able to set the timeouts for each mirror on their own (some mirrors sync every minute so 1 hour delay might be more appropriate than 72).

If a tier 1 mirror is unreachable or out of sync, tier 2 mirrors that use this mirror should NOT receive emails about being out of sync. There is a field in the database that records the source mirror for tier 2 mirrors, but this field is often not correct due to mirrors changing their upstream without notifying us.

Templates for the email texts can be found here: https://git.server-speed.net/users/flo/bin/tree/generate-mirror-mail.pl
Comment by Florian Pritz (bluewind) - Friday, 22 June 2018, 20:07 GMT
Current mail generation script: https://git.server-speed.net/users/flo/arch-mirror-tools/tree/bin/generate-mirror-mail.pl

Loading...