Dead mirrors

General system Pacman
1

The following errors are appearing each time the mirrorlist is updated:

==> Warning about https://endeavouros.ip-connect.info/repo/$repo/$arch:
    Connection to this mirror failed after 30 seconds.
    Continuing.
==> Warning about https://fastmirror.pp.ua/endeavouros/repo/$repo/$arch:
    Connection to this mirror failed after 30 seconds.
    Continuing.
==> Warning about https://mirror.jingk.ai/endeavouros/repo/$repo/$arch:
    Update level is 2240/2247, some [endeavouros] packages may be outdated if this mirror is in use.
    Continuing.
==> Warning about https://mirrors.c0urier.net/linux/endeavouros/repo/$repo/$arch:
    Connection to this mirror failed after 30 seconds.
    Continuing.

Can anything be done about this? It takes at least extra 90 seconds each time which is very annoying. Maybe consider removing these from mirrorlist?

2

Mirrors go on and off line for a number of reasons. If you are consistently having issues with the same mirrors then you can comment them out of the mirror list.

3

This isn’t going to help with my issue though. endeavouros-mirrorlist package will overwrite the content and still rank these dead mirrors.

4

How often do you need to update your mirrorlist for a repo that doesn’t include a lot of things critical for day to day use? And someone on the development time correct me, but I don’t think this utility ranks these dead mirrors high enough for you to even get them in normal use, if there’s a mirror that is available and has a good enough connection.

5

There is a Hook to rank EndeavourOS mirrors after installing or upgrading the related mirrorlist package
So basically it happens after each endeavouros-mirrorlist upgrade. Maybe that needs to be changed or the timeout needs to set much lower. Something definitely needs to be done about this.

1 Like
6

I see. During my time with EndeavourOS, I haven’t noticed that many updates to the EndeavourOS utilities. I don’t know how often the development team pushes updates to people for these utilities, thus I can’t really say anything else other than perhaps someone else can help you.

7

The issue is YOUR the only one having an issue. What can we do? There may be a number of reason you can not connect ranging from the mirror being offline to the mirror being limited in your country to being completely blocked. Sorry you feel like a minute and a half is a major amount of time out of your schedule however there isn’t anything that can be done.

1 Like
8

Or I am the only one who cared enough to report. So what?

That’s simply not true.

  1. timeout_default can be decreased
  2. These mirrors can be removed from here
  3. Or added here
  4. You tell me.

Something that doesn’t survive the package reinstallation is not good.

That looks plausible. In such case I am NOT the only one having an issue.

So f me, right? This delay is absolutely unnecessary and therefore shouldn’t exist. These mirrors are consistently not working here.

9

It’s not only about update for me. This happens each time that package is installed or reinstalled and, as you might imagine, this will happen a lot during the testing the OS installation. I’m working on EndeavourOS ARM image for WoA laptops and therefore have to reinstall it a lot.

10

There is something you can do in file /etc/eos-rankmirrors.conf:

  1. Add the failing mirrors to array EOS_IGNORED_MIRRORS, something like this (note the partial names):
EOS_IGNORED_MIRRORS=(ip-connect fastmirror jingk c0urier)
  1. Change the value of EOS_AUTORANK_TIMEOUT from 30 to smaller (or larger!)

Hope this helps.

4 Likes
11

Will this survive the eos-rankmirrors package upgrade?

12

Yes, unless you don’t merge possible config changes carelessly. :wink:

13

Wouldn’t this cause the config file to be overwritten? Or will it only happen if it’ll be changed in the package?

14

Do you mean this?

backup=(etc/$pkgname.conf)

That should protect overwriting. pacman creates a .pacnew file instead of overwriting the config file you have changed.

2 Likes
15

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