NFS Server Issue

English Network/Internet
1

This is a new Tumblweed install. After enabling the nfs-server I am unable to connect from two different linux computers.

Running from either machine results in:

showmount -e tower

clnt_create: RPC: Port mapper failure - Timed out

Running showmount from the server:

Export list for tower:
/mnt/raid    *
/home/mmontz *

This is the exports file on the nfs-server machine:

/home/mmontz    *(rw,root_squash,sync,no_subtree_check)
/mnt/raid       *(rw,root_squash,sync,no_subtree_check)

Firewall is disabled.

This has worked for sometime on this machine before I had to rebuild it.

Any ideas?

Thanks,
Michael

2

What is reported by a client with rpcinfo?

rpcinfo -p <nfs_server>
3 
 RPC: Port mapper failure - Timed out
4

On the server, check that the NFS server is ok…

systemctl status nfsserver
5 
systemctl status nfs-server
● nfs-server.service - NFS server and services
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/nfs-server.service.d
           └─nfsserver.conf, options.conf
        /run/systemd/generator/nfs-server.service.d
           └─order-with-mounts.conf
   Active: active (exited) since Thu 2018-01-25 10:34:51 CST; 1min 23s ago
  Process: 30212 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 30211 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
  Process: 30209 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)
  Process: 30218 ExecStart=/usr/sbin/rpc.nfsd $NFSD_OPTIONS (code=exited, status=0/SUCCESS)
  Process: 30217 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
 Main PID: 30218 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/nfs-server.service

Jan 25 10:34:51 tower systemd[1]: Starting NFS server and services...
Jan 25 10:34:51 tower systemd[1]: Started NFS server and services.
mmontz@tower:~> 



journalctl -n 20
-- Logs begin at Wed 2018-01-24 17:55:39 CST, end at Thu 2018-01-25 10:38:21 CST. --
Jan 25 10:38:04 tower rpc.mountd[30216]: Caught signal 15, un-registering and exiting.
Jan 25 10:38:04 tower systemd[1]: Stopped NFSv4 ID-name mapping service.
Jan 25 10:38:04 tower systemd[1]: Stopped NFS Mount Daemon.
Jan 25 10:38:04 tower systemd[1]: Starting NFS Mount Daemon...
Jan 25 10:38:04 tower systemd[1]: Starting NFSv4 ID-name mapping service...
Jan 25 10:38:04 tower rpc.mountd[30276]: Version 2.1.1 starting
Jan 25 10:38:04 tower systemd[1]: Started NFS Mount Daemon.
Jan 25 10:38:04 tower systemd[1]: Started NFSv4 ID-name mapping service.
Jan 25 10:38:04 tower systemd[1]: Starting NFS server and services...
Jan 25 10:38:04 tower kernel: nfsd: last server has exited, flushing export cache
Jan 25 10:38:04 tower systemd[1]: Started NFS server and services.
Jan 25 10:38:04 tower sudo[30266]: pam_unix(sudo:session): session closed for user root
Jan 25 10:38:04 tower systemd[1]: Starting Notify NFS peers of a restart...
Jan 25 10:38:04 tower kernel: NFSD: starting 90-second grace period (net ffffffffa5109c80)
Jan 25 10:38:04 tower sm-notify[30286]: Version 2.1.1 starting
Jan 25 10:38:04 tower sm-notify[30286]: Already notifying clients; Exiting!
Jan 25 10:38:04 tower systemd[1]: Started Notify NFS peers of a restart.
Jan 25 10:38:21 tower sudo[30290]:   mmontz : TTY=pts/1 ; PWD=/home/mmontz ; USER=root ; COMMAND=/usr/bin/journalctl -n 20
Jan 25 10:38:21 tower sudo[30290]: pam_systemd(sudo:session): Cannot create session: Already running in a session
Jan 25 10:38:21 tower sudo[30290]: pam_unix(sudo:session): session opened for user root by mmontz(uid=0)
6

You mentioned that the firewall is disabled. Since you’re running TW, can you check the following?

systemctl status firewalld

systemctl status SuSEfirewall2
7

SuSEfirewall2 is what it was. I was not aware that it was installed. Yast said firewall was disabled.

Thanks for your assistance

8

Glad to have been of help.

PS: Be aware that there has been a recent move to firewalld, so perhaps that confused things (with respect to YaST) here.