Debian Configuration :: CIFS Mount Causes 90-sec Timeout Delay During Shutdown
Nov 17, 2015
I'm using Debian 8.2 from a very recent download of the latest NetInst (less than 2 weeks). I'm sort of new to Linux - More accurately, I've used Unix and Linux extensively in the past, so most of my knowledge is dated. In particular, the whole systemd / systemctl paradigm is completely new to me.
Problem: I've added an entry to /etc/fstab to mount a NAS drive as CIFS. When I do a system shutdown or reboot, the system hangs for 90 seconds trying to unmount the NAS. If I manually umount the NAS prior to shutdown / reboot everything works fine.
I've done a fair amount of investigation and web searches, but haven't found a fix yet. Apparently several people were encountering similar problems about a year back, and it seems pretty clear that the root cause what ordering of steps in the shutdown process, e.g., WLAN being turned off before unmounting filesystems. This seems to have been resolved for most users (no one is discussing it any more), but I'm now running into the same issue. Ugh.
I tried to add a shell script to /etc/rc0.d to umount the NAS first in the shutdown process. This had no effect. I assume this is because the new systemd / systemctl paradigm supplants the old /etc/rc model of runlevel control, though it is rather baffling (to me, at least) as to why /etc/rc* still exists if the system is no longer using it...?
Here's some things I'd like to try, but how to proceed:
1. In the new systemd / systemctl paradigm, how do I examine and change the ordering of steps in the shutdown process? I've seen a lot of documentation on systemd, but nothing tells me how to do what I used to be able to do with /etc/rc with a simple rename of a symlink. If I knew how to look at the order of shutdown and change that ordering, I'm fairly certain I could identify and resolve this issue.
2. Is there some other way to mount my CIFS NAS other than editing /etc/fstab? Is it possible that my manual edit to /etc/fstab is the cause of this issue? My research into systemd indicates that it IS supposed to be compatible with /etc/fstab. I have not yet found documentation describing how to mount a filesystem at boot WITHOUT editing /etc/fstab ...
So after having spent the past half year preparing to abandon Windows and come over to Debian I finally made the switch last night only to realize I forgot one important thing... I didn't figure out how to map the network drive on my Windows server (currently learning to replace this with Debian as well) to my Debian system.
I have read about 15 links but keep getting the following error: Mount Error (6): No such device or address
Here is what I'm trying to enter into my terminal (with important bits removed for security of course)
mount -t cifs //xxx.xxx.xxx.xxx/Network_Storage/ -o username=xxx,password=xxx /mnt/cifs
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
I have Linux debian 7.7.0 i386-amd64 under VBox 4.3.20 and here is the problem:::
When I open the menu from Linux's top-right corner and click SHUT DOWN..., it shows the dialog with choices, and that Linux guest will automatically shutdown after 60 seconds and I need to change that delay value to 3 seconds. Of course I could just re-click Shut Down -button again, but I don't want to do it. Period.
By Googling I found these "instructions" for UBUNTU:
None of this worked on my 13.04 system. In the end I re-compiled gnome-session.
In gsm_shell.c and gsm_logout_dialog.c change #define AUTOMATIC_ACTION_TIMEOUT from 60 to 5
I have a PC104 running debian. I have 3 hard drives (in addition to the one booting) mounted in fstab by UUID. I use the options defaults,error=remount-ro. However, this means that when I boot with the hard drives not attached, I have to press Ctrl-D to bypass when the boot discovers the drives are missing. Is there a timeout commandoption I can add to fstab so that it automatically continues booting even if the hard drives are not attached? I could not find anything on a timeout command. (I tried adding timeout=1000 but no-random guess)
I've mounted a kind of proxy to map some cifs folders, 150 aprox. It umounts and mounts everything each hour, to check on changes on a configfile managed by a secretary, she just edits a file with names and I prepared a cron to notice the new mountpoints. It's a debian, no desktop , no nothing else. Just mount.cifs and apache2 to let the master webpage access to some files on each user samba home. The server has 4 cores and 2Gb of RAM. It's brand new, but it goes very slow.
Does anyone have an idea why is that working so slow? The apache is working well, it's the shell which is working extremelly slow.
I try to connect my Debian Jessie to my Windows share
This is what I have done:
-> 1 - create an .smbcredentials file located in my /home directory (with account / password and domain) -> 2 - implement /etc/fstab with information like that : //192.168.x.x/Animes/media/Animes cifs uid=toto,dir_mode=0777,file_mode=0777,credentials=/home/.smbcredentials,iocharset=utf800
and when I try to go on my windows share, I have this message:
An error occurred while accessing 'Home', the system responded: mount: only root can mount //192.168.x.x/Audio-Video-01 on /media/Audio-Video-01
I think about one thing, if uid=toto is different in fstab than my current debian account session name, it is possible the problem came because of that?
I'm trying to lower consumption of my server/HTPC. After wakeup from pm-suspend server/HTPC is ready to use in 1 or 2 seconds .For example if I suspend it while watching movie in KODI, after resume movie starts playing instantly. But some services (SSH and SAMBA) are not running. I thought it was network problem so I change configuration to static (not DHCP). SAMBA and SSH starts like 15 seconds after wakeup.
When I boot up, or come out of standby, etc, it takes about a minute for my Windows shares on Win 7 to show up under Network. Is there anything I can try that will make this initial connection faster? Either on Debian or the Win7 machine? I have the latest Debian vanilla. This is over wifi. My other devices list the shares right away.
I have a windows 7 box and a debian 5.0 box connected to a linksys wrt300n router. I can access the linux box from windows 7 through ssh. I used to be able to access the linux box from outside the LAN, but when I was messing with the ssh port configuration (at least I think this was what happened), i lost my ability to connect. I tried writing a new sshd_config file so that it is much simpler:
Protocol 2 PasswordAuthentication no UsePAM yes
I tried directly connecting the linux box to the internet to rule out a router firewall issue that i was missing. iptables -L yields nothing, as I have since rebooted the machine since messing with iptables rules. But still, when I try to ssh in from outside the LAN, I get a connection timeout error after a 10-15 second hang.
On a Debian 5.0.8 I have a problem with OpenSSH server (sshd): when connecting to it from another host there is always a 10 seconds delay before sshd gives login prompt to the client. After the connection is established the communication goes on without any interruption. This long delay started to happen a few months ago and sshd_config was not changed at that time.
Here is a short description of the conversation between the putty client (on MS Windows) and sshd: - putty client starts connection to sshd - 10 s delay - sshd returns "login as:" - user types username in putty window - sshd returns "password:" - user types password in putty window - sshd returns MotD and shell prompt
Here is a short description of the conversation between the OpenSSH client (on a Debian 6) and sshd: - client does "ssh firstname.lastname@example.org" - 10 s delay - sshd returns "Password:" - user types password - sshd returns MotD and shell prompt
I tried connecting from: - local host - NO DELAY - a host on the same subnet - delay exists - a host on another subnet - delay exists
I've found the following suggestions but to no avail (of course I restarted sshd after changing its configuration): - on server put "UseDNS no" at the end of /etc/ssh/sshd_config - in /etc/hosts on the server define mappings between IP addresses and host names for the ssh clients - on client use "GSSAPIAuthentication no" in /etc/ssh/ssh_config
I have a Debian VPS running Lenny and I'm trying to setup a way to run remote desktop sessions from it. I went with FreeNX, NX client for windows from nomachine, XDM and xfce4. All seems to have installed well, but I can't start an NX session on my box. I can connect to the server and authenticate, but the client hangs on "Downloading the session information," eventually timing out. The log output is below - I'm not even seeing an error message. Any ideas?
The only thing I noticed during install, which was about 400 packages since this was a barebones VPS, was that I should consider recompiling the kernel with CONFIG_SOFTWARE_SUSPEND=y. I don't know if this has any impact on session information, however, since this is a new session, not one I'm trying to resume.
Linux box info: root@mytestbox:~# uname -a Linux mytestbox 2.6.32-30-generic-pae #59-Ubuntu SMP Tue Mar 1 23:01:33 UTC 2011 i686 GNU/Linux
Windows box info: Windows Server 2008 SP2 Enterprise I've verified via --verbose output that mount.cifs is indeed processing the passed on options.
root@mytestbox:~# mount -t cifs //10.1.1.10/Test /root/testwin --verbose -o credentials=/root/testcreds,rw,nocase,noperm,noacl,nounix,noserverin o,iocharset=utf8,file_mode=0777,dir_mode=0777
Yet, when I type mount all it reports is (rw,mand). The share works just fine, and I can see the masking (all files are showing as rwxrwxrwx as expected etc) but mount is not listing the options?!
Is this normal expected behavior? Is there a bug report on this? I've google'd to the best of my capabilities and could not locate any such information which is why I decided to hit the forums prior to filing a bug.
I have a network share mounted with cifs which does not work as expected. It should automount at boot and dismount at shutdown. It does not automount at boot, but "# mount -a" will mount it in the gui after booting finishes. This I can live with, but at shutdown or reboot, the cifs share hangs for about 30 seconds before dying. My /etc/fstab entry code...
I saw a bug report about the cifs umount issue, but can't find it at the moment. I did notice that it was a very old bug. If I remember to do "# umount /media/data-srv" before rebooting, all is fine, but I seem to constantly forget and then stew as the system hangs for an extra 30-45 seconds. I've tried several things to automate it including shutdown scripts added to /etc/init.d/ and elsewhere, but nothing seems to work. Anyone have this issue and find a work-around?
I have a SMB share being mounted during boot using a /etc/fstab entry.All that seems to work fine, but on shutdown or reboot I found that the system hangs for a variable period trying to unmount the share. It appears from the log that the unmount is happening after the network connections are closed.Is there someway around this, or is there some other way I should be mounting the share so that it is closes successfully at restart or shutdown?
When I click logout or shut down I get a countdown saying I will be logged out or shut down in 60 seconds, then it counts down. I can click the "shut down now" button, but I find this behavior incredibly irritating. When I click logout I would like to logout NOW.
I search many hours on the web for wipe my ram in a secure way and i find nothing good/secure/work exept URL... and i think it's the best solution for wipe RAM at shutdown!Im a newbie user and i want to implement this solution on my debian system at shutdown, i think its very easy because TAILS is based on debian! Does someone can put the procedures for get that on a debian box please?
Without being paranoiac, it seems possible to keep the memory content for some minutes after shutdown and dump it accessing directly to the hardware.So how to fill the memory with constant or random pattern before halting? Is there a kernel option that I can give at boot time , or an other tool I can install from Debian/Ubuntu to achieve this ?
I have looked all over the place but I can't find if this is possible. I am running Debian 6 as a media server (SMB) and it is tied to a UPS, I used gnome power management to set up a low battery shutdown but this UPS also is powering another embedded computer. So, I was wondering if it was possible to have a script run (to log in and shut down the embedded system) before gnome power management shuts down the Debian server. I know I could probably get it to run on every shutdown, but I am looking for low power only.
Samba doesn't seem to disconnect on shutdown except by timing out, causing a loooong Lucid shutdown. (I can disconnect manually before shutdown by unmounting the Samba shares, and shutdown is then very fast.) Apparently Network Manager is somehow involved. I've installed a NM shutdown Samba script which works for the first user account, but not for the second user account (which was created and then put into the admin group).
I've been using linux for a few months. Recently I have installed debian jessie and I'm learning how to secure my laptop. I have installed
Code: Select allapt-get install sysv-rc-conf
to shutdown few services that I believe I don't need at boot which I found very useful. Among others I have deselected avahi-daemon, cups, cups-browsed, etc. The problem is that, after rebooting, when running:
Code: Select allnetstat -lntup
I still find 'avahi-daemon: r' and 'cupsd' running. I have tried
I'm using Debian Sid xfce on my lenovo laptop. When i try to shutdown, the screen always stays on (the fans turn off). It says "reached target shutdown", then this happens: [URL] .... and then it hangs. I have to press the power button to shut it down. (I have the same problem with reboot). I had the same issues with Jessie.
Things i tried so far and didn't work:
Code: Select allshutdown -h now shutdown -p now halt poweroff systemctl poweroff init 0
I edited /etc/default/grub and added the following options at "GRUB_CMDLINE_LINUX_DEFAULT":
acpi=force, acpi=off*, acpi=noirq
*acpi=off: shutdown (not reboot) worked a few times but i didn't have wifi and power manager didn't seem to work
none of them worked..
I have no energy or wake up options at my BIOS.
I found out that i can normally reboot with the Alt + sysrq + REISUB key combination.
I'm running a Debian on a laptop (actually a netbook: Asus EEE 1001PX) as a cheap homeserver. However I'd like it to automatically "shutdown -h NOW" when I remove the AC plug (switch it off at the wall). Otherwise I have to ssh to it and call it myself, and that just sucks Can I somehow detect the removal of AC power and upon that run a script ?
on my netbook I've tried to make possible for my user to shutdown without needing a password. battery could run low when I'm not in front of it. Editing sudoers has allowed my user to shutdown the system, but Gnome still prompts me for the root password whenever root is logged in too. That's usually the case, because to avoid entering the root password multiple times whenever I need elevated privileges and not wanting to cache the root password, I keep a Root Terminal always open.
I'm having some trouble in trying to make a clean solution and tougher time searching to not get the basic mounting pages/posts. So I thought I'd throw this out hereFor Oracle, we have an app server that runs /sharedapps and is an NFS mount for all other app/db nodes. What I'm working on now is that on this app server that hosts/exports /sharedapps file system has a sub folder with a CIFS mount (/sharedapps/data/appmount). e thing is that the remote nodes with the NFS mount to /sharedapps don't see the remote data in /sharedapps/data/appmount, only the main app server that has the CIFS connection. Realistically it makes sense why, but I'm trying to research if there is a way to have it do so. This is where I'm struggling. We are working on this in a dev instance right now but soon to be in production. In production, there are many DB nodes that could process a request which is why it would be best to have the NFS connection follow the remote CIFS connection
in configuring a fresh install of Squeeze. I discovered that it is possible to power off the system under gnome simply by pressing the power button or by selecting the "Shut Down" entry on "System" menu.However I need to restrict this option only to root. How can I do that?