Updating issue

Hello Garuda users.
I have been having an issue with updating the system of late, the first part is the output of the issue is below. For the life of me I can't work out why this is happening and have been trying to find a solution but I can't seem too find a one.

the issue:

╭─[email protected] in ~ took 170ms
╰─λ sudo pacman -Syu
[sudo] password for thor:
:: Synchronizing package databases...
garuda.db failed to download
core.db failed to download
extra.db failed to download
community.db failed to download
multilib.db failed to download
error: failed retrieving file 'garuda.db' from geo-mirror.chaotic.cx : Resolving timed out after 10000 millise
conds

any advise on this would be great.

2 Likes

Welcome :slight_smile:

Please post your garuda-inxi.

And try

garuda-update

in your terminal.

7 Likes

thank you for the reply, the garuda-inxi ouptu is:

System:
Kernel: 5.19.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3251f839-fde6-42d1-a673-eba2e3b3e3f7 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.25.4 tk: Qt v: 5.15.5 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7B89 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: B450M MORTAR (MS-7B89) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 1.H5
date: 01/04/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 5% (should be ignored) rechargeable: yes status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2 gen: 3
built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3865 high: 4383 min/max: 2200/4409 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3587 2: 3800
3: 3800 4: 3562 5: 3800 6: 3800 7: 4053 8: 3800 9: 4383 10: 3793 11: 4213
12: 3800 bogomips: 91198
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
protection
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: eVga.com.
driver: nvidia v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-07) arch: Ampere code: GAxxx process: TSMC n7
(7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max:
gen: 4 speed: 16 GT/s bus-ID: 26:00.0 chip-ID: 10de:2482 class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 6016x2160 s-dpi: 81 s-size: 1886x686mm (74.25x27.01")
s-diag: 2007mm (79.01")
Monitor-1: DP-3 pos: primary,top-right res: 4096x2160 hz: 24 dpi: 86
size: 1210x680mm (47.64x26.77") diag: 1388mm (54.65") modes: N/A
Monitor-2: HDMI-0 pos: bottom-l res: 1920x1080 hz: 60 dpi: 96
size: 510x290mm (20.08x11.42") diag: 587mm (23.1") modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA
515.65.01 direct render: Yes
Audio:
Device-1: NVIDIA GA104 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 26:00.1 chip-ID: 10de:228b
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 28:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound Server-1: ALSA v: k5.19.1-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 16.1 running: no
Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 2.65 TiB used: 131.14 GiB (4.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Gigabyte
model: GP-ASM2NE2512GTTDR size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: ECFM12.3 temp: 31.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung model: SSD 960 EVO
250GB size: 232.89 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B7QCXE7
temp: 26.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EARS-003BB1 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A80
scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: KingSpec model: ACSC4M512S25
size: 472 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1D scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Toshiba model: MK6465GSXN
size: 596.17 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
type: HDD rpm: 5400 serial: <filter> rev: 1M scheme: MBR
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 131.11 GiB
(27.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 25.8 MiB
(8.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 131.11
GiB (27.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 131.11
GiB (27.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 131.11
GiB (27.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.27 GiB used: 1.5 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 56.1 C mobo: N/A gpu: nvidia temp: 36 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 376 Uptime: 1d 19h 30m wakeups: 26 Memory: 31.27 GiB used: 4.07
GiB (13.0%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.1.1 clang: 14.0.6 Packages: pacman: 2026 lib: 521
Shell: fish v: 3.5.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.20
Garuda (2.6.6-1):
System install date:     2022-05-12
Last full system update: 2022-08-30
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:            bluetooth-autoconnect.service systemd-vconsole-setup.service

I have tried garuda-update to on prevail

Try Garuda-Assistant -> "Refresh Mirrorlist"

1 Like

Thank you for the suggestion, i gave it a go and also added some new ones on my second attempt and had no success.

garuda-update does refresh the mirrorlist.

Post the full output of garuda-update.

4 Likes

HI mate,
here is the output of garuda-update

╭─[email protected] in ~ took 28m56s
[] × garuda-update
[sudo] password for thor:
:: Synchronizing package databases...
garuda.db failed to download
core.db failed to download
extra.db failed to download
community.db failed to download
multilib.db failed to download
error: failed retrieving file 'garuda.db' from geo-mirror.chaotic.cx : Resolving timed out after 10000 millise
conds
error: failed retrieving file 'core.db' from sydney.mirror.pkgbuild.com : Connection time-out
error: failed retrieving file 'extra.db' from sydney.mirror.pkgbuild.com : Connection time-out
error: failed retrieving file 'community.db' from sydney.mirror.pkgbuild.com : Connection time-out
warning: too many errors from sydney.mirror.pkgbuild.com, skipping for the remainder of this transaction
error: failed retrieving file 'multilib.db' from sydney.mirror.pkgbuild.com : Connection time-out
error: failed retrieving file 'garuda.db' from cdn-mirror.chaotic.cx : Resolving timed out after 10000 millise
conds
error: failed retrieving file 'core.db' from arch.lucassymons.net : Resolving timed out after 10000 millisecon
ds
error: failed retrieving file 'extra.db' from arch.lucassymons.net : Resolving timed out after 10000 milliseco
nds
error: failed retrieving file 'community.db' from arch.lucassymons.net : Connection time-out
warning: too many errors from arch.lucassymons.net, skipping for the remainder of this transaction
error: failed retrieving file 'multilib.db' from arch.lucassymons.net : Connection time-out
error: failed retrieving file 'garuda.db' from au-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'core.db' from syd.mirror.rackspace.com : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'extra.db' from syd.mirror.rackspace.com : Connection time-out
error: failed retrieving file 'community.db' from syd.mirror.rackspace.com : Connection time-out
warning: too many errors from syd.mirror.rackspace.com, skipping for the remainder of this transaction
error: failed retrieving file 'multilib.db' from syd.mirror.rackspace.com : Connection time-out
error: failed retrieving file 'garuda.db' from au-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from br-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from br-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from br-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from bg-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from ca-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from ca-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from ca-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from cl-1-mirror.chaotic.cx : Resolving timed out after 10001 millis
econds
error: failed retrieving file 'garuda.db' from cl-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from fr-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from fr-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from fr-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from de-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-4-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-5-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-6-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from in-2-mirror.chaotic.cx : Resolving timed out after 10001 millis
econds
error: failed retrieving file 'garuda.db' from in-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-4-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-5-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-6-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from jp-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from jp-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from jp-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from jp-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from kr-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from kr-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from kr-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from es-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from es-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from ae-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from ae-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from uk-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from uk-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from uk-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from uk-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from us-az-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-az-1-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-az-2-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-fl-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-mi-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-ny-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-tx-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-ut-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-va-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-va-2-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-va-3-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-va-4-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed to synchronize all databases (download library error)
:: Synchronizing package databases...
chaotic-aur.db failed to download
error: failed retrieving file 'chaotic-aur.db' from garudalinux.org : Resolving timed out after 10000 millisec
onds
error: failed to synchronize all databases (download library error)

--> Refreshing mirrorlists using rate-mirrors, please be patient..
Error: failed to connect to https://www.archlinux.org/mirrors/status/json/, consider increasing fetch-mirrors-
timeout

Failed to update mirrorlist
:: Synchronizing package databases...
garuda.db failed to download
core.db failed to download
extra.db failed to download
community.db failed to download
multilib.db failed to download
error: failed retrieving file 'garuda.db' from geo-mirror.chaotic.cx : Resolving timed out after 10000 millise
conds
error: failed retrieving file 'core.db' from sydney.mirror.pkgbuild.com : Resolving timed out after 10000 mill
iseconds
error: failed retrieving file 'extra.db' from sydney.mirror.pkgbuild.com : Connection time-out
error: failed retrieving file 'community.db' from sydney.mirror.pkgbuild.com : Connection time-out
warning: too many errors from sydney.mirror.pkgbuild.com, skipping for the remainder of this transaction
error: failed retrieving file 'multilib.db' from sydney.mirror.pkgbuild.com : Connection time-out
error: failed retrieving file 'garuda.db' from cdn-mirror.chaotic.cx : Resolving timed out after 10000 millise
conds
error: failed retrieving file 'extra.db' from arch.lucassymons.net : Connection time-out
error: failed retrieving file 'community.db' from arch.lucassymons.net : Connection time-out
error: failed retrieving file 'multilib.db' from arch.lucassymons.net : Connection time-out
warning: too many errors from arch.lucassymons.net, skipping for the remainder of this transaction
error: failed retrieving file 'core.db' from arch.lucassymons.net : Connection time-out
error: failed retrieving file 'garuda.db' from au-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'extra.db' from syd.mirror.rackspace.com : Connection time-out
error: failed retrieving file 'community.db' from syd.mirror.rackspace.com : Connection time-out
error: failed retrieving file 'multilib.db' from syd.mirror.rackspace.com : Connection time-out
warning: too many errors from syd.mirror.rackspace.com, skipping for the remainder of this transaction
error: failed retrieving file 'core.db' from syd.mirror.rackspace.com : Connection time-out
error: failed retrieving file 'garuda.db' from au-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from br-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from br-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from br-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from bg-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from ca-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from ca-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from ca-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from cl-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from cl-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from fr-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from fr-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from fr-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from de-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-4-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-5-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from de-6-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from in-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-4-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-5-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from in-6-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from jp-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from jp-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from jp-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from jp-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from kr-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from kr-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from kr-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from es-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from es-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from ae-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from ae-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from uk-mirror.chaotic.cx : Resolving timed out after 10000 millisec
onds
error: failed retrieving file 'garuda.db' from uk-1-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from uk-2-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from uk-3-mirror.chaotic.cx : Resolving timed out after 10000 millis
econds
error: failed retrieving file 'garuda.db' from us-az-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-az-1-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-az-2-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-fl-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-mi-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-ny-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-tx-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-ut-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-va-mirror.chaotic.cx : Resolving timed out after 10000 milli
seconds
error: failed retrieving file 'garuda.db' from us-va-2-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-va-3-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed retrieving file 'garuda.db' from us-va-4-mirror.chaotic.cx : Resolving timed out after 10000 mil
liseconds
error: failed to synchronize all databases (download library error)
:: Synchronizing package databases...
chaotic-aur.db failed to download
error: failed retrieving file 'chaotic-aur.db' from garudalinux.org : Resolving timed out after 10000 millisec
onds
error: failed to synchronize all databases (download library error)

--> Applying keyring updates before starting full system update..
warning: chaotic-keyring-20220803-1 is up to date -- skipping
warning: garuda-hotfixes-1.1.2-1 is up to date -- skipping
error: target not found: blackarch-keyring

Please add code tags to your terminal output, it's just a mess to look at otherwise. If you are not sure how, back up and read through this post:

Paste the output of:

cat /etc/resolv.conf
2 Likes

sorry about the mess, the outptu is:

File: /etc/resolv.conf
# Generated by NetworkManager
search home.gateway
nameserver 192.168.1.254

Your nameserver is set to a local device on your network. Do you recognize this device? (Are you running your own DNS with a PiHole or something?)

Try to change to a proper DNS provider to see if you can put an update together.

sudo micro /etc/resolv.conf

Change the "nameserver" line to the IP of an actual DNS provider:

nameserver 208.67.222.222

Ctrl + q to quit, make sure to save your changes.

If the file does not let you make a change, you may have to remove the immutable attribute first:

sudo chattr -i /etc/resolv.conf

This is not a permanent intervention; NetworkManager will overwrite this value when it restarts. You should figure out what is going on with the DNS server that is being assigned by the gateway.

If you wish to make it permanent instead of figuring out how to fix the DNS issue, you will have to re-apply the immutable attribute after editing the file (same chattr command, just change the -i to +i).

3 Likes

HI BluishHumility,
that worked a treat and your right in that it changes every time I reboot. I'm happy to say that this one is solved, but any suggestions on which questions I should ask and trouble shooting I can do to find why it keeps changing. I did before this started I disabled the IP6 in the network manager, but I cant see why that would case this issue.

I would bet a hundred bucks that 192.168.1.254 is your gateway. You can confirm by running the ip route command:

 λ ip route
default via 192.168.0.1 dev eno1 proto dhcp src 192.168.0.2 metric 100
192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.2 metric 100

The "default via" value will identify your gateway (in my case the gateway is 192.168.0.1).

It is perfectly common for your gateway to assign a DNS server for devices on your network, but in this case it looks like something is misconfigured somehow--it should be assigning an actual DNS server, not itself.

The first thing I would try is simply rebooting your router (I am assuming your router is your gateway). If you can, just unplug it from power, wait ten seconds or so, then plug it back in. Then reboot your computer too, and see if the gateway is still setting itself as the DNS server.

If it is, you should figure out how to log in to the admin portal for your router so you can examine the settings. Typically you would navigate to the IP address of your router in a web browser (just type 192.168.1.254 in the address bar) and log in. If you have never logged in before, do a web search for your router model to find out what you are supposed to be using for the default credentials.

Somewhere in the settings you should be able to change the DNS servers, or at least see what they are set to. They might refer to them as DNS servers or Name Servers, and it might be stuck in various places in the settings. My DNS servers can be configured in Gateway > Connection > Local IP Network > IPv4, but every router does this a little differently. You might have to poke around a little bit to find it.

Once you find it, add the DNS servers you want to use for the primary and secondary DNS servers. I typically use OpenDNS because it works well and I appreciate the configuration that can be done in their web portal.

208.67.222.222
208.67.220.220

Obviously feel free to use any DNS servers you want.

My guess is your router is configured with IPv6 nameservers, and perhaps an IPv4 nameserver is not configured by default. By disabling IPv6 the gateway is no longer able to pass along the nameserver.

It is pretty common for ISPs to have IPv6 nameservers that they send down to their subscribers by default (it helps them examine your network traffic :face_with_monocle:). Depending on your ISP these nameservers are often not great anyway, so getting in there and fixing the settings is probably for the best.

4 Likes