Feature #15159
Monitoring of our mirrors' ability to sync
0%
Description
After uploading Tails 3.4 it was discovered that something is broken on the Tor Project’s side, in our mirroring setup. To prevent these last minute mirror problems about syncing, I wonder if we could add some simple monitoring. For instance: at the start of each day our rsync server creates a file with (with predictable name, e.g. today’s date), and later in the day we check that each mirror has this expected file.
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2018-01-10 |
History
#1 Updated by anonym 2018-01-09 14:14:59
- Assignee set to bertagaz
- Target version set to Tails_3.5
Does this make sense? (Setting a target release just so the ticket isn’t lost)
#2 Updated by intrigeri 2018-01-09 15:53:30
As suggested on XMPP earlier today I think we should get rid of the torproject part of our mirroring rsync chain. Once this is done we have a subset of this monitoring for free since we already monitor our rsync server. I’ll start a discussion with the mirrors & sysadmin teams about this later.
#3 Updated by intrigeri 2018-01-10 11:26:28
- related to
Bug #15162: Remove rsync.torproject.org from the mirrors synchronization chain added
#4 Updated by anonym 2018-01-23 19:52:54
- Target version changed from Tails_3.5 to Tails_3.6
#5 Updated by bertagaz 2018-03-14 11:32:28
- Target version changed from Tails_3.6 to Tails_3.7
#6 Updated by intrigeri 2018-04-29 07:53:52
- Status changed from Confirmed to Rejected
- Assignee deleted (
bertagaz)
intrigeri wrote:
> As suggested on XMPP earlier today I think we should get rid of the torproject part of our mirroring rsync chain.
We’re going to do it (Bug #15162).
> Once this is done we have a subset of this monitoring for free since we already monitor our rsync server.
Once Bug #15162 is done, I think the monitoring we already have is good enough so I’m rejecting this. Let’s reopen if we ever notice a problem that our existing monitoring does not catch.