Debian Configuration :: NFS Shares In Fstab - Error: Mount.nfs4: Access Denied By Server While Mounting (null)
Feb 2, 2010
I run a mediaserver on Archlinux, working perfectly (or almost). I have set up NFS v3 and that worked for me on these clients:
- Debian Lenny
- Archlinux 64bit
Now I've upgraded my Lenny-box to squeeze and I see that 2 of my 3 shared folders (tdone and twatch) are mounted like they should and the third one (media) doesn't come up. A 'mount -a' as root gives this error: mount.nfs4: access denied by server while mounting (null) My relevant fstab-lines:
i'm trying to setup a nfs4 server and client. i followed the instructions in
[URL]
The SERVER is on 192.168.89.1 running Xubuntu 10.04, and the CLIENT is on 192.168.89.128 running Ubuntu 10.10. Firewall is disabled on both the server and the client for testing purposes. /etc/default/nfs-kernel-server on the SERVER:
Code:
# Number of servers to start up RPCNFSDCOUNT=8 # Runtime priority of server (see nice(1))
[code]....
because we want UID/GUID to be mapped from names. This way, server and client do not need the users to share same UID/GUID. In that case,
1. Should i set those 2 fields to "no" and "yes" respectively instead?
2. Or else, how do i make sure that the uid on the server is mapped to something useful on the client instead of nobody and nogroup?
i'm trying to setup a nfs4 server and client. i followed the instructions in [URL](nfsv4 quick start section) and [URL] The SERVER is on 192.168.89.1 running Xubuntu 10.04, and the CLIENT is on 192.168.89.128 running Ubuntu 10.10. Firewall is disabled on both the server and the client for testing purposes. /etc/default/nfs-kernel-server on the SERVER:
Code:
# Number of servers to start up RPCNFSDCOUNT=8 # Runtime priority of server (see nice(1))
[code]....
On the [URL], i see some steps related to portmap on the "NFS Server" and "NFS Client" sections. Would i need those steps as well? There's also a list of steps on [URL] (linked from [URL]. Are those necessary?
EDIT: Running showmount on the client seemed to show that NOTHING is shared on the server:
I just built an AMD Phenom II Six Core with 4 Gigs Ram a 160Gib / and swap, and (2) Two Tb mirror for Raid (data storage) I had been using DMRAID in the deprecated box but this box has MDADM v3.1.4 - 31st August 2010 from source (on MDADM wikipedia).
I have no permission problems with using the raid and dmraid is un-installed. The raid is working perfectly and is mounted in my fstab with ext4 defaults 0 2 as my options.
I have two exports /media/raid/Test /test
Both show IP and subnet on the showmount -e for the server. I can mount the test just fine on the server. I cannot, however, mount the /media/raid/Test error: mount.nfs: access denied by server while mounting hostname:/media/raid/Test Using dmraid I am able to have the deprecated box export and mount nfs shares from the raid but using MDADM on the new computer, I cannot. I get similar results with pointing MYSQL's data folder to a location on the "/media/raid/Database" (even with apparmor entries).
I've just made the switch from Ubuntu to Debian Squeeze and am having trouble connecting external media (be it a USB stick or an ext HD). The error I am getting when I connect anything via usb is the following:
Error mounting: mount exited with exit code 1: helper failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
I have a server running Red Hat Enterprise Linux ES (2.6.9.55.ELsmp). When it starts up I get the following error: Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.10 starting WARNING: can't access (null) exec of init ((null)) failed!!!: 14 unmount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!
After that I got no response from the OS. I have the installation CD, so I tried to start the rescue mode, while going through the steps I received an error stating that mounting to /mnt/sysimage failed and that if I want to I can access a shell. I really don't know what to do from here
Using Xubuntu 10.04 to connect to some Windows XP shares by adding lines to fstab. The network shares are not mounted at boot, but can be mounted from the command line, after the OS has booted and everything is up. I am suspecting the network isn't up yet, when fstab is processed. I tried adding the option "_netdev" to the relevant network share lines in fstab, but the shares still don't mount automatically at boot up. I read that this option only works for NFS and I am using CIFS. Can someone confirm that _netdev only works for NFS ?
I've seen solutions involving running a mount script after the OS is fully loaded, or running a cron job to periodically check the status of the share and mount if needed. Good workaround but doesn't address the root cause. Is there any other way (besides the _netdev option) to delay mounting of network shares that appear in fstab until the network interface is up ?
I set up a nfs server that is working locally only, on remote I get this: root@poc ~]# mount -t nfs storage:/var/ftp/pub /net mount.nfs: access denied by server while mounting storage:/var/ftp/pub
This is my exports file: /var/ftp/pub/downloads 192.168.1.23(rw,sync) /var/ftp/pub 192.168.1.23(ro,sync) this is my rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100011 1 udp 875 rquotad .....
Firewall has 2049 open only. Other services suck as nfs or status, lockd have random ports, so firewalled.
I recently installed CentOS 5 as my server. I have samba running 100%, today i was working on NFS i had it semi working at one point where i could mount to the shared folder but i could not see any of the files in it, now when ever i try to access it i get, mount.nfs: access denied by server while mounting 192.168.1.100:/Server
I can not use nfs from F10 client to F12 server. nfs mount on F10 to F12 times out anf nfs4 mount gives "mount.nfs4: mounting localhost:/home failed, reason given by server: No such file or directory" I have tried to close firewall and set selinux to permissive mode on both client and server with same result. Samba works fine. On server [root@flokipal ~]# mount -t nfs4 localhost:/home /media/tonlist mount.nfs4: mounting localhost:/home failed, reason given by server: No such file or directory
but
[root@flokipal ~]# mount -t nfs localhost:/home /media/tonlist [root@flokipal ~]#
Since FC6, NFS became very finicky and seemingly causes servers to randomly denying mounts from some terminals but not others, with all exactly the same new FC installation and exactly the same hardware - crazy!. The only difference is hostnames of the terminals trying to mount NFS volumes on the server and I made sure that /etc/hosts on all terminals and servers contain each others ip addresses and hostnames. I always uninstall SELinux which is truly a huge pain in a corporate environment. Is there ANY way I can relax the NFS authentication on the server in order to make sure clients can mount volumes?
e.g. the following is encountered often, with sometimes crazy situations that clients can only mount nfs volum es from the server after I first boot the server and then ALL the terminals. It is painful as you might agree! Other way round, no go, client will not mount until server is booted and then client booted.
In this case I really prefer windows lackey security. It works. Never mind how crappy windows is, at least I don't have diabolical access problems on servers.. NFS used to be very nice about 6 years ago but truly sucks recently imo. /]# mount -o soft -t nfs nfsserver:/public /xfer mount.nfs: access denied by server while mounting nfsserver:/public
I'm trying to setup a NFS4 server (no security, local home network behind FW). It seems that I'm missing something because 'rpcinfo -p' does not list v4 for NFS: petit-pois:/home/eric# rpcinfo -p
I'm running sid, and doing weekly updates. Recently I've been unable to mount nfs shares on one of my home computers. I haven't changed any settings, and nfs works fine on the other computers on my small home network. I suspect an update messed something up with nfs.
I setup a Samba share and I cannot connect. I can mount in on local host but when I CD to the folder I mounted the share on I get access denied when I run ls.
I cannot install files from source (tar.bz, tar.bz2, tar.gz, etc) my latest attempt began at tuxfiles. following the 'tutorial', if you will, I managed to unpack the files; but when it came to the ./configure step, I got the following error: zsh: no such file or directory: ./configure
Here I figured different distros, slight variances, so instead I tried putting a space in the command (./ configure), and got this error. zsh: permission denied: ./
So finally I tried both ./configure and ./ configure as su and I still got the same errors... this is the same problem that I've always had when installing from source. I am using Fedora 12.
Using NFS on the client machine. I am running scientific linux on my machine. Its working fine for my other machines.I have made sure that the firewall is disabled and also the selinux too. here is what i get when i use rpcinfo -p on the client.
rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100007 2 udp 868 ypbind 100007 1 udp 868 ypbind .....
I've all of a sudden been getting permission denied for almost everything I try to do. Upon logging in, I get a huge amount of "/dev/null: Permission denied"
The only way I can manage to get to the terminal is by Ctrl-C. It never brings up the command line, unless I do that.
If I try to startX, I get errors, also saying permission denied, and then one that says
Code:
I also get many "failed" errors when booting, most of them saying that a file could not be found/located.
Check the thread link at the top for other information in the first post.
I could reinstall Debian, but the computer I am using is a Libretto 110CT (64MB RAM), which has only a PCMCIA drive, for which I have a USB port replicator. There is no CD drive.
It was also a custom install fitted for the computer, so I'd rather not have to set everything up again, nor would I know how to exactly, as I've never done it before.
I have a command line that mounts the disk of my mobile
Code:
It works, but there is a problem with it. Every folder and file has root:root ownership, so I am unable to change anything. Even when I change permissions manually, it does not work.
Now, I want to move this to fstab but have no idea how an fstab line should look like. Obviously, I want to also have rw access to the disk.
When trying to mount samba share off of domain member server sysimage in Windows receive error "There are currently no logon servers available to service this logon request". When trying to mount.cifs from PDC to samba share on sysimage receive error "mount error(13): Permission denied".
PDC is ClearOS 5.2 named "dc0" Samba file server is CentOS 5.5 x86_64 named "sysimage" dc0 Samba version is samba - 3.5.5-1.1.v5.i386 sysimage Samba version is samba-3.0.33-3.29.el5_5.1.x86_64
dc0 is configured correctly to my knowledge, windows machines can join domain, domain users can log into windows machines, user directories are mapped properly, logon scripts run properly. sysimage ldap authentication is set up as shown in "Procedure 7.1.
Code: //192.168.0.242/websites /mnt/supercube cifs rw,user=XXX,pass=XXX,iocharset=utf8,file_mode=0777,file_mode=0777,dir_mode=0777,uid=XXX 0 0 But it doesn't auto mount with everything and disconnects whenever I suspend my computer. The only way to get it to mount is with Code: sudo mount -a and it mounts fine with no error.
Did lucid change the way it uses fstab or something? Obviously writing mount -a isn't a huge concern, but it kind of destroys the point of putting it in my fstab.
I have not done the SMTP debug yet but just from basic troubleshooting, I think I know what the problem is. My mail server is rejecting my web server from sending mail due to 'relay access denied':
Code: root@www:# telnet mail.domain.tld 25 Trying 211.113.101.135... Connected to mail.domain.tld. Escape character is '^]'.
Anybody know how to make an ext3 or 4 partition start up at boot with only the owner and its group having read and write access permissions.I don't want 'others' to have folder access. This is what i have done. / etc/fstab:/dev/sdb5/media/Data ext4 owner 1 2 The folder starts on the boot since it has been allocated a folder as u can see. Next i changed the the ownership and the group ownership of the folder:chown johnny:johnny /media/DataThe problem is that other users can few my partition since 'others' have read access. How do i change that to zero access?
It's been awhile since I posted anything which is a good sign my install has been working well and I have been able to handle most everything. However, I'm not able to handle this issue. I recently installed F11 and everything went well. But, when trying to see my other computers on the local network, I cannot. I receive this error message: Unable to mount location Failed to receive shared list from server. I understand the message as it is obvious, but do not know how to fix it.
I just ugraded from karmic, and it all went without a hitch. Except now when i boot i get... Error while mounting /etc/fstab press s to skip or m for manual recovery.
Pressing s works and i have a working machine, but i would like to fix this. Not tried the manual recovery yet as i have no idea about fstab and don't want to break it.
After having problems with lxde crashing while running Jessie, and re-installing Wheezy, I am not able to mount my WinXP drive. In the past I was able to run pcmanfm and mount the drive from there. It would ask for my root password and then would mount the drive. Now, however, when I click on the drive icon it gives me an error message saying authentication required.
One thing is that when I installed Wheezy I had the WinXP drive disconnected so as to not inadvertently install Wheezy on the wrong drive (I have two identical drives). After installing I connected the WinXP drive and then did a grub update. I can boot either drive, as expected, but I can not mount the WinXP drive from pcmanfm. Do I need to change the Policykit?
I wanted to use NFS4 with id mapping. I followed the write up at [URL] and basically have everything working.
The problem is that I cannot write a file unless I have group write permissions. On the server the user has uid = 1000, gid = 1000. On the client the user has uid =1699, gid = 1000. Both have the same user name.
On the client the directory listing properly shows the user name and the group name. If the file on the server is 644, the client cannot write to the file. If it is 664 on the server, then the client can write to the file.
/etc/export on server contains:
Code: /export 172.24.84.0/24(rw,fsid=0,insecure,no_subtree_check,async) /export/myuser 172.24.84.0/24(rw,nohide,insecure,no_subtree_check,async) /etc/fstab on client contains:
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
xx@xx.com SMTP error from remote mail server after initial connection: host [URL] [ip address]: 550 Access denied...
I'm using Opensuse 11.4 updated from 11.3, update from 11.2 updated from. I'm mounting at boot time (in fstab) some shares from an opensuse 11.2 server. Mounting worked fine in 11.2, 11.3 and also in 11.4 but suddenly (maybe an automatic update?) It stopped working.... sometimes.
Sometimes they are mounted properly but sometimes they aren't. When mount fails I get a log error: "rpc.statd is not runninf but is required for remote locking. Either use '-o nolock' to keep locks local or start statd"
If I run manually (as root) mount -a the shares mount properly always, so I thought it was a problem of timing (the service starting late) so I tried to get a script to run after the network initialitation, the script does: "mount -a". But it doesn't work either.
