Bug 463278
| Summary: | Incorrect D-Bus system bus user ID in system.conf | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jay Turner <jturner> |
| Component: | dbus | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.3 | CC: | benl, srevivo, syeghiay |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-20 20:54:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jay Turner
2008-09-22 19:57:21 UTC
Some additional information. Got the dbus selinux issues resolved, loaded up the new NetworkManager (0.7.0-0.11.svn4088.el5) and here's what I get when restarting NM (picking just the stuff related to eth0, the wireless interface): Sep 23 14:30:40 haring NetworkManager: <info> eth0: driver is 'ipw3945'. Sep 23 14:30:40 haring NetworkManager: <info> eth0: driver does not support SSID scans (scan_capa 0x00). Sep 23 14:30:40 haring NetworkManager: <info> Found new 802.11 WiFi device 'eth0'. Sep 23 14:30:40 haring NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_13_02_4a_10_55 Sep 23 14:30:40 haring NetworkManager: <info> Trying to start the supplicant... Sep 23 14:30:44 haring NetworkManager: <info> (eth0): device state change: 1 -> 2 Sep 23 14:30:44 haring NetworkManager: <info> (eth0): bringing up device. Sep 23 14:30:44 haring kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Sep 23 14:30:44 haring NetworkManager: <info> (eth0): preparing device. Sep 23 14:30:44 haring NetworkManager: <info> (eth0): deactivating device. Sep 23 14:30:44 haring NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed The last entry is quite interesting, as that's new with the NM rebase and might be the cause of the problems. After NM gets launched, is a wpa_supplicant process running? Should be something like: /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log Very strange. No, there's not a wpa_supplicant process. In fact, the wpa_supplicant service is chkconfig'd off for all runlevels. The good news is that after configuring and starting the service manually, appears things are working. Appears that NM is no longer handling the initiation of wpa_supplicant correctly. Let me know what other information I can provide. Ok, that means we have issues with D-Bus service activation, probably due to the SELinux stuff. You shouldn't need to chkconfig the supplicant service on because it should be started on-demand by NM via dbus service activation. If you chkconfig wpa_supplicant off again, and set selinux to permissive mode, then reboot, does you get the supplicant process? Issue appears to be an incorrect user ID in the dbus system bus configuration. Will build dbus-1.1.2-10.el5 to fix. 1.1.2-10.el5 makes things lots happier. dbus-1.1.2-10.el5 included in 20080930.0 candidate trees. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0094.html |