Unusable EOS mirror server

Probably the wrong category again, may the purple Linux demon haunt me at night :imp: :

For some time now, the following two EOS mirror servers have always been broken. Not that I would miss one of them, but it always takes a while for the mirror server list ranking to jump over. So, is this art or can it go away?

==> eos-rankmirrors: info: fetching https://gitlab.com/endeavouros-filemirror/PKGBUILDS/-/raw/master/endeavouros-mirrorlist/endeavouros-mirrorlist ...
==> eos-rankmirrors: info: ranking EndeavourOS mirrors, please wait ...
==> Warning about https://mirror.albony.xyz/endeavouros/repo/$repo/$arch:
Connection failed.
Continuing.
==> Warning about https://mirror.nimatarlani.com/endeavouros/repo/$repo/$arch:
Connection failed.
Continuing.
==> eos-rankmirrors: info: fetching https://gitlab.com/endeavouros-filemirror/PKGBUILDS/-/raw/master/endeavouros-mirrorlist/endeavouros-mirrorlist ...
==> eos-rankmirrors: info: ranking EndeavourOS mirrors, please wait ...
==> Warning about https://mirror.nimatarlani.com/endeavouros/repo/$repo/$arch:
    Connection failed.
    Continuing.

I always have the mirror.nimatarlain one fail. Never had an issue with mirror.albony, as far as I know.

1 Like

I only get the one failed and then it finishes.

==> eos-rankmirrors: info: extracting /var/cache/pacman/pkg/endeavouros-mirrorlist-24.3-1-any.pkg.tar.zst ...
==> eos-rankmirrors: info: ranking EndeavourOS mirrors, please wait ...
==> Warning about https://mirror.nimatarlani.com/endeavouros/repo/$repo/$arch:
    Connection failed.
    Continuing.
==> Info: Results of ranking EndeavourOS mirrors:

Sometimes some mirrors fail for various reasons, they may be in maintenance mode or some other temporary issue with networking.

That’s why a mirrorlist file contains several mirrors. If the first mirror in the list fails, the next one will be used. If that fails too, the next in the list will be used, and so on.

eos-rankmirrors gives a warning about each mirror that fails to give a proper answer within a timeout. In most cases the warnings can be simply ignored. Only if all mirrors fail, there will be a problem. :wink:

File /etc/eos-rankmirrors.conf is a place where user can configure many things for eos-rankmirrors.
For example, to exclude selected mirrors from ranking, one can add (partial) names of mirrors into the array variable EOS_IGNORED_MIRRORS:

EOS_IGNORED_MIRRORS=(
   albony
   nimatarlani
)

Then those mirrors will not be ranked at all, and they will not give warnings either.

Another somewhat related config variable is EOS_AUTORANK_TIMEOUT with which user can specify how long time each mirror is allowed to take to return its answer.

1 Like

OK, then forget it. I just thought that feedback about faulty mirrors might be of interest to someone.

It is interesting of course, thanks for posting! :+1:

If a mirror is permanently failing, we will contact them, and possibly remove the mirror from our list if they don’t want to be a mirror anymore.

2 Likes

I had something like that in mind …

https://nimatarlani.com

main Dom is reachable it is only the mirror subdomain that has issues.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.