[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
In https://wiki.archlinux.org/index.php/talk:NFS#NetworkManager-wait- online I found a workaround that works for me (ArchLinux has been using systemd for a long time already): * create a file /lib/systemd/system/auto_share.service with the following contents: After=NetworkManager-wait-online.service Before=systemd-user-sessions.service * execute the following commands in a terminal: systemctl enable NetworkManager-wait-online systemctl reenable auto_share.service Having done this once, booting and shutdown works fine, even with still mounted cifs shares. It stays the same after system reboot. Even if this workaround will work fine for everyone (?), this bug should be fixed permanently anyhow! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577885 Title: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi) Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 with no issue. I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the command "umount /media/server ..." I have not tested if this also occurs when I am connected via ethernet. I think it is because the (Wifi)Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577885 Title: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi) Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 with no issue. I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the command "umount /media/server ..." I have not tested if this also occurs when I am connected via ethernet. I think it is because the (Wifi)Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Unfortunately, the bug seems to be back in Ubuntu 16.04 (Xenial) now, probably due to changements in the boot and shutdown sequences. See also [bug 1577885]. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) Status in dbus package in Ubuntu: Fix Released Status in dhcdbd package in Ubuntu: Invalid Status in netbase package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in wpasupplicant package in Ubuntu: Fix Released Status in dhcdbd source package in Lucid: Invalid Status in dhcdbd source package in Natty: Invalid Status in sysvinit package in Debian: New Bug description: IMPORTANT: this bug has enough information; please don't post _anything_ unless a developer asks for specific feedback! By posting to this bug you only make it harder for a developer to spot the gem comments. Please use the "me too feature" of launchpad to signal that you are affected and would like to see this fixed. I installed smbfs,and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: /// /home/hamish/ cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of "cifs" in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
This bug seems to be quite similar to "[Bug 211631] Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)", fixed in 2013. Has Xenial brought back an old problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1577885 Title: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi) Status in systemd package in Ubuntu: Confirmed Bug description: Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 with no issue. I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the command "umount /media/server ..." I have not tested if this also occurs when I am connected via ethernet. I think it is because the (Wifi)Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
