ubuntuusers.de

via DuckDuckGo

Nach upgrade von 20.04 auf 22.04 startet der network-manager nicht mehr

Status: Gelöst | Ubuntu-Version: Ubuntu 22.04 (Jammy Jellyfish)
Antworten |

iceman80

Anmeldungsdatum:
18. September 2013

Beiträge: 37
Zitieren
15. August 2022 17:13 (zuletzt bearbeitet: 15. August 2022 19:56)

Hallo zusammen,

wie im Titel schon geschrieben, habe ich ein upgrade auf 22.04 durchgeführt. Danach ist mein Server nicht mehr über ssh zu erreichen. Wenn ich mich direkt auf dem server anmelde (ohne SSH) kommt es beim Booten zu einer Fehlermeldung, wenn der networkmanager gestartet werden soll. Danach geht es weiter und ich kann mich auf dem Server anmelden.

1
sudo systemctl status snap.network-manager.networkmanager.service

gibt folgende Fehlermeldung zurück:

1
2
3
snap.network-manager.networkmanager.service: Start request repeated too quickly.
snap.network-manager.networkmanager.service: Failed with result 'exit-code'.
Failed to start Service for snap application network-manager.networkmanager.

Ich vermute das dieser Fehler dafür verantwortlich ist, das ich den Server auch nicht mehr per ssh erreichen kann. Aber das ist nur meine Vermutung.

Unter 20.04 lief natürlich alles noch und beim upgrade habe ich auch bei der übernahme der Confs immer den Default genommen (Also Datei beibehalten).

Eine Ammerkung noch, auf dem Server laufen einige Docker Container. Diese sind nach wie vor über einen Browser ansprechbar. Falls ich hier wichtige Informationen vergessen habe, fragt bitte nach, ich bin mir nicht sicher ob ich alles relevante untergebracht habe.

Könnt Ihr mir hier weiterhelfen bzw. sagen, wie ich den networkmanager wieder zum laufen bekomme?

Danke schonmal im voraus.

Moderiert von ChickenLipsRfun2eat:

Thema in einen passenden Forenbereich verschoben. Bitte beachte die als wichtig markierten Themen („Welche Themen gehören hier her und welche nicht?“) in jedem Forenbereich. Danke.

DJKUhpisse Team-Icon

Supporter, Wikiteam
Avatar von DJKUhpisse

Anmeldungsdatum:
18. Oktober 2016

Beiträge: 16624

Wohnort: in deinem Browser, hier auf dem Bildschirm
Zitieren
15. August 2022 17:58 
journalctl -u NetworkManager.service --no-pager

iceman80

(Themenstarter)

Anmeldungsdatum:
18. September 2013

Beiträge: 37
Zitieren
15. August 2022 19:28

Danke für den Tip mit dem journalctl. Dadurch habe ich gesehen, das der Dienst Networkmanager.service läuft und den Dienst snap.network-manager.networkmanager.service schon vor dem upgrade in einen Error lief. Den schließe ich also als Fehler erstmal aus.

Mittlerweile konnte ich feststellen, das neben meiner ssh Session mit der ich mich auf den Server angemeldet hab, auch meine andere ssh Verbindung mit der Teile meiner Heimautomation (FHEM) und dem Server reden nicht mehr funktionieren. Somit vermute ich, das das Problem entweder meine SSH Keys oder generell mein remoteverbindung sind.

Da weiß ich aber ebenso wenig wo ich suchen sollte... ☹

DJKUhpisse Team-Icon

Supporter, Wikiteam
Avatar von DJKUhpisse

Anmeldungsdatum:
18. Oktober 2016

Beiträge: 16624

Wohnort: in deinem Browser, hier auf dem Bildschirm
Zitieren
15. August 2022 19:30

Was sagt denn der Log? Hat der Rechner seine IP-Adressen?

iceman80

(Themenstarter)

Anmeldungsdatum:
18. September 2013

Beiträge: 37
Zitieren
15. August 2022 19:51

