I can see the rational behind this (although 2 days inactive, I think, is a bit premature
for this kind of measure).
But I agree with Ján, that at least the admin should be notified.
R's
Sami
----- Original Message -----
From: "Ján ONDREJ (SAL)" <ondrejj(a)salstar.sk>
To: "Adrian Reber" <adrian(a)lisas.de>
Cc: "Sami Ait Ali Oulahcen" <sami(a)marwan.ma>,
mirror-admin(a)lists.fedoraproject.org
Sent: Thursday, March 19, 2020 9:15:47 AM
Subject: Re: Mirror not re-enabled automatically
On Thu, Mar 19, 2020 at 08:55:46AM +0100, Adrian Reber wrote:
On Wed, Mar 18, 2020 at 03:43:00PM -0700, Kevin Fenzi wrote:
> On Wed, Mar 18, 2020 at 11:45:35AM +0100, Sami Ait Ali Oulahcen wrote:
> > Hi,
> >
> > Basically what the title says. Mirror's been disabled due to downtime, but
> > hasn't been re-enabled (automatically) after being back up.
> > Is this normal behavior ?
>
> How did you disable it?
>
> We have a crawler that looks at mirrors and adds or removes them from
> rotation based on if they are up to date or not. If you didn't do
> anything, normally the crawler would drop your mirror if it was down or
> out of date and then re-add it back after it was up/synced.
> Is the mirror synced up?
The crawler is actually disabling mirrors which are not active for a few
days via User_Active. If a mirror has been disabled like this it will
have a corresponding comment in the comment field and needs to be
manually enabled again. We added this a couple of years ago to not try
to scan really old and unmaintained mirrors.
This sounds reasonably, but also our mirror (ftp.upjs.sk) has been disabled
this way years ago.
It's OK, but mirror admin should be reported about this.
At least mirrormanager client script reports this?
Jan ONDREJ (SAL)