August 2020 - Arch-general - lists.archlinux.org

[arch-general] R: openvpn-client@ takes long time to start
by Riccardo Paolo Bestetti 14 Aug '20

14 Aug '20

Da: Giancarlo Razzolini Inviato: Venerdì, 14 Agosto, 2020 13:29 A: General Discussion about Arch Linux Cc: Riccardo Paolo Bestetti Oggetto: Re: [arch-general] openvpn-client@ takes long time to start Em agosto 14, 2020 3:58 Riccardo Paolo Bestetti via arch-general escreveu: >> After a reboot, the first openvpn-client@ instance I try to start takes almost exactly two minutes to start. The instances before that one start just fine in a few seconds. >> > Guess you meant: "The instances *after* ..." Yes I did. :) >> When that happens, I can see from journalctl that the client actually starts in the first few seconds after the systemctl command. But then, the command doesn't terminate for two more minutes (with no further journal entries). >> > Openvpn has quite good logging capabilities that you can put to use here. The output from OpenVPN indicates that the client is started within the first few seconds from when I give the `systemctl start openvpn-client@whatever` command (see previous email). The tun interface is created, opened, the routes are received and added to the routing table. All the usual stuff. Of course, I can also reach remote hosts through the VPN after that. The exact same thing (& output) happens if I try to start OpenVPN manually from the command line. Minus, of course, the two-minutes wait before the command returns. >> Has anyone seen this before? What could it be? >> > Without knowing more, my first guess is that you still don't have connectivity when that first openvpn client starts. > 2 minutes matches exactly the 120 seconds default ping-restart parameter. So, > what happens is, the client starts, you have > no connectivity then, after two minutes, ping-restart kicks in, and your connection gets through. > So, get a network manager that can properly trigger network-online.target. Or, if your network manager is triggering it, then > it means your network is not quite ready when it does. See above. I also forgot to specify it also happens when the system has been up for hours. It really can't be that the network is not ready. I don't think there's anything much that could be disturbing it. I'm using systemd-networkd for everything + iwd for wireless. Riccardo > Regards, > Giancarlo Razzolini

2 1

[arch-general] openvpn-client@ takes long time to start
by Riccardo Paolo Bestetti 14 Aug '20

14 Aug '20

After a reboot, the first openvpn-client@ instance I try to start takes almost exactly two minutes to start. The instances before that one start just fine in a few seconds. When that happens, I can see from journalctl that the client actually starts in the first few seconds after the systemctl command. But then, the command doesn't terminate for two more minutes (with no further journal entries). Has anyone seen this before? What could it be? Riccardo

2 1

[arch-general] old archlinux instance repositories progress
by Jude DaShiell 13 Aug '20

13 Aug '20

I found and downloaded a current mirrorslist file and selected servers to use. pacman cannot update though and I suspect this is because the necessary ssh keys have to be imported. How is this done using pacman facilities in such a situation? --

4 6

[arch-general] Pros/Cons of Python zipapp packaging
by Daan De Meyer 11 Aug '20

11 Aug '20

Hi, We've been discussing the distribution mechanism for mkosi ( https://github.com/systemd/mkosi) and one of the ideas is using Python zipapp (https://docs.python.org/3/library/zipapp.html) to allow us to split mkosi up into multiple files for easier development without complicating the packaging process. zipapp takes all source files in a directory and bundles them up into a single executable python zip archive so after building the zip you can simply call ./mkosi to run mkosi and can put it anywhere in the PATH to simply run mkosi wherever you want. Are there any issues with this approach from a distro packaging perspective? Zipapp doesn't bundle a specific python version (uses system python and system python stdlib) and we don't intend on bundling any dependencies in the zipapp. I don't think I've ever seen a python application packaged this way which is why I'm asking. Cheers, Daan

4 4

[arch-general] old archlinux cannot now update
by Jude DaShiell 11 Aug '20

11 Aug '20

Is a link in the archwiki on the process to point archlinux at all of the new repositories and import all of the ssh keys? I hadn't been able to access my computers while this move happened so wasn't able to do the necessary steps to change where archlinux finds all of its updates. --

3 3

[arch-general] Estimate on when 5.8 will hit core? - (Virtualbox Still Won't Build)
by David C. Rankin 08 Aug '20

08 Aug '20

Devs, Just a quick check on when 5,8 is going from testing to core? I ask because Virtualbox still is not ready for 5.8: https://www.virtualbox.org/ticket/19644 -- David C. Rankin, J.D.,P.E.

1 0