Bug ID 990356
Summary Cannot start NFSv4 only server without RPC
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Network
Assignee bnc-team-screening@forge.provo.novell.com
Reporter trcs@gmx.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Hi.

I want to setup a NFSv4 only server without RPC. I have followed the steps from
the SUSE Linux Enterprise Server 12 SP1 Release Notes�:

   1) set NFS3_SERVER_SUPPORT=no in /etc/sysconfig/nfs
   2) systemctl disable rpcbind.socket

However, rpcbind, rpc.mountd, rpc.statd, rpcbind and rpc.idmapd are started, so
both 1) and 2) has no effect. rpciod is also running but I don't know if it is
related to NFS or not. I have done some tests enabling and disabling
rpcbind.socket and rpcbind.service with the following results:

   socket     service    result
   ------------------------------------------
   disabled   disabled   no difference
   masked     disabled   system doesn't boot�
   disabled   masked     system doesn't boot�
   masked     masked     system doesn't boot�

I have also removed the references to rpcbind.socket in nfs-server.service but
nothing changed. And if I remove all the rpc-xxx.yyy references in that file
the system won't boot.

When the system can't boot there are the following start up messages:

   [  OK  ] Started NFS Mount Daemon
   [Failed] Failed to start NFS status monitor for NFSv2/3 locking..
   See 'systemctl status rpc-statd.service' for details�
   Starting NFS server and services...
   ...
   [ **** ] A start job is running for NFS server and services (xxx / no limit)

[1] 3.1.4.5 NFSv4 only configuration
[2] A start job is running for NFS server and services (xxx / no limit)
[3] I cannot run the command because all the VTs are blocked (no login prompt)
by the message described in [2]


You are receiving this mail because: