Update errors on both my systems

 update
:: Synchronizing package databases...
 garuda                                                96.8 KiB   169 KiB/s 00:01 [----------------------------------------------] 100%
 core.db failed to download
 extra.db failed to download
 multilib.db failed to download
 chaotic-aur                                            2.6 MiB  2.81 MiB/s 00:01 [----------------------------------------------] 100%
error: failed retrieving file 'core.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 5235 ms: Couldn't connect to server
error: failed retrieving file 'extra.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 5235 ms: Couldn't connect to server
error: failed retrieving file 'multilib.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 5378 ms: Couldn't connect to server
warning: too many errors from mirror.cyberbits.asia, skipping for the remainder of this transaction
error: failed to synchronize all databases (download library error)
:: Synchronizing package databases...
 chaotic-aur                                            2.6 MiB  2.59 MiB/s 00:01 [##############################################] 100%

--> Refreshing mirrorlists using rate-mirrors, please be patient..🍵

:: Synchronizing package databases...
 garuda downloading...
 core downloading...
 extra downloading...
 multilib downloading...
 chaotic-aur downloading...
error: failed retrieving file 'extra.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 32 ms: Couldn't connect to server
error: failed retrieving file 'multilib.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 32 ms: Couldn't connect to server
error: failed retrieving file 'core.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 42 ms: Couldn't connect to server
warning: too many errors from mirror.cyberbits.asia, skipping for the remainder of this transaction
error: failed to synchronize all databases (unexpected error)

Failed to update mirrorlist
:: Synchronizing package databases...
 garuda downloading...
 core downloading...
 extra downloading...
 multilib downloading...
 chaotic-aur downloading...
error: failed retrieving file 'core.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 378 ms: Couldn't connect to server
error: failed retrieving file 'extra.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 378 ms: Couldn't connect to server
error: failed retrieving file 'multilib.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 5540 ms: Couldn't connect to server
warning: too many errors from mirror.cyberbits.asia, skipping for the remainder of this transaction
error: failed to synchronize all databases (unexpected error)
:: Synchronizing package databases...
 chaotic-aur downloading...
:: Synchronizing package databases...
 garuda is up to date
 core.db failed to download
 extra.db failed to download
 multilib.db failed to download
 chaotic-aur is up to date
error: failed retrieving file 'multilib.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 5282 ms: Couldn't connect to server
error: failed retrieving file 'core.db' from mirror.cyberbits.asia : Failed to connect to mirror.cyberbits.asia port 443 after 5374 ms: Couldn't connect to server
error: failed retrieving file 'extra.db' from mirror.cyberbits.asia : Connection time-out
warning: too many errors from mirror.cyberbits.asia, skipping for the remainder of this transaction
error: failed to synchronize all databases (download library error)

What’s going on?

Take a look here

8 Likes

I used

update remote fix

and it solved my problem.

1 Like

Or that :slight_smile:
I think the last

garuda-update

4.4.1 did the same :wink:

I marked @TilliDie’s answer as solution :slight_smile:

2 Likes

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