Your message dated Fri, 08 May 2015 13:13:20 +0200
with message-id <1711096.xVEM1sj2fJ@hipnos>
and subject line Re: [Pkg-utopia-maintainers] Bug#745029: network-manager:
automatically kills scripts that take longer than 3 seconds
has caused the Debian Bug report #745029,
regarding network-manager: automatically kills scripts that take longer than 3
seconds
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
745029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745029
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.8.8-5
Severity: normal
Dear Maintainer,
after upgrading in a Testing machine with systemd to 0.9.8.8-5 version we get
nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' took
too long; killing it.
with no mount of nfs partitions.
Investigating we found
https://wiki.archlinux.org/index.php/NetworkManager#Avoiding_the_three_seconds_timeout
so we replace the symlink /etc/systemd/system/dbus-org.freedesktop.nm-
dispatcher.service creating the script file /etc/systemd/system/dbus-
org.freedesktop.nm-dispatcher.service with the following content:
.include /lib/systemd/system/NetworkManager-dispatcher.service
[Service]
RemainAfterExit=yes
and enable the script file with permissions rwxr-xr-x.
Doing so we workaroud the problem ...
Regards!
Guido
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.113+nmu3
ii dbus 1.8.0-3
ii init-system-helpers 1.18
ii isc-dhcp-client 4.2.4-7
ii libc6 2.18-4
ii libdbus-1-3 1.8.0-3
ii libdbus-glib-1-2 0.102-1
ii libgcrypt11 1.5.3-4
ii libglib2.0-0 2.40.0-2
ii libgnutls26 2.12.23-13
ii libgudev-1.0-0 204-8
ii libmm-glib0 1.0.0-4
ii libnl-3-200 3.2.24-1
ii libnl-genl-3-200 3.2.24-1
ii libnl-route-3-200 3.2.24-1
ii libnm-glib4 0.9.8.8-5
ii libnm-util2 0.9.8.8-5
ii libpam-systemd 204-8
ii libpolkit-gobject-1-0 0.105-4
ii libsoup2.4-1 2.46.0-2
ii libsystemd-login0 204-8
ii libuuid1 2.20.1-5.7
ii lsb-base 4.1+Debian12
ii policykit-1 0.105-4
ii udev 204-8
ii wpasupplicant 1.1-1
Versions of packages network-manager recommends:
ii crda 1.1.2-1
ii dnsmasq-base 2.68-1
ii iptables 1.4.21-1
ii modemmanager 1.0.0-4
ii ppp 2.4.5+git20130610-4
Versions of packages network-manager suggests:
ii avahi-autoipd 0.6.31-4
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi, after upgrading network-manager to version 1.0.0.5 (unlike with the
previous versions) we restore the symlink and everything is now ok.
So we think we can close this bug ...
Regards!
Guido
On Wed, 21 May 2014 10:53:20 +0200 MAG4 Piemonte <[email protected]> wrote:
> Dear Michael and Dan, thank you for the answers.
> So we will wait NM next versions to test the restore of the symlink ...
> Regards!
>
> Guido
>
> In data lunedì 19 maggio 2014 12:01:39, Dan Williams ha scritto:
> > On Mon, 2014-05-19 at 17:05 +0200, Michael Biebl wrote:
> > > Am 17.04.2014 13:13, schrieb MAG4 Piemonte:
> > > > Package: network-manager
> > > > Version: 0.9.8.8-5
> > > > Severity: normal
> > > >
> > > > Dear Maintainer,
> > > > after upgrading in a Testing machine with systemd to 0.9.8.8-5 version
> > > > we get
> > > > nm-dispatcher.action: Script
> > > > '/etc/NetworkManager/dispatcher.d/01ifupdown' took
> > > > too long; killing it.
> > > > with no mount of nfs partitions.
> > > > Investigating we found
> > > > https://wiki.archlinux.org/index.php/NetworkManager#Avoiding_the_three_seconds_timeout
> > > > so we replace the symlink /etc/systemd/system/dbus-org.freedesktop.nm-
> > > > dispatcher.service creating the script file /etc/systemd/system/dbus-
> > > > org.freedesktop.nm-dispatcher.service with the following content:
> > > > .include /lib/systemd/system/NetworkManager-dispatcher.service
> > > > [Service]
> > > > RemainAfterExit=yes
> > > > and enable the script file with permissions rwxr-xr-x.
> > > > Doing so we workaroud the problem ...
> > > > Regards!
> > > >
> > >
> > >
> > > That is intended behaviour. Scripts are not supposed to start long
> > > running tasks. Please fix your scripts to not do that.
> > >
> > > Afaics there is nothing to fix on the NM side, right Dan?
> >
> > At the moment it's intended behavior. NM 0.9.9+ have bumped the timeout
> > to 20 seconds, and for 0.9.10 we're planning to make NetworkManager
> > block on dispatcher scripts for up/down. Obviously, that makes your
> > network connections take longer to connect or disconnect if the
> > dispatcher scripts are stupid, but then the stupid scripts need to get
> > fixed to not take so long.
> >
> > Note that for NFS especially, network connections can drop without
> > warning, especially on WWAN/WiFi/Bluetooth, and at that point the
> > connection is completely gone, and NFS just has to handle that without
> > blocking.
> >
> > Dan
> >
>
>
--- End Message ---
