Description of problem: nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/13-named' took too long; killing it. nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/20-squid' took too long; killing it. NetworkManager[413]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/12-dhcpd' timed out. NetworkManager[413]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/13-named' timed out. NetworkManager[413]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/20-squid' timed out. ww1 dbus-daemon[412]: ppp0: error fetching interface information: Device not found dbus-daemon[412]: IP ppp0 no esta presente dbus-daemon[412]: ppp0: error fetching interface information: Device not found nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/12-dhcpd' took too long; killing it. NET[863]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/20-squid' took too long; killing it. NetworkManager[413]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/13-named' timed out. NetworkManager[413]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/20-squid' timed out. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.? 2. 3. Actual results: "warn" in logs Expected results: "clear" logs Additional info: NetworkManager-0.9.7.0-12.git20121004.fc18.i686 Executing "dispatchers" from shell, return without any problem.
The NM dispatcher uses 3 seconds timeout for the scripts. Is there any reason why the scripts should run that long? Did you inspect the scripts what they do? Did you modify them? E.g. 20-squid just reloads the squid configuration using systemctl: /bin/systemctl reload squid.service
"killed" scripts are fedora default, but I have other script (supposed not killed in logs) that could take 6 seconds or more while connect remote machine.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Do we really need to kill the scripts? Can we just stop waiting for them? I have a local script that restarts autofs, but that can take longer than 3 seconds - and killing leaves autofs down: Jan 21 11:25:46 paiute systemd: Started Network Manager Script Dispatcher Service. Jan 21 11:25:47 paiute nm-dispatcher.action: NetworkManagerDispatcher: performing autofs stop Jan 21 11:25:47 paiute NetworkManagerDispatcher: performing autofs stop Jan 21 11:25:47 paiute systemd: Stopping Automounts filesystems on demand... Jan 21 11:25:47 paiute automount[13514]: umount_autofs_indirect: ask umount returned busy /data Jan 21 11:25:49 paiute automount[13514]: umount_autofs_indirect: ask umount returned busy /home Jan 21 11:25:50 paiute nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/28-autofs' took too long; killing it. Jan 21 11:25:51 paiute systemd: Stopped Automounts filesystems on demand.
(In reply to Orion Poplawski from comment #4) > Do we really need to kill the scripts? Can we just stop waiting for them? > I have a local script that restarts autofs, but that can take longer than 3 > seconds - and killing leaves autofs down: > > Jan 21 11:25:46 paiute systemd: Started Network Manager Script Dispatcher > Service. > Jan 21 11:25:47 paiute nm-dispatcher.action: NetworkManagerDispatcher: > performing autofs stop > Jan 21 11:25:47 paiute NetworkManagerDispatcher: performing autofs stop > Jan 21 11:25:47 paiute systemd: Stopping Automounts filesystems on demand... > Jan 21 11:25:47 paiute automount[13514]: umount_autofs_indirect: ask umount > returned busy /data > Jan 21 11:25:49 paiute automount[13514]: umount_autofs_indirect: ask umount > returned busy /home > Jan 21 11:25:50 paiute nm-dispatcher.action: Script > '/etc/NetworkManager/dispatcher.d/28-autofs' took too long; killing it. > Jan 21 11:25:51 paiute systemd: Stopped Automounts filesystems on demand. In the future NM will Just Wait Longer and yes, it could just continue without killing the script.
I'm experiencing the same problem in Fedora 19. I can participate in testing reporting about this "feature" request if some developer would handle the implementation.
*** This bug has been marked as a duplicate of bug 982734 ***