> Mirror maintainer confirmed very quickly that it was a hiccup they were
> dealing with
Yup, as we already noticed, the trouble had already stopped for several
hours, in total opposition of observed behavior observed until then.
Good to have formal confirmation things are back to normal! Thx for
Final update on this so it doesn't stay "open" forever:
On dc., jul. 17 2019, Evilham wrote:
On dc., jul. 17 2019, Bernard Rosset via Dng wrote:
b) If not and this a confirmed defect, would not it be
reasonable to
remove said host from the pool until the maintainer can inspect
what is
going
On dc., jul. 17 2019, Bernard Rosset via Dng wrote:
Thx Evilham for your answer. Glad it was not sinkholed ;o)
Not at all :-).
But maybe it'll be interesting to add simple monitoring at a
connection
level same way you ran your tests.
I'll try to setup a thing in the next couple days.
I wa
Thx Evilham for your answer. Glad it was not sinkholed ;o)
> FWIW: I've been running "while; curl; sleep 30" as a similar test for a
> good few minutes now and it's been solid.
Yup, as I stated before in my report, nothing wrong had been detected
since 1100Z, ie almost 6h ago.
I have been using
Hello,
On dc., jul. 17 2019, Bernard Rosset via Dng wrote:
After I stumbled, by chance, on mirror 141.84.43.19 (being part
of the
deb.devuan.org pool) being unavailable for a couple of minutes,
I set a
script up checking TCP/80 availability for all of mirrors in
said pool.
The conclusion is
After I stumbled, by chance, on mirror 141.84.43.19 (being part of the
deb.devuan.org pool) being unavailable for a couple of minutes, I set a
script up checking TCP/80 availability for all of mirrors in said pool.
The conclusion is clear:
1°) 141.84.43.19 is the only mirror suffering from this pr
