This bug is fixed for me by:
network-manager (0.9.8.8-0ubuntu6) trusty; urgency=medium
[ Martin Pitt ]
* Mark autopkgtests with isolation-machine as these tests can't run in
schroot or LXC.
[ Felix Geyer ]
* Don't check for TARGET_DEBIAN in patches. Upstream has removed the macro
** Changed in: network-manager (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient
The bug was apparent in 13.10, but I do not see it after upgrade to 14.04
(amd64).
I do not see dhclient in lsof output but I have not check with ps.
The bad surprise is that /etc/default/halt is ignored in 14.04.
(Consequence of systemd inclusion?)
--
You received this bug notification
Couldn't find anything like this in debian bugtracker.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
stopped
To
BTW it stops dhclient if I do disconnect from gnome's network-manager
menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is
Interesting .. should be possible to figure out the different code
paths, next time I have time to have a look...
On Wed, Mar 12, 2014 at 07:17:11PM -, Ivan Larionov wrote:
BTW it stops dhclient if I do disconnect from gnome's network-manager
menu.
--
You received this bug notification
So what should we do to get this bug fixed? Report in to NM developers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
Not sure it's an upstream bug - if you read back, there used to be
Debian-specific code wrapped in an #ifdef, which depends on a
preprocessor symbol that is no longer defined .. if you've got time you
could see if the seem problem ever existed in Debian, and if so, if/how
they fixed it ..
S.
On
OK, the commit that fixed things for me was upstream commit
52b3810b0e0d87bb47c6d77627d49fbb323d804d, fix NMPolicy/NMManager
refcounting. Not familiar with exactly how git works, but that seems to
have been cherry picked and reapplied to the main branch as
8c167c1f8f4338ccdc9906a9595e02c67fc1d9ca:
Looks like it doesn't print this messages as well.
I verified my package and I see this patches applied. No idea why
there're no debug messages from your patches.
** Attachment added: nm_start_stop_2.log
Seems that code path isn't being triggered at all for you. Interestingly,
older versions exhibit the same issue for me. Going to try to isolate the
commit that fixed things for me (binary search time!) .. hopefully then
will have some understanding of what's going on.
On 7 Mar 2014 18:01, Ivan
Interesting, your setup seems to skip a whole bunch of steps .. starting
with:
device state change: activated - disconnected
Will have a look at the source and see how that could get skipped.
Anything odd about your system - did you configure your wired connection
in n-m by hand?
--
You
Hmm, my best guess is that your connection never makes it to an
activated state .. can you grep your syslog for 'state ch.*activated'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
Connection configured automatically.
State changed to activated during nm start. Log attached.
** Attachment added: nm_start_stop.log
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614/+attachment/4010385/+files/nm_start_stop.log
--
You received this bug notification
Created new ethernet connection with all defaults — same isue, dhclient
isn't stopped after stopping NM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount:
Color me baffled. Try adding some more debug??
diff -ur network-manager-0.9.8.8/src/nm-policy.c
network-manager-0.9.8.8.sd/src/nm-policy.c
--- network-manager-0.9.8.8/src/nm-policy.c 2014-01-26 17:37:05.0
+
+++ network-manager-0.9.8.8.sd/src/nm-policy.c 2014-03-06
Syslog:
Mar 5 21:36:10 animeworld NetworkManager[16725]: debug [1394040970.362890]
[nm-netlink-monitor.c:164] link_msg_handler(): netlink link message: iface idx
2 flags 0x11043
Mar 5 21:36:11 animeworld NetworkManager[16725]: info (eth0): IP6 addrconf
timed out or failed.
Mar 5 21:36:11
NM with patch: https://launchpad.net/~xeron-oskom/+archive/network-
manager
BTW I don't see debug info from patch you provided.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
Weird - I'm not seeing it here. I added some debug to n-m a while back,
will see if I can find the patch..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot:
OK, if you can change /etc/init/network-manager.conf so the exec line
reads:
exec NetworkManager --log-level=DEBUG
And apply the attached patch to the n-m sources, rebuild install, what
happens? (As you need syslogd to stay up to log the results, just 'sudo
stop network-manager' and have a in
This problem still exists in the latest 14.04 with all updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
** Attachment added: Processlist at umountfs step
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614/+attachment/4005370/+files/psaux.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at this now, and getting sidetracked by RCS confusion .. what is
the difference between:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/network-
manager/trusty/files
and
http://bazaar.launchpad.net/~network-manager/network-
manager/ubuntu/files
? The latter seems to have
@oyvinst, the current NetworkManager in trusty (0.9.8.8-0ubuntu1) *does*
seem to stop dhclient:
Jan 26 17:25:02 xubuntu NetworkManager[1766]: info caught signal 15, shutting
down normally.
Jan 26 17:25:02 xubuntu NetworkManager[1766]: info (eth0): device state
change: activated - disconnected
We should probably remove the obsolete patches to avoid confusion.
** Patch added: Remove obsolete debian-specific patches that are no longer
compiled
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614/+attachment/3957801/+files/sd-nm.diff
--
You received this bug
lsof just before remount to read-only of root:
dhclient 1317 root 4w REG 8,5 578 530637
/var/lib/NetworkManager/dhclient-90ac51b1-a118-416f-a126-0ad83a2c7b9c-eth0.lease
.. and unclean shutdown as a result.
On a clean and up-to-date Ubuntu 13.10 installation. When patch exists
since april of
Still exists in 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
stopped
To manage notifications about this bug
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Considering that this might causes dataloss/filesystem corruption is
there any reason explaining why this patch has not been added yet in
13.04 networkmanager ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note for those wanting to apply the above patch: network-manager uses
quilt, and the above patch only patches the patches. So do quilt pop
-a after unpacking the source, then apply the patch above, then quilt
push -a to reapply the changed patches.
--
You received this bug notification because
I was able to apply the patch from post #2 now, thanks to Steve's hint.
Using the patched network-manager I don't experience any hangs at
shutdown/reboot anymore!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Extremely brief instructions are given in
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1073433/comments/120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
Thanks for your reply, Steve!
Unfortunately I'm on x86_64, so I'd have to build it myself I guess. Could you
give me a little hint on how to do that?
I issued a apt-get source network-manager and got 2 packages
(*ubuntu6.debian.tar.gz and *0.9.8.0.orig.tar.xz), I also downloaded the patch
I'm using raring and also having the issue of shutdown/restart hanging
for a short time due to mount: / is busy.
I made a script that executes ps -Af on shutdown/reboot and writes it to a
log file. (see attachment)
There's a long line containing /sbin/dhclient; I presume that indicates
dhclient
M4he, yes, looks like it. Does the patch above apply cleanly to n-m in
saucy? It solved things for me. If you're on x86-32 I can probably build
you a package to test easily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*raring, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
stopped
To manage notifications about this bug go to:
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
stopped
To manage notifications about this bug
I can confirm the above patch fixes the problem of dhclient still being
running on shutdown for me (once I figured out how to use quilt so I
could rebuild nm.)
Still need to a fix an upstart/ureadahead problem to get a clean
shutdown on my machine, but this is progress.
--
You received this bug
** Summary changed:
- dhclient is not stopped during shutdown
+ /etc/init.d/umountroot: mount: / is busy due to dhclient is not stopped
** Description changed:
The result is
mount: / is busy
and root filesystem recovery during next boot.
network-manager 0.9.8.0-0ubuntu3 in Raring
39 matches
Mail list logo
