Linux mint connection failed

Linux Mint Forums

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

Activation of network connection failed

Post by patrick999 » Tue Dec 13, 2022 7:20 pm

I have a new custom build, using an ASRock Rack x570d4u board and an AMD Ryzen 5 Pro 5650G CPU (no GPU, as it’s integrated on chip).

I installed LM21, and I keep getting the intermittent error message «Connection failed. Activation of network connection failed.»

It doesn’t seem that it’s actually losing network connectivity, at least that I notice, but it flashes this error message every couple of minutes. In reality, it may be losing network connectivity for an instant, but it’s being restored quickly. In any event, it makes it unstable and not something I’d rely on as a server.

I’ve tried everything to fix this. I’ve used both the on-board ethernet port or, at various times, two separate network cards that I had lying around to connect to the router. I’ve flashed the bios. I’ve reinstalled Mint, including with a freshly downloaded image. But the result is always the same: this error message appears every couple of minutes.

I have looked in syslog, and it says something like «state change: ip-config failed (reason; ip-config unavailable), sys-iface-state «managed.»

If anyone thinks it would be helpful, I could post more of syslog in this thread. The only reason I’m not doing so now is that the server is in a corner in the basement, and I’m accessing it over IPMI and don’t have copy and paste available. I’d need to go down there with a USB drive and copy the relevant portion of the log file that way, which I’m willing to do if anyone would find it helpful.

Any thoughts? I’ve been troubleshooting this for the better part of a day and don’t have a clue where to go from here.

Last edited by LockBot on Tue Jun 13, 2023 10:00 pm, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Re: Activation of network connection failed

Post by sleeper12 » Tue Dec 13, 2022 9:05 pm

lsemmens Level 11
Posts: 3710 Joined: Wed Sep 10, 2014 9:07 pm Location: Rural South Australia

Re: Activation of network connection failed

Post by lsemmens » Tue Dec 13, 2022 10:10 pm

I get that regularly on a computer that has Two network sockets. As I only use one of them , every now and then the computer tries to connect via the disused socket. It does not affect my network usage so I just ignore it. Strangely enough, if I disable that socket in network settings, it turns itself back on at random, no biggie to me.

Check network settings to see if it attempting to connect via an unused device, wifi, network adaptor et al.

Re: Activation of network connection failed

Post by patrick999 » Wed Dec 14, 2022 1:50 am

Sleeper12 that suggestion is for wireless networks. I’m using a wired network and have tried both a 1GB RJ45 port and two different 10GB sfp+ cards, with the same result. It also happens whether I’m in an installed LM21 installation or Mint Live bootable media.

semmens I really don’t want to have to live with a flaky network connection. This is going to be my main server and workstation, and I’d like it to be rock solid.

Re: Activation of network connection failed

Post by sleeper12 » Wed Dec 14, 2022 2:01 am

Re: Activation of network connection failed

Post by patrick999 » Wed Dec 14, 2022 3:05 am

Here is some of the output from inxi -Fxxxrz (incidentally, I notice the «virtual ethernet type USB»; I have no idea what that is and wonder if it’s somehow causing problems):

ystem:
Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
Desktop: Cinnamon 5.4.12 tk: GTK 3.24.33 wm: Mutter vt: 7
dm: LightDM 1.30.0 Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy
Machine:
Type: Server Mobo: ASRockRack model: X570D4U serial:
UEFI: American Megatrends LLC. v: P1.50 date: 08/01/2022
CPU:
Info: 6-core model: AMD Ryzen 5 PRO 5650G with Radeon Graphics bits: 64
type: MT MCP smt: enabled arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB
L3: 16 MiB
Speed (MHz): avg: 2349 high: 2350 min/max: 400/4464 boost: enabled cores:
1: 2350 2: 2350 3: 2350 4: 2349 5: 2350 6: 2346 7: 2349 8: 2348 9: 2350
10: 2350 11: 2349 12: 2350 bogomips: 93606
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
. . .
Network:
Device-1: Intel I210 Gigabit Network vendor: ASRock driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 26:00.0
chip-ID: 8086:1533 class-ID: 0200
IF: enp38s0 state: down mac:
Device-2: Intel I210 Gigabit Network vendor: ASRock driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0
chip-ID: 8086:1533 class-ID: 0200
IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac:
Device-3: American Megatrends Virtual Ethernet type: USB
driver: cdc_ether bus-ID: 5-5.3:5 chip-ID: 046b:ffb0 class-ID: 0a00
serial:
IF: enx12333986a6c3 state: unknown speed: -1 duplex: half mac:
. . . .

Repos:
Packages: apt: 2129
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com vanessa main upstream import backport
2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse

Re: Activation of network connection failed

Post by patrick999 » Wed Dec 14, 2022 3:11 am

Also, here are some lines from syslog which I think are from when the problem is occurring:

