Unable to retrieve mirrors [SOLVED]

MichaelRpdx · 2020-06-20 03:49:43

The messages:

root@tent michael]# pacman -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirrors.kernel.org : Could not resolve host: mirrors.edge.kernel.org
error: failed retrieving file 'core.db' from mirrors.kernel.org : Could not resolve host: mirrors.kernel.org
error: failed retrieving file 'core.db' from ca.us.mirror.archlinux-br.org : Could not resolve host: ca.us.mirror.archlinux-br.org
error: failed retrieving file 'core.db' from mirror.lty.me : Could not resolve host: mirror.lty.me
error: failed retrieving file 'core.db' from mirrors.cat.pdx.edu : Could not resolve host: mirrors.cat.pdx.edu
core 133.6 KiB 3.53 MiB/s 00:00 [####################################################] 100%
error: failed retrieving file 'extra.db' from mirrors.kernel.org : Could not resolve host: mirrors.edge.kernel.org
error: failed retrieving file 'extra.db' from mirrors.kernel.org : Could not resolve host: mirrors.kernel.org
error: failed retrieving file 'extra.db' from ca.us.mirror.archlinux-br.org : Could not resolve host: ca.us.mirror.archlinux-br.org
error: failed retrieving file 'extra.db' from mirror.lty.me : Could not resolve host: mirror.lty.me
error: failed retrieving file 'extra.db' from mirrors.cat.pdx.edu : Could not resolve host: mirrors.cat.pdx.edu
extra

This error occurs after an extended, 24 hours+, of time on linux 5.7.3 on a VPS system. On this system the hwclock is wanderring. The fix is to upgrade to 5.7.4.

That symptom:
[root@tent michael]# for i in 1 2 3 4 ; do hwclock -r ; sleep 1 ; done
2020-04-30 09:06:32.351278-07:00
2020-06-25 16:36:26.447690-07:00
2020-06-20 20:05:58.085588-07:00
2020-06-20 12:19:58.073129-07:00
[root@tent michael]#

What is needed to get the mirrors resolveable by pacman?

Last edited by MichaelRpdx (2020-06-20 16:18:00)

jasonwryan · 2020-06-20 03:53:30

1. Use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

2. Can you ping/reach other sites, or is it just mirrors? I would imagine the former, which makes it a networking issue, not mirror-specific.

MichaelRpdx · 2020-06-20 03:59:06

ah, well yes. I cannot ping reliably:

[root@tent michael]# ping mirrors.kernel.org
ping: mirrors.kernel.org: Temporary failure in name resolution

[root@tent michael]# ping -c 1 google.com
ping: google.com: Temporary failure in name resolution

[root@tent michael]# ping -c 1 google.com
PING google.com(sea30s02-in-x0e.1e100.net (2607:f8b0:400a:803::200e)) 56 data bytes
ping: Warning: time of day goes back (-332163071842us), taking countermeasures
64 bytes from sea30s02-in-x0e.1e100.net (2607:f8b0:400a:803::200e): icmp_seq=1 ttl=121 time=251658213 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 251658213.422/251658213.422/251658213.422/0.000 ms
[root@tent michael]#

so, yes, it is a temporary failure

jasonwryan · 2020-06-20 04:09:22

jasonwryan wrote:

1. Use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code.

Then, fix your networking.

MichaelRpdx · 2020-06-20 04:20:48

To fix my posting problem:

The messages:

root@tent michael]# pacman -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirrors.kernel.org : Could not resolve host: mirrors.edge.kernel.org
error: failed retrieving file 'core.db' from mirrors.kernel.org : Could not resolve host: mirrors.kernel.org
error: failed retrieving file 'core.db' from ca.us.mirror.archlinux-br.org : Could not resolve host: ca.us.mirror.archlinux-br.org
error: failed retrieving file 'core.db' from mirror.lty.me : Could not resolve host: mirror.lty.me
error: failed retrieving file 'core.db' from mirrors.cat.pdx.edu : Could not resolve host: mirrors.cat.pdx.edu
core                                                        133.6 KiB  3.53 MiB/s 00:00 [####################################################] 100%
error: failed retrieving file 'extra.db' from mirrors.kernel.org : Could not resolve host: mirrors.edge.kernel.org
error: failed retrieving file 'extra.db' from mirrors.kernel.org : Could not resolve host: mirrors.kernel.org
error: failed retrieving file 'extra.db' from ca.us.mirror.archlinux-br.org : Could not resolve host: ca.us.mirror.archlinux-br.org
error: failed retrieving file 'extra.db' from mirror.lty.me : Could not resolve host: mirror.lty.me
error: failed retrieving file 'extra.db' from mirrors.cat.pdx.edu : Could not resolve host: mirrors.cat.pdx.edu
extra

This error occurs after an extended, 24 hours+, of time on linux 5.7.3 on a VPS system. On this system the hwclock is wanderring. The fix is to upgrade to 5.7.4.

That symptom:

[root@tent michael]# for i in 1 2 3 4 ; do hwclock -r ; sleep 1 ; done
2020-04-30 09:06:32.351278-07:00
2020-06-25 16:36:26.447690-07:00
2020-06-20 20:05:58.085588-07:00
2020-06-20 12:19:58.073129-07:00
[root@tent michael]#

What is needed to get the mirrors resolveable by pacman?

And continuing:

ah, well yes. I cannot ping reliably:

[root@tent michael]# ping mirrors.kernel.org
ping: mirrors.kernel.org: Temporary failure in name resolution

[root@tent michael]# ping -c 1 google.com
ping: google.com: Temporary failure in name resolution

[root@tent michael]# ping -c 1 google.com
PING google.com(sea30s02-in-x0e.1e100.net (2607:f8b0:400a:803::200e)) 56 data bytes
ping: Warning: time of day goes back (-332163071842us), taking countermeasures
64 bytes from sea30s02-in-x0e.1e100.net (2607:f8b0:400a:803::200e): icmp_seq=1 ttl=121 time=251658213 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 251658213.422/251658213.422/251658213.422/0.000 ms
[root@tent michael]#

so, yes, it is a temporary failure

jasonwryan · 2020-06-20 04:33:33

Please paste details of your networking setup: card, driver, manager, configs, and the output of `find /etc/systemd -name "*.service"`

finoderi · 2020-06-20 06:41:19

MichaelRpdx wrote:

ah, well yes. I cannot ping reliably:
[root@tent michael]# ping mirrors.kernel.org
ping: mirrors.kernel.org: Temporary failure in name resolution

It's not a temporary problem ) It's just the system's way to tell you that DNS is not working. Have you tried to ping just IPs?
Something like:

ping -c 10 1.1.1.1

or

ping -c 10 8.8.8.8

Fixing the issue depends on what network manager you're using and your DNS set up.

MichaelRpdx · 2020-06-20 08:06:34

As to testing DNS -

[root@tent pacman.d]# ping -c 10 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
ping: Warning: time of day goes back (-1240605184064us), taking countermeasures
64 bytes from 8.8.8.8: icmp_seq=1 ttl=122 time=83886068 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=122 time=27962024 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=122 time=55924044 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=122 time=27962024 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=122 time=27962024 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=122 time=27962024 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=122 time=55924048 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=122 time=27962024 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=122 time=27962018 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=122 time=27962026 ms

--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 782936652ms
rtt min/avg/max/mdev = 27962018.220/39146832.403/83886068.185/1661355.881 ms

and

[root@tent pacman.d]# ping -c 10 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
ping: Warning: time of day goes back (-7420195211163us), taking countermeasures    ## Note
64 bytes from 1.1.1.1: icmp_seq=1 ttl=62 time=55924048 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=62 time=27962024 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=62 time=55924048 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=62 time=83886072 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=62 time=55924050 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=62 time=55924050 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=62 time=0.000 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=62 time=0.000 ms

About the note, a root problem on ths system is a wandering hwclock. This has a solution - upgrade from linux 5.7.3. which is my attempt to do now. This sees to be a kernal issue on VPS systems.

Here is some information on that issue:

When opening a ticket with my vendor, their response was:

   Do you by chance run on 5.7.3?

And it turns out I did.
It's a bug. Fixed.

If you are curious:
   https://bugzilla.kernel.org/show_bug.cgi?id=20822

If I'd only been lazy and waited until today to upgrade my systems, no problem.

MichaelRpdx · 2020-06-20 08:18:52

I am currently ssh'd into the system. It is a VPS system. From that I can assume the card and driver are fine. As to the rest of you request:

[root@tent etc]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:16:3c:38:ba:d1 brd ff:ff:ff:ff:ff:ff
    inet 107.191.106.119/24 brd 107.191.106.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2604:180:1:148::bde2/48 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3cff:fe38:bad1/64 scope link 
       valid_lft forever preferred_lft forever
[root@tent etc]# ip route
default via 107.191.106.1 dev eth0 proto static 
107.191.106.0/24 dev eth0 proto kernel scope link src 107.191.106.119 
[root@tent etc]# find /etc/systemd -name "*.service"
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/multi-user.target.wants/systemd-resolved.service
/etc/systemd/system/multi-user.target.wants/systemd-networkd.service
/etc/systemd/system/multi-user.target.wants/postfix.service
/etc/systemd/system/multi-user.target.wants/cronie.service
/etc/systemd/system/multi-user.target.wants/ntpd.service
/etc/systemd/system/multi-user.target.wants/sshd.service
/etc/systemd/system/multi-user.target.wants/vnstat.service
/etc/systemd/system/multi-user.target.wants/named.service
/etc/systemd/system/multi-user.target.wants/saslauthd.service
/etc/systemd/system/multi-user.target.wants/dhcpcd.service
/etc/systemd/system/dbus-org.freedesktop.resolve1.service
[root@tent etc]#

But, as I stated, this is a VPS system. The base functioning of the networking is OK.
This system is at least six years old. It functions fine.

seth · 2020-06-20 12:49:41

/etc/systemd/system/multi-user.target.wants/systemd-resolved.service
/etc/systemd/system/multi-user.target.wants/systemd-networkd.service
…
/etc/systemd/system/multi-user.target.wants/dhcpcd.service

You have two interfering network managing services activated, pick one and disable the other.

But the wild running clock will mess w/ DNS.

This is mirror.pit.teraswitch.com for the lts kernel (you can intall it parallel to the main one - in case anything should go wrong)
http://204.16.246.250/archlinux/core/os … kg.tar.zst
http://204.16.246.250/archlinux/core/os … ar.zst.sig

Lone_Wolf · 2020-06-20 12:50:12

/etc/systemd/system/multi-user.target.wants/systemd-resolved.service
/etc/systemd/system/multi-user.target.wants/systemd-networkd.service
/etc/systemd/system/multi-user.target.wants/dhcpcd.service

You appear to be using two conflicting network management tools (dhcpcd conflicts with systemd-networkd AND systemd-resolved ), choose one and disable the other.

Incase you do need both, make sure they don't try to manage the same interface.

MichaelRpdx · 2020-06-20 14:57:28

seth wrote:

/etc/systemd/system/multi-user.target.wants/systemd-resolved.service
/etc/systemd/system/multi-user.target.wants/systemd-networkd.service
…
/etc/systemd/system/multi-user.target.wants/dhcpcd.service
You have two interfering network managing services activated, pick one and disable the other.
But the wild running clock will mess w/ DNS.
This is mirror.pit.teraswitch.com for the lts kernel (you can intall it parallel to the main one - in case anything should go wrong)
http://204.16.246.250/archlinux/core/os … kg.tar.zst
http://204.16.246.250/archlinux/core/os … ar.zst.sig

OK, I picked the systemd and deleted dhcpcd

I then downloaded the specified kernel package and sig. Then installed it with

pacman -U linux-lts-5.4.46-1-x86_64.pkg.tar.zst

Which ran to completion without issue. I then rebooted the system and came back up with kernel 5.7.3.

What am I missing in the process here?

seth · 2020-06-20 15:00:08

You need to change the default kernel in the boot manager (assuming you cannot access the system during the boot process)

loqs · 2020-06-20 15:00:43

Is /boot on a separate partition to / and if so was it mounted when you reinstalled the kernel package?

MichaelRpdx · 2020-06-20 15:20:17

To respond to the two of you. Yes, a separate boot partion:

[michael@tent new_kernel]$ df -h -t ext4
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3        58G   13G   43G  23% /
/dev/sda1       488M  104M  350M  23% /boot
[michael@tent new_kernel]$

Which conatins:

[michael@tent boot]$ ls -ltr
total 93740
drwx------ 2 root root    16384 Jul 25  2016 lost+found
drwxr-xr-x 6 root root     4096 Nov 29  2018 grub
-rw-r--r-- 1 root root  7454464 Jun 18 18:10 vmlinuz-linux
-rw-r--r-- 1 root root  9538944 Jun 18 18:11 initramfs-linux.img
-rw-r--r-- 1 root root 31395755 Jun 18 18:12 initramfs-linux-fallback.img
-rw-r--r-- 1 root root  6400384 Jun 20 07:42 vmlinuz-linux-lts
-rw-r--r-- 1 root root  9833170 Jun 20 07:42 initramfs-linux-lts.img
-rw-r--r-- 1 root root 31340227 Jun 20 07:43 initramfs-linux-lts-fallback.img
[michael@tent boot]$

Since I've not messed with Grub and am disinclined to shoot myself in the foot, what next?

I see there is a 5.7.3 and 5.4.46 versions:

[michael@tent boot]$ file vmlin*
vmlinuz-linux:     Linux kernel x86 boot executable bzImage, version 5.7.3-arch1-1 (linux@archlinux) #1 SMP PREEMPT Wed, 17 Jun 2020 19:42:12 +0000, RO-rootFS, swap_dev 0x7, Normal VGA
vmlinuz-linux-lts: Linux kernel x86 boot executable bzImage, version 5.4.46-1-lts (linux-lts@archlinux) #1 SMP Wed, 10 Jun 2020 20:36:34 +0000, RO-rootFS, swap_dev 0x6, Normal VGA
[michael@tent boot]$

Last edited by MichaelRpdx (2020-06-20 16:19:33)

seth · 2020-06-20 15:36:15

https://wiki.archlinux.org/index.php/GR … ation_file
https://wiki.archlinux.org/index.php/GR … menu_entry

Last edited by seth (2020-06-20 15:36:59)

MichaelRpdx · 2020-06-20 16:14:57

Thank you.
The big, green TIP box was certainly the thing needed for people who need to have a wake up call

Arch Linux

#1 2020-06-20 03:49:43

Unable to retrieve mirrors [SOLVED]

#2 2020-06-20 03:53:30

Re: Unable to retrieve mirrors [SOLVED]

#3 2020-06-20 03:59:06

Re: Unable to retrieve mirrors [SOLVED]

#4 2020-06-20 04:09:22

Re: Unable to retrieve mirrors [SOLVED]

#5 2020-06-20 04:20:48

Re: Unable to retrieve mirrors [SOLVED]

#6 2020-06-20 04:33:33

Re: Unable to retrieve mirrors [SOLVED]

#7 2020-06-20 06:41:19

Re: Unable to retrieve mirrors [SOLVED]

#8 2020-06-20 08:06:34

Re: Unable to retrieve mirrors [SOLVED]

#9 2020-06-20 08:18:52

Re: Unable to retrieve mirrors [SOLVED]

#10 2020-06-20 12:49:41

Re: Unable to retrieve mirrors [SOLVED]

#11 2020-06-20 12:50:12

Re: Unable to retrieve mirrors [SOLVED]

#12 2020-06-20 14:57:28

Re: Unable to retrieve mirrors [SOLVED]

#13 2020-06-20 15:00:08

Re: Unable to retrieve mirrors [SOLVED]

#14 2020-06-20 15:00:43

Re: Unable to retrieve mirrors [SOLVED]

#15 2020-06-20 15:20:17

Re: Unable to retrieve mirrors [SOLVED]

#16 2020-06-20 15:36:15

Re: Unable to retrieve mirrors [SOLVED]

#17 2020-06-20 16:14:57

Re: Unable to retrieve mirrors [SOLVED]

Board footer