On Wed, Apr 13, 2016, at 03:50, Peter Palfrader wrote: > We can identify at least four causal factors. Probably more, if we > look a bit further. > (1) The scripts Debian uses to mirror repositories treat the mirroring > hierarchy as a tree. The failure of any node or link will cause > the subtrey(s) under the failed component to not receive updates. > (2) There is an ongoing network outage between where the australian > mirror is and its upstream mirror in the US. > (3) The scripts that automatically update the security rotation only > check if a server is online and responds to http requests - it > does not check if a mirror is current. > (4) The nagios warning was missed in all the noise, and the relevant > teams are overworked and busy.
Thank you for that information. If we ever manage to fix (3), this would alleviate most of my worries over a single mirror being returned in the geo-ip RRSET for some areas of the Internet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique de Moraes Holschuh <h...@debian.org>
