Error to use yay/paru. No route to host

ray-x · 2022-09-02 07:00:15

It has been a issue for me a few month ago. I have been use yay for a while and it used to work well for me. But it begin to complain about "No route to host" now.
e.g. I am trying to install aws-cli-v2

shell>  yay -s aws-cli-v2
2 aur/aws-cli-v2 2.7.28-1 (+10 1.23) 
    Universal Command Line Interface for Amazon Web Services (version 2)
1 aur/aws-cli-v2-bin 2.7.28-1 (+41 1.77) 
    Universal Command Line Interface for Amazon Web Services version 2
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 2
:: Checking for conflicts...
:: Checking for inner conflicts...
 -> Package conflicts found:
 -> Installing aws-cli-v2 will remove: aws-cli
 -> Conflicting packages will have to be confirmed manually
[Aur:2]  python-awscrt-0.13.13-1  aws-cli-v2-2.7.28-1

:: (0/2) Downloaded PKGBUILD: aws-cli-v2
:: (0/2) Downloaded PKGBUILD: python-awscrt
 -> error fetching aws-cli-v2: Cloning into 'aws-cli-v2'...
fatal: unable to connect to aur.archlinux.org:
aur.archlinux.org[0: 95.216.144.15]: errno=No route to host
aur.archlinux.org[1: 2a01:4f9:c010:50::1]: errno=Network is unreachable 
	context: exit status 128

error fetching python-awscrt: Cloning into 'python-awscrt'...
fatal: unable to connect to aur.archlinux.org:
aur.archlinux.org[0: 95.216.144.15]: errno=No route to host
aur.archlinux.org[1: 2a01:4f9:c010:50::1]: errno=Network is unreachable 
	context: exit status 128

But I can clone those repo from git, e.g.

git clone ssh://aur@aur.archlinux.org/aws-cli-v2.git
Cloning into 'aws-cli-v2'...
remote: Enumerating objects: 178, done.
remote: Counting objects: 100% (178/178), done.
remote: Compressing objects: 100% (107/107), done.
remote: Total 178 (delta 69), reused 178 (delta 69), pack-reused 0
Receiving objects: 100% (178/178), 38.06 KiB | 87.00 KiB/s, done.
Resolving deltas: 100% (69/69), done.

Network also works fine with ping:

ping 95.216.144.15
PING 95.216.144.15 (95.216.144.15) 56(84) bytes of data.
64 bytes from 95.216.144.15: icmp_seq=1 ttl=36 time=432 ms

I am not sure what is the issue. I searched in old posts but seems most of error was due to network issue and solve automatically in a few days. But this has buggy me for a while.

Last edited by ray-x (2022-12-03 03:34:56)

seth · 2022-09-02 07:26:36

Please edit your post and use code tags, https://bbs.archlinux.org/help.php#bbcode

This has nothing to do w/ yay/paru but your network is not stable, the outcome being random.
Common cause are conflicting services turning it on and off against each other.

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

If that's not it, please post a complete system journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st

after such failures in case there's an issue w/ the carrier (unreliable wifi etc)

ray-x · 2022-12-03 03:52:02

Thanks for your response, but it does not seems resolve the issue

the output of

sudo journalctl -b | curl -F 'file=@-' 0x0.st

is :

 sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/ok19.txt

Trilby · 2022-12-03 04:14:44

Both of these packages are in the main repos now, so you should not be using yay to install them.

Of course you shouldn't be using yay anways... but that's another topic.

Are you having the same issue with any current AUR packages? If so, do you get the same error building properly with makepkg?

I hope were not kept in suspense for another three months for these questions

Last edited by Trilby (2022-12-03 04:17:11)

dakota · 2022-12-03 04:15:28

You missed the part where seth asked about your services...

seth wrote:

Common cause are conflicting services turning it on and off against each other.
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

cfr · 2022-12-03 04:34:39

These are not directly responsible for your network problems, but they are likely responsible for lots of problems you are having or will have. The journal is packed with messages like the following:

Dec 03 14:47:43 ray-xps-arch sudo[9064]:      ray : TTY=pts/3 ; PWD=/home/ray/Downloads ; USER=root ; COMMAND=/usr/bin/pacman -S -y --config /etc/pacman.conf --

pacman -Sy is one fantastic way to break your system.

