You are not logged in.

#26 2021-05-20 14:09:30

prk07
Member
Registered: 2018-12-16
Posts: 44

Re: [Solved] Changing wifi logs out and stops Network Manager

Pacman upgraded these packages from May 12. I reported the error few days late after trying to find some solution for the same.

Pacman packages

Offline

#27 2021-05-20 14:37:05

seth
Member
Registered: 2012-09-03
Posts: 21,074

Re: [Solved] Changing wifi logs out and stops Network Manager

May 12th is only

[2021-05-12T06:06:33+0530] [ALPM] upgraded readline (8.1.0-2 -> 8.1.001-1)
[2021-05-12T06:06:34+0530] [ALPM] upgraded btrfs-progs (5.11.1-1 -> 5.12-1)
[2021-05-12T06:06:34+0530] [ALPM] upgraded file (5.40-2 -> 5.40-3)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-cryptonite (0.28-29 -> 0.29-1)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-x509 (1.7.5-143 -> 1.7.5-144)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-x509-store (1.6.7-142 -> 1.6.7-143)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-x509-validation (1.6.11-142 -> 1.6.11-143)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-tls (1.5.5-23 -> 1.5.5-24)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-x509-system (1.6.6-210 -> 1.6.6-211)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-connection (0.3.1-119 -> 0.3.1-120)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-http (4000.3.16-19 -> 4000.3.16-20)
[2021-05-12T06:06:34+0530] [ALPM] upgraded haskell-http-client-tls (0.3.5.3-414 -> 0.3.5.3-415)
[2021-05-12T06:06:34+0530] [ALPM] upgraded protobuf (3.15.8-1 -> 3.16.0-1)
[2021-05-12T06:06:35+0530] [ALPM] upgraded libphonenumber (8.12.21-1 -> 8.12.22-1)
[2021-05-12T06:06:35+0530] [ALPM] upgraded systemd-libs (248-5 -> 248.2-2)
[2021-05-12T06:06:35+0530] [ALPM] upgraded systemd (248-5 -> 248.2-2)
[2021-05-12T06:06:35+0530] [ALPM] upgraded libwnck3 (3.36.0-1 -> 40.0-1)
[2021-05-12T06:06:35+0530] [ALPM] upgraded md4c (0.4.7-1 -> 0.4.8-1)
[2021-05-12T06:06:35+0530] [ALPM] upgraded python (3.9.4-1 -> 3.9.5-1)
[2021-05-12T06:06:35+0530] [ALPM] upgraded marble-common (21.04.0-1 -> 21.04.0-2)
[2021-05-12T06:06:35+0530] [ALPM] upgraded marble (21.04.0-1 -> 21.04.0-2)
[2021-05-12T06:06:35+0530] [ALPM] upgraded mariadb-libs (10.5.9-1 -> 10.5.10-1)
[2021-05-12T06:06:35+0530] [ALPM] upgraded mariadb-clients (10.5.9-1 -> 10.5.10-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded mariadb (10.5.9-1 -> 10.5.10-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python-six (1.15.0-3 -> 1.16.0-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python-setuptools (1:56.0.0-1 -> 1:56.1.0-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded meson (0.58.0-1 -> 0.58.0-2)
[2021-05-12T06:06:36+0530] [ALPM] upgraded mpg123 (1.27.0-1 -> 1.27.2-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded npm (7.12.0-1 -> 7.12.1-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded openshadinglanguage (1.11.13.0-4 -> 1.11.14.0-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded pandoc (2.13-18 -> 2.13-19)
[2021-05-12T06:06:36+0530] [ALPM] upgraded pandoc-crossref (0.3.10.0-36 -> 0.3.10.0-37)
[2021-05-12T06:06:36+0530] [ALPM] upgraded protobuf-c (1.3.3-3 -> 1.3.3-4)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python-pep517 (0.10.0-1 -> 0.10.0-2)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python-sphinx (4.0.0-1 -> 4.0.1-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python-websocket-client (0.58.0-1 -> 0.59.0-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python-zeroconf (0.29.0-1 -> 0.29.0-2)
[2021-05-12T06:06:36+0530] [ALPM] upgraded python2-six (1.15.0-3 -> 1.16.0-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded qjackctl (0.9.2-2 -> 0.9.3-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded remmina (1:1.4.13-1 -> 1:1.4.14-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded runc (1.0.0rc93-2 -> 1.0.0rc94-1)
[2021-05-12T06:06:36+0530] [ALPM] upgraded systemd-sysvcompat (248-5 -> 248.2-2)
[2021-05-12T06:06:36+0530] [ALPM] upgraded virtualbox-host-dkms (6.1.22-1 -> 6.1.22-2)
[2021-05-12T06:06:37+0530] [ALPM] upgraded virtualbox (6.1.22-1 -> 6.1.22-2)
[2021-05-12T06:06:37+0530] [ALPM] upgraded vlc (3.0.13-1 -> 3.0.13-2)
[2021-05-12T06:08:49+0530] [ALPM] upgraded brave-bin (1:1.24.82-1 -> 1:1.24.84-1)
[2021-05-12T06:09:25+0530] [ALPM] upgraded visual-studio-code-bin (1.56.0-2 -> 1.56.1-1)
[2021-05-12T17:24:30+0530] [ALPM] upgraded hdparm (9.60-1 -> 9.61-1)
[2021-05-12T17:24:30+0530] [ALPM] upgraded spirv-tools (2020.7-1 -> 2021.1-1)
[2021-05-12T17:24:30+0530] [ALPM] upgraded shaderc (2020.5-1 -> 2021.0-1)

And the only thing there looking even close to be capable to causing this is the systemd update.
Can you downgrade both packages to 248-5? (Make sure to have some live distro, eg. the install iso around - if this goes wrong, the system won't boot and you'll have to fix it offline)

Offline

#28 2021-05-20 16:29:57

prk07
Member
Registered: 2018-12-16
Posts: 44

Re: [Solved] Changing wifi logs out and stops Network Manager

Downgrading can break the system which is not possible to attempt right now.
Although I found this utility to downgrade https://github.com/pbrisbin/downgrade

Will this be helpful?
Can you suggest something else?

BTW thanks for digging into my issue for so long!

Offline

#29 2021-05-20 19:35:46

seth
Member
Registered: 2012-09-03
Posts: 21,074

Re: [Solved] Changing wifi logs out and stops Network Manager

Probably not (didn't look at it but most "hey, i figured this about archlinux" blogscripts are just a way to hurt yourself)
You can roll back the entire installation to a specific date, https://wiki.archlinux.org/title/Downgrading_packages and https://wiki.archlinux.org/title/Arch_L … cific_date

You should always approach changes to the system with the awareness that this can go wrong and be ready to deal with it.
In 99.86% (that's a super accurately made up number) of all cases there won't be any problem, but if it ever is, you don't want to make plans on how to deal with it after the effect…

It's an interesting problem, there's something to learn and at worst there's gonna be a comic relief and you're cooperating competently.
I'm not going anywhere.

Offline

#30 2021-05-21 00:16:26

prk07
Member
Registered: 2018-12-16
Posts: 44

Re: [Solved] Changing wifi logs out and stops Network Manager

I do not have the local cache of old packages to downgrade. How to proceed in this case?

Offline

#31 2021-05-21 06:13:50

seth
Member
Registered: 2012-09-03
Posts: 21,074

Re: [Solved] Changing wifi logs out and stops Network Manager

The second link describes how to set the repo to a specific date and sync the local installation to that date.

Offline

#32 2021-05-21 06:50:52

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,992

Re: [Solved] Changing wifi logs out and stops Network Manager

FWIW I don't think we've seen the service enable find command yet, and this reads to me like there's some possible communication issue between dhcpcd and NM (though it does look like the former is at least properly initiated by NM itself, but afaik the new dhcpcd integration is fairly new so there might be some issues) maybe try switching that to use NMs internal client or dhclient or so?

Offline

#33 2021-05-21 07:29:24

seth
Member
Registered: 2012-09-03
Posts: 21,074

Re: [Solved] Changing wifi logs out and stops Network Manager

ftr, dhcpcd was supported as dhcp client until ~1yr ago when dhcpcd was updated to 9.0 and then wasn't until a recent patch to NM and is supported by the repo NM since May 5th.

Offline

#34 2021-05-21 08:47:40

prk07
Member
Registered: 2018-12-16
Posts: 44

Re: [Solved] Changing wifi logs out and stops Network Manager

This is amazing!

So, I was using dhcpcd client for NM in my config at /etc/NetworkManager/conf.d/dhcp-client.conf

[main]
dhcp=dhcpcd

I commented these lines to switch NM to internal client and now I can switch between my Networks without getting logged out.

The warning vanished in journal of NM relating to dhcp-listener which was as follows:

dhcp-listener: dhcp-event: (pid 1823) unhandled DHCP event for interface wlp59s0

Now only one warn message appeared which is below.

May 21 14:01:59 resurrection NetworkManager[10686]: <warn>  [1621585919.8152] sup-iface[6c4222fd9915f453,4,wlp59s0]: call-p2p-cancel: failed with P2P cancel failed

Please comment if I need to take action to remove this warning message.

I was using the dhcpcd client in NM since 2019 when I first setup Arch installation in this machine and had faced no issues with it. I recently move to my home where wifi has static IP address. Is it possible that TP-Link Archer router meddling with something while connecting to the network?


Wifi is working fine now. I will mark the post as solved in a day after some usage to see if there's any error.

Thanks @Seth and @V1Del for sticking to my post and helping.

Offline

#35 2021-05-21 09:34:10

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,992

Re: [Solved] Changing wifi logs out and stops Network Manager

P2P errors are normalish and can generally be ignored. While it's possible that your router does weird stuff or there's some bug with the new dhcpcd and NM integration (as mentioned even if you had that config it was pretty much broken for a year and it was likely using the internal client anyway) I do find it quite weird that this does have such a large scale effect. But I do remember a lot of similar sounding issues when dhcpcd had that bigger architecture change which lead to similar shenanigans if one had accidentally enabled multiple instances of dhcpcd. Maybe rsmarples pops in here and has some thoughts on what's going on here.

Last edited by V1del (2021-05-21 09:37:20)

Offline

#36 2021-05-21 09:47:08

prk07
Member
Registered: 2018-12-16
Posts: 44

Re: [Solved] Changing wifi logs out and stops Network Manager

I have always disabled the dhcpcd unit as per the arch wiki guidelines present here.

Do not enable the systemd units shipped with the dhclient and dhcpcd packages. They will conflict with NetworkManager, see the note in #Installation for details.

So, I hope multiple instances were not active for dhcpcd in this case.

Offline

#37 2021-05-21 11:45:55

seth
Member
Registered: 2012-09-03
Posts: 21,074

Re: [Solved] Changing wifi logs out and stops Network Manager

dhcpcd gets a lease, but NM doesn't seem to make anythnig out of it

May 20 12:17:29 resurrection dhcpcd[1005]: wlp59s0: offered 192.168.0.204 from 192.168.0.1
May 20 12:17:29 resurrection dhcpcd[1005]: wlp59s0: leased 192.168.0.204 for 7200 seconds
May 20 12:17:29 resurrection NetworkManager[631]: <warn>  [1621493249.8305] dhcp-listener: dhcp-event: (pid 1004) unhandled DHCP event for interface wlp59s0

5 seconds later NM starts its dispatcher

May 20 12:17:35 resurrection systemd[1]: Started Network Manager Script Dispatcher Service.

That finishes 10 seconds later

May 20 12:17:45 resurrection systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

9 seconds later NM figures it can't configure an IP (suspicious 25 seconds, the dbus tieout, after the lease is obtained)

May 20 12:17:54 resurrection NetworkManager[631]: <info>  [1621493274.8663] device (wlp59s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')

The it disconnects, dhcpcd notices the carrier loss (cause NM terminates the wpa_supplicant connection)

May 20 12:17:54 resurrection NetworkManager[631]: <info>  [1621493274.8672] manager: NetworkManager state is now DISCONNECTED
May 20 12:17:54 resurrection kernel: wlp59s0: deauthenticating from d8:07:b6:c5:38:e9 by local choice (Reason: 3=DEAUTH_LEAVING)
May 20 12:17:54 resurrection dhcpcd[1005]: wlp59s0: carrier lost

The NM wants to scan for networks

May 20 12:17:55 resurrection NetworkManager[631]: <info>  [1621493275.0026] device (wlp59s0): set-hw-addr: set MAC address to 96:DD:41:F2:72:67 (scanning)

And at this point everything goes south.

I'd imagine that there's a comm error betwen dhcpcd and NM, causing the "ip-config-unavailable", but that doesn't explain why everything falls apart.

Suspiciously there's a couple of dhcpcd PIDs lingering around and in two sets.

May 20 12:18:27 resurrection systemd[1]: NetworkManager.service: Found left-over process 1004 (dhcpcd) in control group while starting unit. Ignoring.
May 20 12:18:27 resurrection systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 20 12:18:27 resurrection systemd[1]: NetworkManager.service: Found left-over process 1005 (dhcpcd) in control group while starting unit. Ignoring.
May 20 12:18:27 resurrection systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 20 12:18:27 resurrection systemd[1]: NetworkManager.service: Found left-over process 1006 (dhcpcd) in control group while starting unit. Ignoring.
May 20 12:18:27 resurrection systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 20 12:18:27 resurrection systemd[1]: NetworkManager.service: Found left-over process 1401 (dhcpcd) in control group while starting unit. Ignoring.
May 20 12:18:27 resurrection systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 20 12:18:27 resurrection systemd[1]: NetworkManager.service: Found left-over process 1405 (dhcpcd) in control group while starting unit. Ignoring.
May 20 12:18:27 resurrection systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.

Maybe the MAC switch causes this but iirc. the condition that made dhcpcd run out of PTYs was fixed in some earlier 9.0.whatever version?

@V1del, did you ping roy about this?

Offline

#38 2021-05-21 12:39:03

prk07
Member
Registered: 2018-12-16
Posts: 44

Re: [Solved] Changing wifi logs out and stops Network Manager

UPDATE: Suspending the system manually or by closing the lid doesn't freeze the system anymore. Looks like when the system wakes up it tries to run NM which was freezing the system.

Offline

#39 2021-05-22 10:56:16

seth
Member
Registered: 2012-09-03
Posts: 21,074

Offline

Board footer

Powered by FluxBB