Home > Default > Problems setting up an NFS server

Problems setting up an NFS server

October 11Hits:1
Advertisement
Hi everybody,
I just completed my first arch install. :-)
I have a desktop and a laptop, and I installed Arch on the desktop (the laptop runs Ubuntu 9.10). I had a few difficulties here and there, but I now have the system up and running, and I'm very happy.
I have a problem setting up an NFS server. With Ubuntu everything was working, so I'm assuming that the Ubuntu machine (client) is set-up correctly. I'm trying to troubleshoot the arch box (server) now.
I followed this wiki article: http://wiki.archlinux.org/index.php/Nfs
Now, I have these problems:
- when I start the daemons, I get:
[[email protected] ~]# /etc/rc.d/rpcbind start
:: Starting rpcbind [FAIL]
[[email protected] ~]# /etc/rc.d/nfs-common start
:: Starting rpc.statd daemon [FAIL]
[[email protected] ~]# /etc/rc.d/nfs-server start
:: Mounting nfsd filesystem [DONE]
:: Exporting all directories [BUSY] exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.1.1/24:/home".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x
[DONE]
:: Starting rpc.nfsd daemon [FAIL]
- If I mount the share on the client with "sudo mount 192.168.1.20:/home /media/desktop", IT IS mounted but I can't browse it because I have no privileges to access the home directory for the user.
my /etc/exports looks like this:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/home 192.168.1.1/24(rw,sync,all_squash,anonuid=99,anongid=99))
/etc/conf.d/nfs-common.conf:
# Parameters to be passed to nfs-common (nfs clients & server) init script.
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=
# Options to pass to rpc.statd.
# See rpc.statd(8) for more details.
# N.B. statd normally runs on both client and server, and run-time
# options should be specified accordingly. Specifically, the Arch
# NFS init scripts require the --no-notify flag on the server,
# but not on the client e.g.
# STATD_OPTS="--no-notify -p 32765 -o 32766" -> server
# STATD_OPTS="-p 32765 -o 32766" -> client
STATD_OPTS="--no-notify"
# Options to pass to sm-notify
# e.g. SMNOTIFY_OPTS="-p 32764"
SMNOTIFY_OPTS=""
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=
# Options to pass to rpc.idmapd.
# See rpc.idmapd(8) for more details.
IDMAPD_OPTS=
# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=
# Options to pass to rpc.gssd.
# See rpc.gssd(8) for more details.
GSSD_OPTS=
# Where to mount rpc_pipefs filesystem; the default is "/var/lib/nfs/rpc_pipefs".
PIPEFS_MOUNTPOINT=
# Options used to mount rpc_pipefs filesystem; the default is "defaults".
PIPEFS_MOUNTOPTS=
/etc/hosts.allow:
nfsd: 192.168.1.0/255.255.255.0
rpcbind: 192.168.1.0/255.255.255.0
mountd: 192.168.1.0/255.255.255.0
Any help would be very appreciated!

Answers

Thanks, I finally got it working.
I realized that even though both machines had the same group, my Ubuntu machine (client) group has GID 1000, while the Arch one has GID 1001. I created a group that has GID 1001 on the client, and now everything is working.
I'm wondering why my Arch username and group both have 1001 rather than 1000 (which I suppose would be the default number for the first user created).
Anyway, thanks again for your inputs.

Read other 5 answers

Tags:

Related Articles

  • Problems setting up an NFS serverOctober 11

    Hi everybody, I just completed my first arch install. :-) I have a desktop and a laptop, and I installed Arch on the desktop (the laptop runs Ubuntu 9.10). I had a few difficulties here and there, but I now have the system up and running, and I'm ver

  • Cannot enable nfs serverNovember 30

    Hello -- I have some problem to enable the nfs server on a Ultra60 running Solaris 10 06/06. First, svcs tells me the service is not enable: bash-3.00# svcs -l /network/nfs/server fmri svc:/network/nfs/server:default name NFS server enabled false sta

  • NFS: server reboot - client problem with "file handle" - no unmontOctober 11

    Hello, when I restart a NFS-server and a client has a NFS-share on it still mounted, that NFS-share becomes unusable on the client: everything causes the client complain about an old "file handle", even trying to unmount that share! So my questi

  • Solaris 10 NFS caching problems with custom NFS serverNovember 30

    I'm facing a very strange problem with a pure java standalone application providing NFS server v2 service. This same application, targeted for JVM 1.4.2 is running on different environment (see below) without any problem. On Solaris 10 we try any kin

  • NFS locking problem, solaris 10, nfsd stops servingNovember 30

    Hi all, First time poster, short time viewer. To set the scene... I have an x86 SAM-QFS installation under management currently. The SAM-QFS infrastructure consists of 2x meta data controllers and 2x file service heads, that currently share out NFS (

  • Memory leak in  NFS serverOctober 11

    Hi all, I have a problem with 2 SunFire 240 (4Gb of Ram) with solaris 10 in a Veritas Cluster. These nodes are 2 NFS server and they have 10 nfs client. We have a memory leak on these servers. The memory utilization increase day by day. The memory se

  • Possible bug in the arch NFS server package?October 11

    i run the nfs server on my arch box, exporting to a debian box and an arch laptop. whenever the arch server reboots lately, the shares don't automatically remount properly on the clients. they're listed in mtab, but if i ls or try to access the direc

  • Solaris 9 NFS clients and Mac OS X 10.3.8 NFS Server issuesOctober 11

    I have a situation where I'm using a Mac OS X Server machine as my file server for heterogeneous mix of clients, Solaris 9 being one of them. The NFS server portion of Mac OS X seems to have some quirks. I made the move to a Mac OS X server from a co

  • Cannot start nfs.serverNovember 30

    I refer to the SUN Blade 100 workstation that is installed with Solaris 8 OS bought 2 month ago. # ps -ef|grep nfs daemon 242 1 0 17:07:24 ? 0:00 /usr/lib/nfs/statd root 513 1 0 17:07:37 ? 0:00 /usr/lib/nfs/mountd # /etc/init.d/nfs.server start # ps

  • Nfs server not responding, hanging startup after 10.10.3 updateNovember 30

    The system boots up fine and I enter my password, then it sits for over 6 minutes with a spinning wheel. The console shows: 4/16/15 10:35:30.000 AM kernel[0]: nfs server localhost:/zz0Lo64HS_Mb5IMJ_JdkXi: not responding 4/16/15 10:35:34.214 AM netbio

Copyright (C) 2019 wisumpire.com, All Rights Reserved. webmaster#wisumpire.com 14 q. 0.570 s.