Mirror verification failure false positive

[IT Services, University of Oxford]

I am specifically reporting about the mirror verification failure reported in:

> http://launchpadlibrarian.net/331775206/mirror.ox.ac.uk-release-probe-logfile.txt

Since we were contacted about this (On the 5th of August 2017), we have been monitoring the availability of the URLs flagged in the report, and they have always been active and available.

So, I reckon there might have been a network blip at the time the report was run. What puzzles me is why the mirror checking process does not back-off and retry later. Well, there is no clear indication of a retrial

Again, talking to my colleagues, it seems this is not the first time the mirror verification process has failed our Ubuntu mirror, and exactly for the same error of supposedly receiving a 404 response.

We host other mirrors on the same server, with exactly the same infrastructure and no other upstream repository has ever reported hitting a 404 when validating our mirror.

Could this failure be due to something your mirror validation system is doing wrongly ?

Please, can you reactivate this mirror as well ..

[Colin Watson (cjwatson)]

Our mirror prober did retry, and as far as I can tell Launchpad is currently quite happy with your mirror:

  https://launchpad.net/ubuntu/+mirror/mirror.ox.ac.uk-release

Can you explain what makes you think the mirror hasn't been reactivated?

[api.ng (hektve)]

(+),(+1), star()

[Launchpad Janitor (janitor)]

[Expired for Launchpad itself because there has been no activity for 60 days.]