Hide Forgot
Description of problem: NetworkManager writes Activation message to the system log *very* often. Version-Release number of selected component (if applicable): NetworkManager-0.9.2-1.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. Use NetworkManager 2. 3. Actual results: System log is flooded with messages, 12 lines at roughly 12 - 18 second intervals An instance is shown below. Expected results: NetworkManager should only log significant networking events. Additional info: This is the set of messages that is periodically written to the system log. This machine has a wireless networking device, but I have another Fedora16/x86_64 machine with no wireless devices and the same flooding of the system log occurs on that machine too. Jan 16 13:19:02 earth NetworkManager[880]: <info> Activation (p7p1) Stage 4 of 5 (IP6 Configure Get) scheduled... Jan 16 13:19:02 earth NetworkManager[880]: <info> Activation (p7p1) Stage 4 of 5 (IP6 Configure Get) started... Jan 16 13:19:02 earth NetworkManager[880]: NetworkManager[880]: <info> Activation (p7p1) Stage 4 of 5 (IP6 Configure Get) scheduled... Jan 16 13:19:02 earth NetworkManager[880]: NetworkManager[880]: <info> Activation (p7p1) Stage 4 of 5 (IP6 Configure Get) started... Jan 16 13:19:02 earth NetworkManager[880]: <info> Activation (p7p1) Stage 5 of 5 (IP Configure Commit) scheduled... Jan 16 13:19:02 earth NetworkManager[880]: <info> Activation (p7p1) Stage 4 of 5 (IP6 Configure Get) complete. Jan 16 13:19:02 earth NetworkManager[880]: <info> Activation (p7p1) Stage 5 of 5 (IP Configure Commit) started... Jan 16 13:19:02 earth NetworkManager[880]: NetworkManager[880]: <info> Activation (p7p1) Stage 5 of 5 (IP Configure Commit) scheduled... Jan 16 13:19:02 earth NetworkManager[880]: <info> Activation (p7p1) Stage 5 of 5 (IP Configure Commit) complete. Jan 16 13:19:02 earth NetworkManager[880]: NetworkManager[880]: <info> Activation (p7p1) Stage 4 of 5 (IP6 Configure Get) complete. Jan 16 13:19:02 earth NetworkManager[880]: NetworkManager[880]: <info> Activation (p7p1) Stage 5 of 5 (IP Configure Commit) started... Jan 16 13:19:02 earth NetworkManager[880]: NetworkManager[880]: <info> Activation (p7p1) Stage 5 of 5 (IP Configure Commit) complete.
You may add this to /etc/NetworkManager/NetworkManager.conf to make logging less verbose: [logging] level=WARN See 'man NetworkManager.conf' for more information.
This is a symptom of a larger problem I think... The issue is that NetworkManager is continually thrashing -- disconnecting and reconnecting the network interfaces. It has made the latest version of NM completely unusable for me. My suspicion is that it has something to do with IPv6 configuration or more people would be complaining about it.
Well, I don't know if it's IPv6-related or not, but both of my F16/x86_64 machines are showing this behavior and both have IPv6 connectivity. Only one of the machines has a wireless network device, so that rules out wireless as the cause of the constant logging. The IPv6 addresses are handed out by the radvd daemon running on the network server to which both machine are connected. Let me know if I can provide any more config info.
One of my co-workers pointed out a workaround. I had set up IPv6 connectivity on the network connection to "Automatic". Setting it to "Ignore" seems to have calmed things down. Even with that setting, the kernel still picks up router advertisements and I get an IPv6 address. It apparently just makes NM get out of the way. The one thing that it noticeable is that it doesn't set the IPv6 address of the DNS server in /etc/resolv.conf, but I suppose I can live with that until this is properly fixed.
BTW, his conjecture was that NM was timing out the IPv6 configuration on an interval much smaller than the router advertisement interval. Increasing the broadcast frequency on the router might also help here.
*** Bug 761313 has been marked as a duplicate of this bug. ***
In fact...this may be a duplicate of bug 675226. I'm not certain of that but the suggested workaround is the same.
Bug 761313 suggests a more serious problem that just flooding the log with messages. I'm seeing both problems on two machines. The more serious problem is that on one machine the frequent reconfiguration causes breaks in other services. On one machine where I have forked-daapd this means that music playing over the network to an airport express will randomly stop. I can live with that ... However, on another machine a VPN connection using openconnect will randomly fail every few minutes. Reconnecting wouldn't be so bad except that the VPN server assigns a different IP address every time so any connections I have open will eventually timeout. This can happen, and has happened, half way though a subversion commit, a git push, sending a mail message, buying books from Amazon. For me, this makes this bug rather serious.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.