VPN tunnel is closed before network drives are unmounted when shutting down

[Eric Jones]

During the shutdown or reboot process, the VPN connection established by openvpn is closed prior to attempting to unmount NFS mounts. This causes the computer to wait for several minutes trying to gracefully unmount a connection that is no longer established. The scripts link in /etc/rc6.d, etc should be renumbered so that the NFS mounts are removed prior to severing the VPN connection.

[Chuck Short (zulcss)]

Are you using dapper or breezy, and are you kernel server or user space?

Thanks
chuck

[PC (pieter-claassen)]

On Tuesday 23 May 2006 02:05, ChuckShort wrote:
> Are you using dapper or breezy, and are you kernel server or user space?
kernel server and dapper.

The problem seems to be that the nfsumount script installed in rc.S are
installed using S prefixes while the nfsumount script should be installed
with a K (therefore be called before the S scripts with the right parameter.)

Pieter

>
> Thanks
> chuck
>
> ** Bug 42122 has been marked a duplicate of this bug

[Eric Jones (jonesy-gmail)]

I'm running Dapper and the code is running in user space I believe.

[Lazy (ubuntu-bugs-oittaa)]

Hardy Heron has the same problem with cifs mounts.

[Thierry Carrez (ttx)]

I would say it all depends on what your configuration looks like. In one case you may have some openvpn bits lying on a NFS or CIFS mount, so you prefer to unmount those at the very last time. In another case you established an NFS or CIFS mount over your OpenVPN tunnel, and you prefer to shutdown the network filesystems before you shutdown OpenVPN itself.

If you are in the second case, you should probably leverage the down and down-pre options of OpenVPN to close the NFS/CIFS filesystems you opened over the tunnel before you shutdown OpenVPN...

[MFauzilkamil Zainuddin (apogee)]

As this bug has duplicate report, I'm marking it as confirmed.

[karaluh (karaluh)]

I can confirm this on Dapper

>I would say it all depends on what your configuration looks like.

Agreed, but more common scenario is tuneling NFS/CIFS over VPN than accesing network file server to start VPN, so VPN before mount on boot and after umount on shutdown should be the default.

[Thierry Carrez (ttx)]

This is linked to bug 211631: network filesystems should generally be unmounted before network services go down.

[Thierry Carrez (ttx)]

OpenVPN would need to be protected in sendsigs to survive until umountnfs is called.

[Patrick Donnelly (batrick)]

What's the status on this bug?

[Thierry Carrez (ttx)]

The boot process has been overhauled in karmic/lucid -- would be good to know if this is still an issue.

[Joshua Powers (powersj)]

Thank you for taking the time to report this bug. In an effort to keep
an up-to-date and valid list of bugs to work on, I have reviewed this
report verifying it still requires effort and occurs on a supported
version of Ubuntu.

I am marking this bug incomplete due to the lack of responses or
updated information stating this still affects currently supported
releases.

It is unfortunate that we were unable to resolve this defect, however,
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.

[Launchpad Janitor (janitor)]

[Expired for openvpn (Ubuntu) because there has been no activity for 60 days.]