Bug 1893223 - NetworkManager log spam in F33
Summary: NetworkManager log spam in F33
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 33
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-30 15:08 UTC by Jerry James
Modified: 2021-11-30 18:52 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 18:52:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Requested logs (25.76 KB, application/x-xz)
2020-11-03 21:51 UTC, Jerry James
no flags Details

Description Jerry James 2020-10-30 15:08:06 UTC
Description of problem:
I upgraded my home machine to F33 last night.  Ever since, NetworkManager has been writing this message to the system log every 7 to 8 seconds:

Oct 30 08:36:28 localhost.localdomain NetworkManager[1433]: <info>  [1604068588.2915] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost.localdomain'

Clearly I have not changed the hostname. :-)

Version-Release number of selected component (if applicable):
NetworkManager-1.26.4-1.fc33.x86_64

How reproducible:
Unknown.

Steps to Reproduce:
1. Unknown
2.
3.

Actual results:
Log spam about a nonexistent hostname change.

Expected results:
Don't write the log message so frequently, at the very least.

Additional info:
Off-topic: the bugzilla component description for the NetworkManager component is "NetworkManager VPN plugin for OpenVPN", which doesn't seem right.

Comment 1 Beniamino Galvani 2020-11-02 08:12:01 UTC
Please set 'level=TRACE' in the [logging] section of /etc/NetworkManager/NetworkManager.conf, set RateLimitBurst=0 in /etc/systemd/journald.conf, reboot and then attach the output of 'journalctl -u NetworkManager -b'. Thanks!

Comment 2 Jerry James 2020-11-03 21:51:16 UTC
Created attachment 1726403 [details]
Requested logs

Attached.  Thank you!

Comment 3 Jerry James 2021-06-07 15:30:56 UTC
There are users complaining about the log spam on users.org.  Can something be done about this, please?

As for the hostname change, hostnamectl shows that the static hostname is "localhost" and the transient hostname is "fedora".  I did not set either, so anaconda apparently did this to me.

Comment 4 Ben Cotton 2021-11-04 13:56:30 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-11-04 14:25:51 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-11-04 15:23:31 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2021-11-30 18:52:04 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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