avahi-daemon[846]: Joining mDNS multicast group on interface enx12333986a6c3.IPv6 with address fe80:32cd:fdb6:87fc.
Dec 13 17:45:46 [computer name] avahi-daemon[846]: New relevant interface enx12333986a6c3.IPv6 for mDNS.
Dec 13 17:45:46 [computer name] avahi-daemon[846]: Registering new address record for fe80:32cd:fdb6:87fc on enx12333986a6c3.*.
Dec 13 17:46:31 [computer name] NetworkManager[851]: [1670975191.0406] device (enx12333986a6c3): state change: ip-config -> failed (reason ‘ip-config-unavailable’, sys-iface-state: ‘managed’)
Dec 13 17:46:31 [computer name] NetworkManager[851]: [1670975191.0410] device (enx12333986a6c3): Activation: failed for connection ‘Wired connection 5’
Dec 13 17:46:31 [computer name] avahi-daemon[846]: Withdrawing address record for fe80:32cd:fdb6:87fc on enx12333986a6c3.
Dec 13 17:46:31 [computer name] NetworkManager[851]: [1670975191.0412] device (enx12333986a6c3): state change: failed -> disconnected (reason ‘none’, sys-iface-state: ‘managed’)
Dec 13 17:46:31 [computer name] avahi-daemon[846]: Leaving mDNS multicast group on interface enx12333986a6c3.IPv6 with address fe80:32cd:fdb6:87fc.
Dec 13 17:46:31 [computer name] avahi-daemon[846]: Interface enx12333986a6c3.IPv6 no longer relevant for mDNS.
Dec 13 17:46:31 [computer name] NetworkManager[851]: [1670975191.0590] dhcp4 (enx12333986a6c3): canceled DHCP transaction
Dec 13 17:51:31 [computer name] NetworkManager[851]: [1670975491.0512] policy: auto-activating connection ‘Wired connection 5’ (39ce19e8-6954-36ff-a06b-6b6c736baa69)
Dec 13 17:51:31 [computer-name] NetworkManager[851]: [1670975491.0517] device (enx12333986a6c3): Activation: starting connection ‘Wired connection 5’ (39ce19e8-6954-36ff-a06b-6b6c736baa69)

lsemmens Level 11
Posts: 3710 Joined: Wed Sep 10, 2014 9:07 pm Location: Rural South Australia

Re: Activation of network connection failed

Post by lsemmens » Wed Dec 14, 2022 4:30 am

patrick999 wrote: ⤴ Wed Dec 14, 2022 1:50 am Sleeper12 that suggestion is for wireless networks. I’m using a wired network and have tried both a 1GB RJ45 port and two different 10GB sfp+ cards, with the same result. It also happens whether I’m in an installed LM21 installation or Mint Live bootable media.

semmens I really don’t want to have to live with a flaky network connection. This is going to be my main server and workstation, and I’d like it to be rock solid.

I was not implying that my connection was flaky, it IS rock solid. The nuisance factor is the pop-up that tells me it is trying to connect to the unused adaptor. If yours is doing that, it might help us help you if you identify the likely cause, ’tis all. Those two reports will go a long way to helping, though.

Re: Activation of network connection failed

Post by patrick999 » Wed Dec 14, 2022 11:56 am

The problem might be resolved. There is something called «USB network» listed as an adapter in the gui network manager. I have no idea what that is or why it’s there. I built another server last year with the predecessor board, the ASRock Rack x470d4u, and there was no «USB network» on that, but with this board, the x570d4u, it’s there. In any event, I turned off that connection in the network manager and watched it for ten minutes without the warning message about failed activation appearing. In the past, it always appeared at least every two minutes. So, it might be resolved. I say «might» because the problem is intermittent and could return.

This appears to support lsemmens theory that it was another adapter interfering. In any event, as noted, it might be resolved.

Re: Activation of network connection failed

Post by patrick999 » Wed Dec 14, 2022 4:53 pm

And now I can report that «USB network,» a rogue adapter, will not stay turned off. I turned it off in the network manager, and the warnings about activation failure stopped. Then a few hours later, «USB network» mysteriously turned on again, and the warnings started again. As soon as I turned it off, however, the warnings stopped.

This sounds like the same behavior that isemmens described. Another adapter is present, and the warnings about activation failure occur. You can disable the other adapter, which causes the warnings to stop, but eventually the other adapter somehow becomes enabled again. At this point, I’m not going to worry about it too much. There are some extra USB ports installed in pcie that might be causing the rogue adapter to appear in the network manager, but I actually think the rogue adapter is associated with the motherboard and possibly bmp, which is server firmware. I might do some further investigation into this later, but for now, it appears that it’s another adapter interfering, and I’m not sure that there are even any drops. It’s probably just warning messages, as in Isemmens’ case.

Источник