Hide Forgot
Description of problem: NetworkManager logs too often, too much and not too clear. Version-Release number of selected component (if applicable): NetworkManager-0.8.3.996-1.fc14.x86_64 How reproducible: Upgrade after seeing bug 655322 fixed. See https://bugzilla.redhat.com/show_bug.cgi?id=655322 as well. Steps to Reproduce: 1. 2. 3. Actual results: see below Expected results: - less logging please - logging that is more clear: what interface is having this 'issue' and why is it worth to complain about? - NM_CONTROLLED was false! So the logic is flawed. Additional info: Mar 2 15:25:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:25:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:25:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:30:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:30:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:30:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:35:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:35:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:35:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:38:47 surfplank2 smartd[4131]: Device: /dev/sdd [SAT], 1 Currently unreadable (pending) sectors Mar 2 15:40:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:40:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:40:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:45:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:45:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:45:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:50:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:50:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:50:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:55:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:55:00 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed Mar 2 15:55:01 surfplank2 NetworkManager[2873]: ifcfg-rh: warning: NM_CONTROLLED was false but HWADDR or SUBCHANNELS was missing; device will be managed
Try to upgrade to NetworkManager-0.8.3.997-1.fc14.x86_64, please. That should help not to modify the ifcfg file every 5 mins and thus not issue the warning over and over. In order NM_CONTROLLED=no could be applied you have to have HWADDR set in your ifcfg file. Orherwise it is not possible to bind the configuration file to an interface.
I already had that version installed, but it needed a NM restart. After `service NetworkManager restart` the logging indeed quieted down, as it appears in a quick test. Thanks!
Recently I still saw quite a number of things being logged for a task that has already been done by the network.service file. (Also NM reports missing stuff, still complains about usb0 that will never have a static MAC address, etc. Result is that eth0 gets same IP as usb0. see other bugzilla entry for this feature)
No progress?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.