The NFS server appears to be down

Asked by ealthuis on 2020-03-24

ea@seanix:~$ ssh 192.168.0.104
ssh: connect to host 192.168.0.104 port 22: Connection timed out
ea@seanix:~$ nmap -p2049 192.168.0.104
Starting Nmap 7.80 ( https://nmap.org ) at 2020-03-24 09:09 PDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.07 seconds

Then when I enter this command:
ea@seanix:~$ sudo autonfs.sh
Automatic NFS mount script started.
Fileserver is down.

This is different from an earlier problem with NFS, I did a fresh install of Pop!Os 19.10 and could not get NFS to work with the above problem, then I installed a just downloaded Ubuntu 18.04LTS and installed NFS again and I have the same result.
Firewalls on both systems are set to allow NFS in and out.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
ealthuis
Solved:
2020-03-24
Last query:
2020-03-24
Last reply:
2020-03-24
Manfred Hampl (m-hampl) said : #1

Is the server really running?
Is it connected to the network?
Is the address 192.168.0.104 correct?
Which operating system is that server?

ealthuis (ealthuis) said : #2

Just downloaded from Ubuntu website Ubuntu 18.04LTS flashed it to a USB drive and installed it complete with updates.
ea@discovery:~$ uname -a
Linux discovery 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
ea@discovery:~$
 The address is correct, and it is connected to the router: "discovery 192.168.0.104 94:de:80:b7:7a:77 598767"
According to the "system Monitor" it is not running.
This is what I get when I do a start:
ea@discovery:~$ systemctl start nfs-kernel-server
Job for nfs-server.service canceled.
ea@discovery:~$
I have had a suspicion that it is not running,
 So how do I list the running jobs?

ealthuis (ealthuis) said : #3

neither the command ps -A or top show NFS, though there are a number of systemd jobs

Manfred Hampl (m-hampl) said : #4

What is the output of the command

systemctl status nfs-kernel-server

ealthuis (ealthuis) said : #5

● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor prese
   Active: failed (Result: exit-code) since Tue 2020-03-24 11:19:59 PDT; 1h 54mi
  Process: 4662 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCES
  Process: 4661 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCE
  Process: 4660 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILUR

Mar 24 11:19:59 discovery systemd[1]: Starting NFS server and services...
Mar 24 11:19:59 discovery exportfs[4660]: exportfs: Failed to stat /export/users
Mar 24 11:19:59 discovery exportfs[4660]: exportfs: Failed to stat export: No su
Mar 24 11:19:59 discovery systemd[1]: nfs-server.service: Control process exited
Mar 24 11:19:59 discovery systemd[1]: nfs-server.service: Failed with result 'ex
Mar 24 11:19:59 discovery systemd[1]: Stopped NFS server and services.
lines 1-13/13 (END)...skipping...
● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-03-24 11:19:59 PDT; 1h 54min ago
  Process: 4662 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 4661 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
  Process: 4660 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)

Mar 24 11:19:59 discovery systemd[1]: Starting NFS server and services...
Mar 24 11:19:59 discovery exportfs[4660]: exportfs: Failed to stat /export/users: No such file or directory
Mar 24 11:19:59 discovery exportfs[4660]: exportfs: Failed to stat export: No such file or directory
Mar 24 11:19:59 discovery systemd[1]: nfs-server.service: Control process exited, code=exited status=1
Mar 24 11:19:59 discovery systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Mar 24 11:19:59 discovery systemd[1]: Stopped NFS server and services.

ealthuis (ealthuis) said : #6

In previous uses, there was no requirement for /export/users. I will create that file thyough I have no need to export "users" or a /home directory.

ealthuis (ealthuis) said : #7

this is now:
ea@discovery:~$ systemctl status nfs-kernel-server
● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor prese
   Active: active (exited) since Tue 2020-03-24 13:30:51 PDT; 3min 32s ago
  Process: 4662 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCES
  Process: 4661 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCE
  Process: 5628 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0
  Process: 5627 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCES
 Main PID: 5628 (code=exited, status=0/SUCCESS)

Mar 24 13:30:49 discovery systemd[1]: Starting NFS server and services...
Mar 24 13:30:51 discovery systemd[1]: Started NFS server and services.
lines 1-11/11 (END)

However Mounting the export on the client still ends in a time out. That could be firewall.
I'll check
 And once again THANKS

ealthuis (ealthuis) said : #8

Once again you have solved my problem, thank you very much.