DJKUhpisse schrieb:

Was sagt denn der Log? Hat der Rechner seine IP-Adressen?

Ja die IP-Adresse ist korrekt. Darüber bekomme ich auch die Docker Container im Browser zufassen.

Welches Log meinst Du genau?

DJKUhpisse Team-Icon

Supporter, Wikiteam
Avatar von DJKUhpisse

Anmeldungsdatum:
18. Oktober 2016

Beiträge: 16624

Wohnort: in deinem Browser, hier auf dem Bildschirm
Zitieren
15. August 2022 19:53

Das von journalctl. Da ist das Ende relevant.

iceman80

(Themenstarter)

Anmeldungsdatum:
18. September 2013

Beiträge: 37
Zitieren
15. August 2022 20:02

DJKUhpisse schrieb:

Das von journalctl. Da ist das Ende relevant.

Okay, hier der Teil aus den NetworkManager.Service

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
Aug 15 17:30:45 nas-b NetworkManager[897]: <info>  [1660577445.0590] modem-manager: ModemManager no longer available
Aug 15 17:30:45 nas-b NetworkManager[897]: <info>  [1660577445.4865] manager: (veth13bab21): new Veth device (/org/freedesktop/NetworkManager/Devices/23)
Aug 15 17:30:45 nas-b NetworkManager[897]: <info>  [1660577445.5342] device (vethc783a15): released from master device docker0
Aug 15 17:30:46 nas-b NetworkManager[897]: <info>  [1660577446.1354] manager: (vethf4a7e5c): new Veth device (/org/freedesktop/NetworkManager/Devices/24)
Aug 15 17:30:46 nas-b NetworkManager[897]: <info>  [1660577446.1967] device (veth32eb4e2): released from master device br-cea21f542557
Aug 15 17:30:46 nas-b NetworkManager[897]: <info>  [1660577446.4009] manager: (vethf189660): new Veth device (/org/freedesktop/NetworkManager/Devices/25)
Aug 15 17:30:46 nas-b NetworkManager[897]: <info>  [1660577446.4570] device (vetheb0ec96): released from master device br-cea21f542557
Aug 15 17:30:47 nas-b NetworkManager[897]: <info>  [1660577447.4773] manager: (veth64cfdd9): new Veth device (/org/freedesktop/NetworkManager/Devices/26)
Aug 15 17:30:47 nas-b NetworkManager[897]: <info>  [1660577447.5084] device (vethc30441c): released from master device br-56f6b205993d
Aug 15 17:30:49 nas-b NetworkManager[897]: <info>  [1660577449.6485] manager: (veth1c36a61): new Veth device (/org/freedesktop/NetworkManager/Devices/27)
Aug 15 17:30:49 nas-b NetworkManager[897]: <info>  [1660577449.6809] device (veth09b375a): released from master device br-72cefae5993b
Aug 15 17:30:50 nas-b systemd[1]: Stopping Network Manager...
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4193] caught SIGTERM, shutting down normally.
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4503] dhcp4 (eno1): canceled DHCP transaction
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4503] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4504] dhcp4 (eno1): state changed no lease
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4508] manager: NetworkManager state is now CONNECTED_SITE
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4513] manager: startup complete
Aug 15 17:30:50 nas-b NetworkManager[897]: <info>  [1660577450.4654] exiting (success)
Aug 15 17:30:50 nas-b systemd[1]: NetworkManager.service: Deactivated successfully.
Aug 15 17:30:50 nas-b systemd[1]: Stopped Network Manager.
-- Boot c85da3207b3b424b844c37fb064a1567 --
Aug 15 17:31:16 nas-b systemd[1]: Starting Network Manager...
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.6145] NetworkManager (version 1.36.6) is starting... (for the first time)
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.6145] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Aug 15 17:31:16 nas-b systemd[1]: Started Network Manager.
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.6340] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.6571] manager[0x563f5b1f2020]: monitoring kernel firmware directory '/lib/firmware'.
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.6571] monitoring ifupdown state file '/run/network/ifstate'.
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.8640] hostname: hostname: using hostnamed
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.8640] hostname: static hostname changed from (none) to "nas-b"
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.8777] dns-mgr[0x563f5b1d12a0]: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.8965] manager[0x563f5b1f2020]: rfkill: Wi-Fi hardware radio set enabled
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.8966] manager[0x563f5b1f2020]: rfkill: WWAN hardware radio set enabled
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.9329] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-adsl.so)
Aug 15 17:31:16 nas-b NetworkManager[897]: <info>  [1660577476.9813] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0135] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-team.so)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0389] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wifi.so)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0477] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0480] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0481] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0482] manager: Networking is enabled by state file
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0715] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-settings-plugin-ifupdown.so")
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0716] settings: Loaded settings plugin: keyfile (internal)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0716] ifupdown: management mode: unmanaged
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0740] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.0741] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.1078] dhcp-init: Using DHCP client 'internal'
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.1079] device (lo): carrier: link connected
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.1082] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.1095] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.1099] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4262] manager: (br0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4287] device (br0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4315] failed to open /run/network/ifstate
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4366] device (br0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4375] policy: auto-activating connection 'br0' (46a2a735-8bc5-4d90-b13c-251f1dbd6e4a)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4385] device (br0): Activation: starting connection 'br0' (46a2a735-8bc5-4d90-b13c-251f1dbd6e4a)
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4433] modem-manager: ModemManager not available
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4477] device (br0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4480] manager: NetworkManager state is now CONNECTING
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4502] device (br0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4507] device (br0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:17 nas-b NetworkManager[897]: <info>  [1660577477.4990] modem-manager: ModemManager now available
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5845] device (eno1): carrier: link connected
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5853] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5883] policy: auto-activating connection 'netplan-eno1' (10838d80-caeb-349e-ba73-08ed16d4d666)
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5898] device (eno1): Activation: starting connection 'netplan-eno1' (10838d80-caeb-349e-ba73-08ed16d4d666)
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5901] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5910] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5931] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:21 nas-b NetworkManager[897]: <info>  [1660577481.5939] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6123] dhcp4 (eno1): state changed new lease, address=192.168.178.11
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6188] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6244] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6247] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6254] manager: NetworkManager state is now CONNECTED_SITE
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6255] policy: set 'netplan-eno1' (eno1) as default for IPv4 routing and DNS
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6263] device (eno1): Activation: successful, device activated.
Aug 15 17:31:23 nas-b NetworkManager[897]: <info>  [1660577483.6271] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 15 17:32:16 nas-b NetworkManager[897]: <info>  [1660577536.9170] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4)
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3876] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3882] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3889] device (virbr0): Activation: starting connection 'virbr0' (478d1baa-62f2-4f1b-9a0e-f21d455783bb)
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3891] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3894] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3895] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.3900] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.4265] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.4267] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:17 nas-b NetworkManager[897]: <info>  [1660577537.4272] device (virbr0): Activation: successful, device activated.
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9137] manager: (br-cea21f542557): new Bridge device (/org/freedesktop/NetworkManager/Devices/5)
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9515] device (br-cea21f542557): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9549] device (br-cea21f542557): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9569] device (br-cea21f542557): Activation: starting connection 'br-cea21f542557' (239bfb5c-7682-4184-9d7a-b9eb2bcd4abc)
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9576] device (br-cea21f542557): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9582] device (br-cea21f542557): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9586] device (br-cea21f542557): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9601] manager: (br-031eb67a2597): new Bridge device (/org/freedesktop/NetworkManager/Devices/6)
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9608] device (br-cea21f542557): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9656] device (br-cea21f542557): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9658] device (br-cea21f542557): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9663] device (br-cea21f542557): Activation: successful, device activated.
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9928] device (br-031eb67a2597): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9937] device (br-031eb67a2597): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9944] device (br-031eb67a2597): Activation: starting connection 'br-031eb67a2597' (732f63b2-9dd7-4fe4-8eec-d6f43a84138f)
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9946] device (br-031eb67a2597): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9949] device (br-031eb67a2597): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9951] device (br-031eb67a2597): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9959] manager: (br-56f6b205993d): new Bridge device (/org/freedesktop/NetworkManager/Devices/7)
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9978] device (br-031eb67a2597): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:18 nas-b NetworkManager[897]: <info>  [1660577538.9995] device (br-031eb67a2597): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0000] device (br-031eb67a2597): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0016] device (br-031eb67a2597): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0471] device (br-56f6b205993d): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0498] device (br-56f6b205993d): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0505] device (br-56f6b205993d): Activation: starting connection 'br-56f6b205993d' (43412373-8b44-4039-bd5a-a1cf3b74d13c)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0507] device (br-56f6b205993d): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0510] device (br-56f6b205993d): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0512] device (br-56f6b205993d): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0521] manager: (br-72cefae5993b): new Bridge device (/org/freedesktop/NetworkManager/Devices/8)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0525] device (br-56f6b205993d): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0549] device (br-56f6b205993d): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0555] device (br-56f6b205993d): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0563] device (br-56f6b205993d): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0977] device (br-72cefae5993b): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0986] device (br-72cefae5993b): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.0995] device (br-72cefae5993b): Activation: starting connection 'br-72cefae5993b' (2ec5f41c-f854-4945-8381-ea6fa8f84287)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1002] manager: (br-80615c98c1ee): new Bridge device (/org/freedesktop/NetworkManager/Devices/9)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1009] device (br-72cefae5993b): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1015] device (br-72cefae5993b): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1021] device (br-72cefae5993b): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1029] device (br-72cefae5993b): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1047] device (br-72cefae5993b): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1051] device (br-72cefae5993b): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1057] device (br-72cefae5993b): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1445] device (br-80615c98c1ee): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1492] device (br-80615c98c1ee): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1502] device (br-80615c98c1ee): Activation: starting connection 'br-80615c98c1ee' (270ddfa4-5c1e-4064-91cb-7b509baf8615)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1504] device (br-80615c98c1ee): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1506] device (br-80615c98c1ee): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1508] device (br-80615c98c1ee): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1517] manager: (br-969ec043c296): new Bridge device (/org/freedesktop/NetworkManager/Devices/10)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1524] device (br-80615c98c1ee): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1547] device (br-80615c98c1ee): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1551] device (br-80615c98c1ee): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1556] device (br-80615c98c1ee): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1907] device (br-969ec043c296): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1918] device (br-969ec043c296): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1927] device (br-969ec043c296): Activation: starting connection 'br-969ec043c296' (420d7e34-5a06-4811-a217-62d5ed90ac33)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1929] device (br-969ec043c296): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1933] device (br-969ec043c296): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1936] device (br-969ec043c296): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1949] manager: (br-bb533333037f): new Bridge device (/org/freedesktop/NetworkManager/Devices/11)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1957] device (br-969ec043c296): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1975] device (br-969ec043c296): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1979] device (br-969ec043c296): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.1989] device (br-969ec043c296): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2399] device (br-bb533333037f): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2410] device (br-bb533333037f): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2423] device (br-bb533333037f): Activation: starting connection 'br-bb533333037f' (f2e19454-8699-414b-ac5a-f5f5116f05cf)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2426] device (br-bb533333037f): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2432] device (br-bb533333037f): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2434] device (br-bb533333037f): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2444] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/12)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2448] device (br-bb533333037f): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2507] device (br-bb533333037f): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2509] device (br-bb533333037f): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2515] device (br-bb533333037f): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2877] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2884] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2892] device (docker0): Activation: starting connection 'docker0' (2c0784e0-fe13-4e00-9dc9-f775a42f546c)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2893] device (docker0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2896] device (docker0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2898] device (docker0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2900] device (docker0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2913] device (docker0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2916] device (docker0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.2922] device (docker0): Activation: successful, device activated.
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5158] manager: (veth5b4fe00): new Veth device (/org/freedesktop/NetworkManager/Devices/13)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5171] manager: (vethf61a94c): new Veth device (/org/freedesktop/NetworkManager/Devices/14)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5585] manager: (veth63ff7a9): new Veth device (/org/freedesktop/NetworkManager/Devices/15)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5603] manager: (vethbe442db): new Veth device (/org/freedesktop/NetworkManager/Devices/16)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5778] manager: (veth88f30af): new Veth device (/org/freedesktop/NetworkManager/Devices/17)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5801] manager: (vethae0de61): new Veth device (/org/freedesktop/NetworkManager/Devices/18)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5840] manager: (veth9bd7ca6): new Veth device (/org/freedesktop/NetworkManager/Devices/19)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.5872] manager: (veth5938a5c): new Veth device (/org/freedesktop/NetworkManager/Devices/20)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.7568] manager: (vethe894f99): new Veth device (/org/freedesktop/NetworkManager/Devices/21)
Aug 15 17:32:19 nas-b NetworkManager[897]: <info>  [1660577539.7586] manager: (veth1310e16): new Veth device (/org/freedesktop/NetworkManager/Devices/22)
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.3676] device (vethf61a94c): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.3681] device (docker0): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.6751] device (veth5938a5c): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.6755] device (br-56f6b205993d): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.7414] device (vethbe442db): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.7417] device (br-72cefae5993b): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.8912] device (veth1310e16): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.8918] device (br-cea21f542557): carrier: link connected
Aug 15 17:32:20 nas-b NetworkManager[897]: <info>  [1660577540.8920] device (vethae0de61): carrier: link connected

