View previous topic :: View next topic |
Author |
Message |
Gen3Hunna n00b


Joined: 31 Dec 2018 Posts: 29
|
Posted: Sun Jan 09, 2022 10:57 pm Post subject: [Solved] One server causing major issues |
|
|
Hello. I just finished installing Gentoo.
I don't know what my issue is, but every time I've emerged (including during the install) I get errors such as:
"Resolving gentoo.mirrors.pair.com... 216.92.2.140
Connecting to gentoo.mirrors.pair.com|(same IP as above)|:80... failed: Connection timed out.
Retrying."
then it tries the same one again more times and basically seems to just go on to a next server after a certain number of failed attempts.
Is this a common issue? What can I do to fix it? It literally multiplied my installation time by like 8x because every single package did this.. -_- .. Any additional information I can give, just ask.
Last edited by Gen3Hunna on Sun Jan 09, 2022 11:38 pm; edited 1 time in total |
|
Back to top |
|
 |
Hu Administrator

Joined: 06 Mar 2007 Posts: 23326
|
Posted: Sun Jan 09, 2022 11:13 pm Post subject: |
|
|
This is not a standard problem, no. However, bad mirrors happen from time to time. You should be able to suppress a bad mirror by setting GENTOO_MIRRORS explicitly to a list that does not include the bad one. See man make.conf for how to configure it.
As a quick and crude hack, you could add an explicit negative route to that host, so that connection attempts to it fail instantly with No route to host instead of performing a full timeout. Such a route would need to be removed when the host recovered. |
|
Back to top |
|
 |
Etal Veteran


Joined: 15 Jul 2005 Posts: 1932
|
Posted: Sun Jan 09, 2022 11:28 pm Post subject: |
|
|
I suggest finding some fast mirrors near you and put them in your make.conf.
You can use app-portage/mirrorselect to find them: https://wiki.gentoo.org/wiki/Mirrorselect |
|
Back to top |
|
 |
Gen3Hunna n00b


Joined: 31 Dec 2018 Posts: 29
|
Posted: Sun Jan 09, 2022 11:38 pm Post subject: |
|
|
lol thank both of you for your answers. Sometimes it just helps to hear these things stated differently. I did what user Hu suggested, and then mirrorselect will now emerge with all dependencies etc and not trying to contact this bad mirror anymore, no more waiting. I know I don't really need to use mirrorselect now that I have it working but I understand it's helpful to have for future mirror issues.
Thanks, I'll mark this as solved. |
|
Back to top |
|
 |
|