Dec 03 14:47:59 ray-xps-arch systemd[1]: Started Pacroller unattended upgrades service.
Dec 03 14:47:59 ray-xps-arch systemd[1]: pacroller.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 03 14:47:59 ray-xps-arch Diskutilization[9168]: /home/ray/bin/pacroller.sh: line 6: /etc/init.d/functions: No such file or directory
Dec 03 14:47:59 ray-xps-arch Diskutilization[9168]: /home/ray/bin/pacroller.sh: line 17: syntax error near unexpected token `}'
Dec 03 14:47:59 ray-xps-arch Diskutilization[9168]: /home/ray/bin/pacroller.sh: line 17: `}'
Dec 03 14:47:59 ray-xps-arch systemd[1]: pacroller.service: Failed with result 'exit-code'.
Dec 03 14:48:18 ray-xps-arch play[1265]: [48.0K blob data]
Dec 03 14:48:29 ray-xps-arch systemd[1]: pacroller.service: Scheduled restart job, restart counter is at 36.

Unattended upgrades would be another great option for trashing your install. Fortunately, these are failing (repeatedly), but if you've been doing this kind of thing, something similar may have succeeded in the past.

Get rid of pacroller, do a complete system update

pacman -Syu

and never run pacman -Sy or pacman -Sy <anything>.

Last edited by cfr (2022-12-03 04:35:08)

jasonwryan · 2022-12-03 04:52:23

My money is on the fact that this isn't Arch Linux. Too much stupid in one thread.

cfr · 2022-12-03 05:14:28

jasonwryan wrote:

My money is on the fact that this isn't Arch Linux. Too much stupid in one thread.

I did look, but it does appear to be Arch:

Dec 03 14:30:03 ray-xps-arch kernel: Linux version 5.15.80-1-lts (linux-lts@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP Sat, 26 Nov 2022 20:23:30 +0000

And pacroller is counted among AUR's evils.

Last edited by cfr (2022-12-03 05:16:09)

ewaller · 2022-12-03 05:22:52

But, we still have not had answers to our queries that would permit us to determine if multiple things are wrestling for control of the 802.11 device.

seth · 2022-12-03 08:46:06

The only wifi event in the journal

Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: SME: Trying to authenticate with 50:d4:f7:41:a3:56 (SSID='McQueen-5G' freq=5745 MHz)
Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: Trying to associate with 50:d4:f7:41:a3:56 (SSID='McQueen-5G' freq=5745 MHz)
Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: Associated with 50:d4:f7:41:a3:56
Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: WPA: Key negotiation completed with 50:d4:f7:41:a3:56 [PTK=CCMP GTK=CCMP]
Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: CTRL-EVENT-CONNECTED - Connection to 50:d4:f7:41:a3:56 completed [id=0 id_str=]
Dec 03 14:30:25 ray-xps-arch wpa_supplicant[1081]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise=9999 txrate=0

There's NM and wpa_supplicant, but nothing else and no indication of a wifi failure (iwlwifi driver/firmware)

But there's the vmnet bridge and I'd suspect that to mess up the route.

ip a; ip r; ip r get 95.216.144.15

Trilby · 2022-12-03 13:41:03

Am I missing some relevant evidence here? What I see is that `git` connects just fine, but `yay` fails. Is there any basis for the transient network connection hypothesis over what seems the far more parsimonious answer that yay is just doing something stupid and / or is itself perhaps outdated?

seth · 2022-12-03 14:11:39

Yay would have to do something massively stupid - or misrepresent the actual error (and just claim that there's no route to the host as generic failure)
Though that's not unlikely, esp. since the journal shows no evidence of anything actually harming the network

128 is EKEYREVOKED - but the OP also predates the openssl3 move.
*shrug*

Trilby · 2022-12-03 14:13:59

seth wrote:

Yay would have to do something massively stupid

Yup.

Arch Linux

#1 2022-09-02 07:00:15

Error to use yay/paru. No route to host

#2 2022-09-02 07:26:36

Re: Error to use yay/paru. No route to host

#3 2022-12-03 03:52:02

Re: Error to use yay/paru. No route to host

#4 2022-12-03 04:14:44

Re: Error to use yay/paru. No route to host

#5 2022-12-03 04:15:28

Re: Error to use yay/paru. No route to host

#6 2022-12-03 04:34:39

Re: Error to use yay/paru. No route to host

#7 2022-12-03 04:52:23

Re: Error to use yay/paru. No route to host

#8 2022-12-03 05:14:28

Re: Error to use yay/paru. No route to host

#9 2022-12-03 05:22:52

Re: Error to use yay/paru. No route to host

#10 2022-12-03 08:46:06

Re: Error to use yay/paru. No route to host

#11 2022-12-03 13:41:03

Re: Error to use yay/paru. No route to host

#12 2022-12-03 14:11:39

Re: Error to use yay/paru. No route to host

#13 2022-12-03 14:13:59

Re: Error to use yay/paru. No route to host

Board footer