kB Team-Icon

Supporter, Wikiteam
Avatar von kB

Anmeldungsdatum:
4. Oktober 2007

Beiträge: 7572

Wohnort: Münster
Zitieren
16. August 2022 09:35

iceman80 schrieb:

[…] 

sudo systemctl status snap.network-manager.networkmanager.service

Du rennst den NetworkManager als snap und zusätzlich auch als natives Programm? Wozu das? Das scheint mir ein sehr kreativ konfiguriertes, weit vom Standard abweichendes System zu sein!

Deaktiviere diesen snap und starte den Rechner neu. Zeige dann: 

nmcli general ; nmcli device ; nmcli connection | cat

Wenn es nicht schlechter funktioniert als vorher, entferne diesen snap. Er ist für normale Ubuntu-Installationen nicht erforderlich, sondern wird nur für Ubuntu Core empfohlen.

iceman80

(Themenstarter)

Anmeldungsdatum:
18. September 2013

Beiträge: 37
Zitieren
16. August 2022 10:42 (zuletzt bearbeitet: 16. August 2022 11:23)

Hi,

eine Nacht drüber schlecht geschlafen und nun zu folgenden Erkenntnissen gekommen:

  • 1. Das System läuft auf einer SSD über USB3 angeschlossen. Also konnte ich sehr problemlos ein SystemImage von vor dem upgrade einspielen (Ein Hoch auf die Backup!). Folglich bin ich wieder auf 20.04 und alles läuft wie immer.

  • 2. Auch auf 20.04 lief der snap.network-manager.service nicht. Was aber anscheinend keine Probleme bereitet hat.

  • 3. Im Netz gab es zu dem Fehler dann den Hinweis, das man Snap deinstallieren sollte und danach wieder installieren soll. Danach lief snap normal, hatte aber in der aktuellen Version keinen network-manager Service mehr.

Ich bleibe jetzt erstmal wieder auf 20.04 und schaue mir die ssh Problematik unter 22.04 in einer ruhigen Minute an.

Danke für Euere Hilfe. Wofür ich snap benötige und mit welcher Installation es auf das System gekommen ist konnte ich noch nicht herausfinden.
Antworten |