[opensuse] Can't start NFS server 13.1
I'm trying to set up a NFS server on 13.1. I have tried both with and without NFSv4 support. If I try with, Yast complains it can't start idmapd and if I try without NFSv4, it complains it can't stop idmapd. So, I guess Schrödinger's cat is playing with my computer. Idmapd is both running and not running at the same time. I don't see where it's enabled. I've checked both Network Services and Services Manager. How do I get the NFS server to run? Do I have to uninstall nfsidmap? Or is this another systemd "feature"? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1 Oct 2014, james.knott@rogers.com wrote:
I'm trying to set up a NFS server on 13.1. I have tried both with and without NFSv4 support. If I try with, Yast complains it can't start idmapd and if I try without NFSv4, it complains it can't stop idmapd. So, I guess Schrödinger's cat is playing with my computer. Idmapd is both running and not running at the same time. I don't see where it's enabled. I've checked both Network Services and Services Manager.
Strange I have no problems with starting NFS server. FWIW, here is my config: ## Path: Network/File systems/NFS server ## Description: number of threads for kernel nfs server ## Type: integer ## Default: 4 ## ServiceRestart: nfsserver # # the kernel nfs-server supports multiple server threads # USE_KERNEL_NFSD_NUMBER="4" ## Path: Network/File systems/NFS server ## Description: use fixed port number for mountd ## Type: integer ## Default: "" ## ServiceRestart: nfsserver # # Only set this if you want to start mountd on a fixed # port instead of the port assigned by rpc. Only for use # to export nfs-filesystems through firewalls. # MOUNTD_PORT="" ## Path: Network/File systems/NFS server ## Description: GSS security for NFS ## Type: yesno ## Default: yes ## ServiceRestart: nfs nfsserver # # Enable RPCSEC_GSS security for NFS (yes/no) # NFS_SECURITY_GSS="no" ## Path: Network/File systems/NFS server ## Description: NFSv3 server support ## Type: yesno ## Default: yes ## ServiceRestart: nfsserver # # Enable NFSv3 server support (yes/no) # This causes the NFS server to respond to # NFSv2 and NFSv3 requests. Only disable this # if you want to ensure only NFSv4 is used. # NFS3_SERVER_SUPPORT="yes" ## Path: Network/File systems/NFS server ## Description: NFSv4 protocol support ## Type: yesno ## Default: yes ## ServiceRestart: nfs nfsserver # # Enable NFSv4 support (server and/or client) (yes/no) # NFS4_SUPPORT="no" ## Path: Network/File systems/NFS server ## Description: NFSv4 server minor version ## Type: integer ## Default: 0 ## ServiceRestart: nfsserver # # Select NFSv4 minor version for server to support (0, 1). # If '1' is selected, NFSv4.0 will also be supported. NFS4_SERVER_MINOR_VERSION="0" ## Path: Network/File systems/NFS server ## Description: Network Status Monitor options ## Type: string ## Default: "" # # If a fixed port should be used to send reboot notification # messages to other systems, that port should be given # here as "-p portnumber". # SM_NOTIFY_OPTIONS="" ## Path: Network/File systems/NFS server ## Description: Always start NFS services ## Type: yesno ## Default: yes ## ServiceRestart nfs # # Always start NFS services (gssd, idmapd), not only if # there are nfs mounts in /etc/fstab. This is likely to be # needed if you use an automounter for NFS. # Note that the nfs service is no longer enabled by default # and the command "chkconfig nfs on" is needed to fully enable # NFS. # NFS_START_SERVICES="yes" ## Path: Network/File systems/NFS server ## Description: Command line parameters for rpc.statd ## Type: string ## Default: "" # # Custom parameters for rpc.statd daemon. Typically this will # be used to set the port number (-p). # STATD_OPTIONS="" ## Path: Network/File systems/NFS server ## Description: Lease time for NFSv4 leases ## Type: integer ## Default: "" # # Set the lease time for the NFSv4 server. This allows new locks # to be taken sooner after a server restart, so it is useful for # servers which need to recover quickly after a failure, particularly # in fail-over configurations. Reducing the lease time can be a # problem is some clients connect over high latency networks. # The default is 90 seconds. A number like 15 might be appropriate # in a fail-over configuration with all clients on well connected # low latency links. NFSV4LEASETIME="" ## Path: Network/File systems/NFS server ## Description: Alternate mount point for rpc_pipefs filesystem ## Type: string ## Default: "" # # In a high-availabilty configuration it is possible that /var/lib/nfs # is redirected so some shared storage and so it is not convenient to # mount the rpc_pipefs filesystem at /var/lib/nfs/rpc_pipefs. In that # case an alternate mount point can be given here. RPC_PIPEFS_DIR="" ## Path: Network/File systems/NFS server ## Description: Options for svcgssd ## Type: string ## Default: "" # # Normally svcgssd does not require any option. However in a # high-availabilty configuration it can be useful to pass "-n" # to guide the choice of default credential. To allow for that # case or any other requiring options ot svcgssd, they can # be specified here. SVCGSSD_OPTIONS="" ## Path: Network/File systems/NFS server ## Description: Extra options for nfsd ## Type: string ## Default: "" # # This setting allows extra options to be specified for NFSD, such as # -H <shared_hostname> in a high-availability configuration. NFSD_OPTIONS="" ## Path: Network/File systems/NFS server ## Description: Extra options for gssd ## Type: string ## Default: "" # # Normally gssd does not require any options. In some circumstances, # -n, -l or other options might be useful. See "man 8 rpc.gssd" for # details. Those options can be set here. GSSD_OPTIONS="" ## Path: Network/File systems/NFS server ## Description: Extra options for mountd ## Type: string ## Default: "" # # This setting allows extra options to be specified for rpc.mountd, # such as --manage-gids. MOUNTD_OPTIONS="" ## Path: Network/File systems/NFS server ## Description: Avoid DNS lookups for kerberos principal ## Type: yesno ## Default: no ## ServiceRestart: gssd # # Avoid DNS lookups when determining kerberos identity # of NFS server (yes/no) # "yes" is safest, but "no" might be needed to preserve # correct behaviour at sites that don't use # Fully Qualified Domain Names when mounting NFS Shares. # NFS_GSSD_AVOID_DNS="no"
How do I get the NFS server to run? Do I have to uninstall nfsidmap? Or is this another systemd "feature"?
I have that package installed, but I don't have nfsidmap started, since I am not using V4. Charles -- "On a normal ascii line, the only safe condition to detect is a 'BREAK' - everything else having been assigned functions by Gnu EMACS." (By Tarl Neustaedter)
On 10/01/2014 01:59 PM, Charles Philip Chan wrote:
Strange I have no problems with starting NFS server. FWIW, here is my config: Where is that file? All I can find is /etc/init.d/nfs, which looks nothing like yours. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2014 02:15 PM, Charles Philip Chan wrote:
Where is that file? All I can find is /etc/init.d/nfs, which looks
nothing like yours. /etc/sysconfig/nfs
A quick comparison shows they are the same and ps aux shows a few lines for nfsd. Also Services Manager show NFS server to be enabled and active, yet I am unable to complete setting up a share and another computer can't see the server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1 Oct 2014, james.knott@rogers.com wrote:
A quick comparison shows they are the same and ps aux shows a few lines for nfsd. Also Services Manager show NFS server to be enabled and active, yet I am unable to complete setting up a share and another computer can't see the server.
Firewall? Charles -- "Besides, I think [Slackware] sounds better than 'Microsoft,' don't you?" (By Patrick Volkerding)
On 10/01/2014 02:57 PM, Charles Philip Chan wrote:
On 1 Oct 2014, james.knott@rogers.com wrote:
A quick comparison shows they are the same and ps aux shows a few lines for nfsd. Also Services Manager show NFS server to be enabled and active, yet I am unable to complete setting up a share and another computer can't see the server. Firewall?
There is no firewall between the 2 computers. I only run one on my firewall computer that connects to the Internet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2014 04:04 PM, James Knott wrote:
On 10/01/2014 02:57 PM, Charles Philip Chan wrote:
On 1 Oct 2014, james.knott@rogers.com wrote:
A quick comparison shows they are the same and ps aux shows a few lines for nfsd. Also Services Manager show NFS server to be enabled and active, yet I am unable to complete setting up a share and another computer can't see the server. Firewall?
There is no firewall between the 2 computers. I only run one on my firewall computer that connects to the Internet.
Hmmm... Now I can see the server with the NFS client. Previously I couldn't. Still though, that doesn't address the issue with the idmap errors. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-10-01 22:11, James Knott wrote:
Still though, that doesn't address the issue with the idmap errors.
Maybe because idmap is not configured. See man idmapd and idmapd.conf, perhaps. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2014 04:18 PM, Carlos E. R. wrote:
Still though, that doesn't address the issue with the idmap errors.
Maybe because idmap is not configured. See man idmapd and idmapd.conf, perhaps.
There is a minimal idmapd.conf [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = <FQDN removed> [Mapping] Nobody-User = nobody Nobody-Group = nobody However, should it even be necessary to have that file, if I'm not using NFSv4? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2014 02:17 PM, James Knott wrote:
On 10/01/2014 04:18 PM, Carlos E. R. wrote:
Still though, that doesn't address the issue with the idmap errors. Maybe because idmap is not configured. See man idmapd and idmapd.conf, perhaps. There is a minimal idmapd.conf
[General]
Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = <FQDN removed>
[Mapping]
Nobody-User = nobody Nobody-Group = nobody
However, should it even be necessary to have that file, if I'm not using NFSv4?
What is exports file look like? I generally have to reboot my machine after I configure it. My exports looks like: /export *(fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check) /export/home0 192.168.20.0/9(rw,root_squash,sync,no_subtree_check) 127.0.0.0/8(rw,root_squash,sync,no_subtree_check) -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Joseph Loo <jloo20111002@gmail.com> [10-01-14 22:17]: [...]
What is exports file look like? I generally have to reboot my machine after I configure it. My exports looks like:
/export *(fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check) /export/home0 192.168.20.0/9(rw,root_squash,sync,no_subtree_check) 127.0.0.0/8(rw,root_squash,sync,no_subtree_check)
cat /etc/exports /mnt/usb3.1 192.168.1.1/22(rw,no_root_squash,sync,no_subtree_check) /192.168.56.1(rw,no_root_squash,sync,no_subtree_check,insecure) man exportfs a reboot is *not* necessary. although I have had to restart the nfs daemon -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2014 07:21 PM, Patrick Shanahan wrote:
* Joseph Loo <jloo20111002@gmail.com> [10-01-14 22:17]: [...]
What is exports file look like? I generally have to reboot my machine after I configure it. My exports looks like:
/export *(fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check) /export/home0 192.168.20.0/9(rw,root_squash,sync,no_subtree_check) 127.0.0.0/8(rw,root_squash,sync,no_subtree_check) cat /etc/exports /mnt/usb3.1 192.168.1.1/22(rw,no_root_squash,sync,no_subtree_check) /192.168.56.1(rw,no_root_squash,sync,no_subtree_check,insecure)
man exportfs
a reboot is *not* necessary. although I have had to restart the nfs daemon
Make sure it is a single line and not 2 lines. Are you sure the mount occurs before the nfs process start? If it does not, it will error out. Opensuse is not suppose to require a reboot, but I always see it error out. Try /etc/init.d/nfs restart or /etc/init.d/nfsserver restart at the command line. Sometimes it generates error messages that will give you a clue. -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Joseph Loo <jloo20111002@gmail.com> [10-01-14 22:41]:
On 10/01/2014 07:21 PM, Patrick Shanahan wrote:
* Joseph Loo <jloo20111002@gmail.com> [10-01-14 22:17]: [...]
What is exports file look like? I generally have to reboot my machine after I configure it. My exports looks like:
/export *(fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check) /export/home0 192.168.20.0/9(rw,root_squash,sync,no_subtree_check) 127.0.0.0/8(rw,root_squash,sync,no_subtree_check) cat /etc/exports /mnt/usb3.1 192.168.1.1/22(rw,no_root_squash,sync,no_subtree_check) /192.168.56.1(rw,no_root_squash,sync,no_subtree_check,insecure)
man exportfs
a reboot is *not* necessary. although I have had to restart the nfs daemon
Make sure it is a single line and not 2 lines.
wrapped in email :^)
Are you sure the mount occurs before the nfs process start? If it does not, it will error out.
I'm not having a problem, you posed the question ????
Opensuse is not suppose to require a reboot, but I always see it error out.
I have had to umount before successful recovery and/or do a remount.
Try /etc/init.d/nfs restart or /etc/init.d/nfsserver restart at the command line. Sometimes it generates error messages that will give you a clue.
systemctl restart nfs.service or rcnfs restart And again, you posed the question. I was only answering, not presenting a problem. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/01/2014 08:11 PM, Patrick Shanahan wrote:
mnt/usb3.1 192.168.1.1/22(rw,no_root_squash,sync,no_subtree_check)
/192.168.56.1(rw,no_root_squash,sync,no_subtree_check,insecure)
I can't think of anything else. Did you try /usr/sbin/exportfs as root?
-- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Joseph Loo <jloo20111002@gmail.com> [10-02-14 00:33]:
On 10/01/2014 08:11 PM, Patrick Shanahan wrote:
mnt/usb3.1 192.168.1.1/22(rw,no_root_squash,sync,no_subtree_check)
/192.168.56.1(rw,no_root_squash,sync,no_subtree_check,insecure)
I can't think of anything else. Did you try /usr/sbin/exportfs as root?
I have no idea what *you* are reading into my posts. I am successfully utilizing nfs. I have no need to try .... unless I see a problem to solve. Please either explain yourself or drop the subject. I am *not* the OP. ps aux | grep nfs USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 2213 0.0 0.0 0 0 ? S< Sep15 0:00 \_[nfsiod] root 2293 0.0 0.0 0 0 ? S< Sep15 0:00 \_[nfsd4] root 2294 0.0 0.0 0 0 ? S< Sep15 0:00 \_[nfsd4_callbacks] root 2298 0.0 0.0 0 0 ? S Sep15 8:43 \_[nfsd] root 2299 0.0 0.0 0 0 ? S Sep15 9:59 \_[nfsd] root 2300 0.0 0.0 0 0 ? S Sep15 9:48 \_[nfsd] root 2301 0.0 0.0 0 0 ? S Sep15 8:19 \_[nfsd] root 5427 0.0 0.0 0 0 ? S Sep15 0:00 \_[nfsv4.0-svc] root 2270 0.0 0.0 15380 328 ? Ss Sep15 0:00 /usr/sbin/rpc.idmapd -p /var/lib/nfs/rpc_pipefs root 2271 0.0 0.0 15380 328 ? Ss Sep15 0:00 /usr/sbin/rpc.idmapd -p /var/lib/nfs/rpc_pipefs root 5420 0.0 0.0 31444 476 ? Ss Sep15 0:00 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
rpc.idmapd is started by the nfs service script, /etc/init.d/nfs or 'systemctl start nfs.service'. It's enabled by setting NFS_START_SERVICES="yes" in /etc/sysconfig/nfs. -- Later, Darin On Wed, Oct 1, 2014 at 1:19 PM, James Knott <james.knott@rogers.com> wrote:
I'm trying to set up a NFS server on 13.1. I have tried both with and without NFSv4 support. If I try with, Yast complains it can't start idmapd and if I try without NFSv4, it complains it can't stop idmapd. So, I guess Schrödinger's cat is playing with my computer. Idmapd is both running and not running at the same time. I don't see where it's enabled. I've checked both Network Services and Services Manager.
How do I get the NFS server to run? Do I have to uninstall nfsidmap? Or is this another systemd "feature"?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-10-01 19:19, James Knott wrote:
I'm trying to set up a NFS server on 13.1. I have tried both with and without NFSv4 support. If I try with, Yast complains it can't start idmapd
I understand you can ignore that. NFS should be running anyway. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R. -
Charles Philip Chan -
Darin Perusich -
James Knott -
Joseph Loo -
Patrick Shanahan