[SOLVED] Fixed two networkmanagers running but now won't autoconnect

wilberfan · 2019-07-23 22:37:03

I couldn't figure out why I had two fixed IP addresses for my new box--until I noticed both of these services were running:

dhcpcd@enp8so.service and NetworkManager.service.

I disabled and stopped the first one so that NetworkManger was the only one running. But now at boot I get a

Activation of Network Connection Failed

I can click on the nm-applet and manually connect fine, but I can't figure out what's happening at boot to make it fail.

Running gnome, btw.

Last edited by wilberfan (2019-07-23 23:24:31)

wilberfan · 2019-07-23 22:49:07

It has something to do with specifying that NetworkManager should automatically connect to a PIA VPN. When I remove that option it DOES autoconnect. Don't know why that would make a difference, tho.

jasonwryan · 2019-07-23 22:54:13

wilberfan wrote:

but I can't figure out what's happening at boot to make it fail.

That's what your journal is for...

wilberfan · 2019-07-23 23:03:54

<info>  [1563921919.1558] vpn-connection[0x56443abfc320,89c9919a-46f6-4923-8eea-79bb042a27c1,"PIA-US-California",0]: VPN plugin: state changed: stopped (6)
Jul 23 15:45:19 mediaserver NetworkManager[536]: <info>  [1563921919.1726] vpn-connection[0x56443abfc110,89c9919a-46f6-4923-8eea-79bb042a27c1,"PIA-US-California",0]: Started the VPN service, PID 1584
Jul 23 15:45:19 mediaserver NetworkManager[536]: <info>  [1563921919.1777] vpn-connection[0x56443abfc110,89c9919a-46f6-4923-8eea-79bb042a27c1,"PIA-US-California",0]: Saw the service appear; activating connection
Jul 23 15:45:19 mediaserver NetworkManager[536]: ** <error> [1563921919.1995] vpn-connection[0x56443abfc110,89c9919a-46f6-4923-8eea-79bb042a27c1,"PIA-US-California",0]: Failed to request VPN secrets #3: No agents were available for this re**>
Jul 23 15:45:19 mediaserver NetworkManager[536]: <info>  [1563921919.1997] device (enp8s0): state change: secondaries -> failed (reason 'secondary-connection-failed', sys-iface-state: 'managed')

Last edited by wilberfan (2019-07-23 23:22:09)

jasonwryan · 2019-07-23 23:09:59

systemctl list-unit-files --state=enabled

wilberfan · 2019-07-23 23:11:22

autovt@.service                            enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service                    enabled
emby-server.service                        enabled
gdm.service                                enabled
getty@.service                             enabled
lm_sensors.service                         enabled
mariadb.service                            enabled
mysqld.service                             enabled
NetworkManager-dispatcher.service          enabled
NetworkManager-wait-online.service         enabled
NetworkManager.service                     enabled
ntpd.service                               enabled
nzbget.service                             enabled
sonarr.service                             enabled
sshd.service                               enabled
remote-fs.target                           enabled

I edited the journal post. This seems important: "Failed to request VPN secrets #3: No agents were available"

Last edited by wilberfan (2019-07-23 23:12:11)

wilberfan · 2019-07-23 23:18:47

This post revealed the problem and solution:

https://unix.stackexchange.com/question … -secrets-3

In my case (In Debian 9 by Gnome 3.2) selecting the password option "Store the password for all users" in the VPN settings got it working. All other options produce the mentioned error.

Thanks for the journal tip (reminder)!

Last edited by wilberfan (2019-07-23 23:23:09)

Arch Linux

#1 2019-07-23 22:37:03

[SOLVED] Fixed two networkmanagers running but now won't autoconnect

#2 2019-07-23 22:49:07

Re: [SOLVED] Fixed two networkmanagers running but now won't autoconnect

#3 2019-07-23 22:54:13

Re: [SOLVED] Fixed two networkmanagers running but now won't autoconnect

#4 2019-07-23 23:03:54

Re: [SOLVED] Fixed two networkmanagers running but now won't autoconnect

#5 2019-07-23 23:09:59

Re: [SOLVED] Fixed two networkmanagers running but now won't autoconnect

#6 2019-07-23 23:11:22

Re: [SOLVED] Fixed two networkmanagers running but now won't autoconnect

#7 2019-07-23 23:18:47

Re: [SOLVED] Fixed two networkmanagers running but now won't autoconnect

Board footer