On 07/20/18 05:58, Bob Goodwin wrote:
On 07/19/18 17:42, Ed Greshko wrote:
> The server is a Fedora system, yes? And, has it been rebooted?
.
Fedora 27 and 28, rebooted several times today ...
I probably should have mentioned doing:
[root@Box10 86data]# ss -t -l -n
State Recv-Q Send-Q Local
Address:Port Peer Address:Port
LISTEN 0 128
0.0.0.0:60705 0.0.0.0:*
LISTEN 0 128
0.0.0.0:111 0.0.0.0:*
LISTEN 0 32
192.168.124.1:53 0.0.0.0:*
LISTEN 0 128
0.0.0.0:22 0.0.0.0:*
LISTEN 0 5
0.0.0.0:631 0.0.0.0:*
LISTEN 0 128
[::]:59745 [::]:*
LISTEN 0 128
[::]:111 [::]:*
LISTEN 0 128
[::]:22 [::]:*
LISTEN 0 5
[::]:631 [::]:*
> I don't currently have a Fedora system running as a NFSv4 server...but what do
you
> get when you do this from a client?
>
> telnet yourserver 2049
.
[root@Box10 86data]# telnet 192.168.1.86 2049
Trying 192.168.1.86...
telnet: connect to address 192.168.1.86: Connection refused
That means the nfs server isn't running....
I have a Fedora server now up on my end running F28....
Do you have something like this?
[root@f28k-b1 ~]# systemctl status nfs
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor pre>
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: active (exited) since Fri 2018-07-20 06:10:15 CST; 13min ago
Process: 4800 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then syst>
Process: 4787 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/S>
Process: 4786 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Main PID: 4800 (code=exited, status=0/SUCCESS)
Jul 20 06:10:15
f28k-b1.greshko.com systemd[1]: Starting NFS server and services...
Jul 20 06:10:15
f28k-b1.greshko.com systemd[1]: Started NFS server and services.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.