Ubuntu
network-manager package

n-m should not tear down interfaces during shutdown

Bug #128316 reported by Jonh Wendell on 2007-07-25

This bug report is a duplicate of: Bug #42121: Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Triaged	Medium	Unassigned

Bug Description

Binary package hint: network-manager

When shut downing, the sendsigs script sends kill signal to all remaing processes, including NetworkManager, which disables the network.

I have some mount shares (cifs) on the network, then when script umountnfs.sh is called it hangs while trying to umount that shares, because there is no network anymore.

Revision history for this message

Alexander Sack (asac) wrote on 2007-07-29: Re: [Bug 128316] n-m should not tear down interfaces during shutdown

On Wed, Jul 25, 2007 at 05:31:25PM -0000, Jonh Wendell wrote:
> Public bug reported:
>
> Binary package hint: network-manager
>
> When shut downing, the sendsigs script sends kill signal to all remaing
> processes, including NetworkManager, which disables the network.
>
> I have some mount shares (cifs) on the network, then when script
> umountnfs.sh is called it hangs while trying to umount that shares,
> because there is no network anymore.
>

I agree with you ... however this needs to be investigated
... e.g. what side effects does it have if you restart network manager
et al.

- Alexander

Brian Murray (brian-murray) on 2007-08-20

Changed in network-manager:
importance:	Undecided → Medium
status:	New → Confirmed

Revision history for this message

Alexander Sack (asac) wrote on 2007-09-13:

I would implement this once we have agreed that network-manager is allowed to tear down managed interfaces during startup; however, this goes hand in hand with not touching _any_ interfaces listed in /etc/network/manager ... decision on this approach is still pending. Stay tuned.

Changed in network-manager:
status:	Confirmed → Triaged

Revision history for this message

Alistair Phipps (alistairphipps) wrote on 2007-10-23:

There may be a more general issue here with network manager behavior, but the specific issue raised by the reporter is a duplicate of bug #42121 -- marking as duplicate.

Revision history for this message

Alistair Phipps (alistairphipps) wrote on 2007-10-23:

See bug #105831 for a report relating to the network manager behavior.

Revision history for this message

Jonh Wendell (wendell) wrote on 2007-10-23:

I don't think it's a dupe. See the bug title.

This issue (as the title says) belongs to N-M.

The sysinit thing is another issue, so, 2 different bugs. Please, revert the dupe.

Revision history for this message

Alistair Phipps (alistairphipps) wrote on 2007-10-24:

Thanks for following up on your report. I understand your concern, but the issue in your description -- CIFS unmount hanging on shutdown -- is the same as the previously reported bug #42121. This can occur in some circumstances even if network-manager is not used and so IMHO is not directly related to network-manager tearing down interfaces. Also, the resolution I linked to in that bug should resolve the issue you describe.

Bug #105831 specifically relates to the network manager behavior you talk about in your title and describes a separate issue this causes. So, it looks like bug #42121 covers your description, and bug #105831 covers your title.

I marked this as a duplicate because I experienced the same issue -- and would also like to see a packaged resolution -- and feel that's most likely to happen by having fewer bug reports that accurately describe specific testable issues. But, if you still feel this isn't a duplicate, you should be able to change the duplicate tag yourself.