Processed: Re: Bug#568971: modem manager rapidly fills up daemon.log
Processing commands for cont...@bugs.debian.org: severity 568971 important Bug #568971 [modemmanager] /usr/sbin/modem-manager: modem manager rapidly fills up daemon.log Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568971: modem manager rapidly fills up daemon.log
severity 568971 important thanks Jö Fahlke wrote: Package: modemmanager Version: 0.3-1 Severity: normal I had the same problem after an interactive upgrade with aptitude. But I noticed it before it filled up my harddrive :) The problem went away after invoke-rc.d dbus restart: == Stopping network connection manager: NetworkManager. Stopping Hardware abstraction layer: hald. Stopping bluetooth: bluetoothd. Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon. Stopping system message bus: dbus. Starting system message bus: dbus. Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. Starting bluetooth: bluetoothd. Starting Hardware abstraction layer: hald. Starting network connection manager: NetworkManager. == Attached are to excerpts from my syslog, one from the initial start of the modemmanager during upgrade and one from the restart of dbus above. I removed log entries for services I deemed irrelevant. If you suspekt some of the removed entries are indeed relevant, please ask for them. The thing that strikes me about the logs is that there is a flurry of restarts of the modemmanager by the NetworkManager in the same second, then nothing for exactly two minutes, then again a flurry of restarts and so on. Bye, Jö. -- System Information: Debian Release: squeeze/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages modemmanager depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst So far, this doesn't look like a modemmanager bug per se. It looks like dbus is not correctly picking up the installed modemmanager dbus policy file after installation, which leads to the flood of access denials. D-Bus uses inotify to monitor /etc/dbus-1 for changes, and there were fixes in 1.2.20 which particularly address bugs in the inotify handling [1]. So far, all bug reporters seems to have used dbus 1.2.16. 1.2.20 has migrated to testing already, so it is likely this particular issue won't show up again (and unless someone confirms this with dbus 1.2.20, I'll keep this bug at severity important). Nonetheless, there are a couple of things we might consider: 1.) modemmanager could reload dbus manually in postinst, to trigger a reload of the dbus config files 2.) network-manager should be more clever when trying to reconnect to modemmanager and not simply try to do it brute force. It could use something like a exponential back off. cheers, Michael [1] http://cgit.freedesktop.org/dbus/dbus/commit/?h=dbus-1.2id=8a9880ffd2b81df38bb0e3492bda7a9636ac0280 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#568971: modem manager rapidly fills up daemon.log
Hi, can you reliably reproduce this? Is a modem-manager process running? Was this directly after installing modemmanager? What lead to this bug, where you upgrading your system or something similar? What happens if you restart network-manager and/or dbus, do you still get the error messages in the daemon.log. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#568971: modem manager rapidly fills up daemon.log
Dear Michael, Luckily this problem did not occur again. I restarted my machine after the fill-up which caused several programs to not respond anymore in order to investigate what was going on. On Wednesday 10 February 2010 17:17:45 Michael Biebl wrote: Hi, can you reliably reproduce this? So no, I cannot reproduce this unfortunately. Is a modem-manager process running? Currently there is a modem-manager process running and everything seems fine again. Checking the logs reveals the following messages: Feb 11 06:55:51 mamma NetworkManager: info starting... Feb 11 06:55:51 mamma NetworkManager: info Trying to start the modem- manager... Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: init! Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: update_system_hostname Feb 11 06:55:51 mamma NetworkManager:SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e Feb 11 06:55:51 mamma NetworkManager:SCPluginIfupdown: management mode: unmanaged Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1c.1/:40:00.0/net/eth0, iface: eth0) Feb 11 06:55:51 mamma NetworkManager:SCPluginIfupdown: locking wired connection setting Feb 11 06:55:51 mamma NetworkManager:Ifupdown: get unmanaged devices count: 1 Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: (141091568) ... get_connections. Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: (141091568) ... get_connections (managed=false): return empty list. Feb 11 06:55:51 mamma NetworkManager:Ifupdown: get unmanaged devices count: 1 Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo) Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Feb 11 06:55:51 mamma NetworkManager:SCPlugin-Ifupdown: end _init. Feb 11 06:55:51 mamma NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Feb 11 06:55:51 mamma modem-manager: Loaded plugin ZTE Feb 11 06:55:51 mamma modem-manager: Loaded plugin Novatel Feb 11 06:55:51 mamma modem-manager: Loaded plugin Generic Feb 11 06:55:51 mamma modem-manager: Loaded plugin AnyData Feb 11 06:55:51 mamma modem-manager: Loaded plugin Option High-Speed Feb 11 06:55:51 mamma modem-manager: Loaded plugin Sierra Feb 11 06:55:51 mamma modem-manager: Loaded plugin Longcheer Feb 11 06:55:51 mamma modem-manager: Loaded plugin Ericsson MBM Feb 11 06:55:51 mamma modem-manager: Loaded plugin Option Feb 11 06:55:51 mamma modem-manager: Loaded plugin Nokia Feb 11 06:55:51 mamma modem-manager: Loaded plugin Gobi Feb 11 06:55:51 mamma NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Feb 11 06:55:51 mamma NetworkManager: info WiFi enabled by radio killswitch; enabled by state file Feb 11 06:55:51 mamma NetworkManager: info WWAN enabled by radio killswitch; enabled by state file Feb 11 06:55:51 mamma modem-manager: Loaded plugin MotoC Feb 11 06:55:51 mamma modem-manager: Loaded plugin Huawei Feb 11 06:55:51 mamma NetworkManager: info (eth0): carrier is ON Feb 11 06:55:51 mamma NetworkManager: info (eth0): new Ethernet device (driver: 'tg3') Feb 11 06:55:51 mamma NetworkManager: info (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Feb 11 06:55:51 mamma NetworkManager: info modem-manager is now available Feb 11 06:55:51 mamma NetworkManager: WARN default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files Feb 11 06:55:51 mamma NetworkManager: info Trying to start the supplicant... Was this directly after installing modemmanager? Yes it was directly after installing the updates with aptitude safe-upgrade (and modemmanager came along with them). What lead to this bug, where you upgrading your system or something similar? What happens if you restart network-manager and/or dbus, do you still get the error messages in the daemon.log. Maybe it was some race condition that occurred right after the update that caused the problem and rebooting the system (and thus restarting the network- manager and dbus too) helped to fix it. It was quite surprising to find my system in a (for me) somewhat unusable state after some updates. Furthermore I know that without being able to reproduce this issue, fixing it for others that install this package is tough. But unfortunately I cannot provide more information about it. Best regards Rico Moorman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a
