Bug 1829178 - Fedora 32 introduced dhcp client re-connections. dhcp client periodically failing.
Summary: Fedora 32 introduced dhcp client re-connections. dhcp client periodically fai...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1817788 (view as bug list)
Depends On:
Blocks: 1841937 1843052
TreeView+ depends on / blocked
 
Reported: 2020-04-29 06:28 UTC by animuspexus
Modified: 2020-06-03 15:00 UTC (History)
17 users (show)

Fixed In Version: NetworkManager-1.22.12-1.fc32
Clone Of:
: 1841937 (view as bug list)
Environment:
Last Closed: 2020-06-03 15:00:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of journalctl output on error (35.02 KB, image/png)
2020-04-29 06:28 UTC, animuspexus
no flags Details
system message on error screenshot (27.91 KB, image/png)
2020-04-29 06:29 UTC, animuspexus
no flags Details
more screenshots (300.58 KB, image/png)
2020-04-29 06:59 UTC, animuspexus
no flags Details
more screenshots 2 (302.62 KB, image/png)
2020-04-29 06:59 UTC, animuspexus
no flags Details
screenshot 3 (900.51 KB, image/png)
2020-04-29 07:21 UTC, animuspexus
no flags Details
adding complete log file (102.43 KB, application/gzip)
2020-04-29 08:36 UTC, animuspexus
no flags Details

Description animuspexus 2020-04-29 06:28:13 UTC
Created attachment 1682721 [details]
screenshot of journalctl output on error

Description of problem:

31 was ok. updated my desktop to 32 today.
using dhcp in my home net. "dhcp-server-router: PC yet running f31.
periodically, each few minutes, dhcp client crushing and restarting network connection, closing all connections to router.

my network card is integrated:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
	Subsystem: ASUSTeK Computer Inc. Device 8672
	Flags: bus master, fast devsel, latency 0, IRQ 126
	Memory at f7100000 (32-bit, non-prefetchable) [size=128K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] PCI Advanced Features
	Kernel driver in use: e1000e
	Kernel modules: e1000e

adding screenshots

Comment 1 animuspexus 2020-04-29 06:29:31 UTC
Created attachment 1682723 [details]
system message on error screenshot

Comment 2 Pavel Zhukov 2020-04-29 06:47:52 UTC
Nothing to do with dhcp here. Reassigning to proper component

Comment 3 animuspexus 2020-04-29 06:59:05 UTC
Created attachment 1682730 [details]
more screenshots

and another one journal screenshot. starting from line, I guess, "grace period expired"

Comment 4 animuspexus 2020-04-29 06:59:31 UTC
Created attachment 1682731 [details]
more screenshots 2

Comment 5 Beniamino Galvani 2020-04-29 07:02:35 UTC
Can you please do the following (as root user):

 - edit /etc/NetworkManager/NetworkManager.conf and set level=TRACE in the [logging] section
 - set "RateLimitIntervalSec=0" in /etc/systemd/journald.conf
 - reboot
 - wait that the problem happens again
 - attach the output of 'journalctl -u NetworkManager -b' to this bugzilla

After attaching the journal log, you could change the DHCP plugin
used by NM to solve your issue. To do this, set 'dhcp=dhclient' or
'dhcp=systemd' in the [main] section of /etc/NetworkManager/NetworkManager.conf.
Then restart NM with 'systemctl restart NetworkManager'.

Thank you!

Comment 6 animuspexus 2020-04-29 07:21:21 UTC
Created attachment 1682736 [details]
screenshot 3

with asked settings right after this error

Comment 7 Beniamino Galvani 2020-04-29 07:29:59 UTC
(In reply to animuspexus from comment #6)
> Created attachment 1682736 [details]
> screenshot 3
> 
> with asked settings right after this error

Unfortunately the log doesn't fit in one screen. Could you instead do:

 journalctl -u NetworkManager -b > log.txt

and attach the log.txt file? If you didn't reboot since then, you don't need to perform again the previous steps.

Comment 8 animuspexus 2020-04-29 08:36:36 UTC
Created attachment 1682762 [details]
adding complete log file

I didn't rebooted. changed to dhcp=system after uploaded last screenshot (this helped). complete log, includingly screenshoted timings, is in attachment.

Comment 9 Beniamino Galvani 2020-04-29 16:55:22 UTC
Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/486

Comment 10 Thomas Haller 2020-06-03 14:55:06 UTC
*** Bug 1817788 has been marked as a duplicate of this bug. ***

Comment 11 Thomas Haller 2020-06-03 15:00:38 UTC
This should be fixed https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c5d1d4c498c50dfc7d2d18b213a117dd1199f1de, which was backported and released as 1.22.12. It should thus be fixed on Fedora 32 with package NetworkManager-1.22.12-1.fc32.


Note You need to log in before you can comment on or make changes to this bug.