On 07/03/17 12:44, Amadeus W.M. wrote:
> Yes, I know it should work, but I need a fix for my problem. 

Oh, I'm sorry.  When you said "I mean, really, nfs not working on a major
distribution?" I thought you were thinking it isn't working at all for anyone.

> I wonder if in my case it's some stale configuration from previous Fedora 
> versions,
> because I've been doing upgrades (as opposed to new installs) for a long 
> time. I
> imagine you installed F25 anew on the VM, right? 

It is possible you may have an old configuration parameter or such that is 
causing
the hang.  But you've not posted any of the configuration information.  In the 
past
it has been practice to either ignore depreciated parameters or toss out an 
error
message that a parameter is invalid.  It hasn't been the practice to hang on 
invalid
parameters.

Yes, I had to configure a new NFS service since getting a NAS box I've not had 
the
need to configure NFS on Fedora.  If I hadn't tossed my very old, heavy, slow, 
server
that had NFS configured on previous versions I would have upgraded it and tried 
that
there.

Now, that being said.....  You indicated that you had NFS working prior to 
upgrading
to F25 but you'd not mentioned the previous version of fedora  You may consider
installing a previous version in a VM (since you mentioned VMs) getting it to 
work
with a similar configuration, taking a snapshot, and then upgrading it to see 
if you
can reproduce the problem.

If you aren't adverse to showing your configuration files you can do that as 
well.

> How do I even tell which version NFS I'm running? 

Not sure what you mean by "version".   But the process rpc.nfsd is the NFS 
server
process and comes with nfs-utils-2.1.1-5.rc4 on F25.

When this is started by the nfs-server.service the parameters for that service 
are
supplied by $RPCNFSDARGS which is sourced from /etc/sysconfig/nfs (as you've 
pointed
out) which is initially RPCNFSDARGS="" meaning the defaults are used.  I 
believe, by
default only V3 and V4 via TCP are supported.  In any event, not allowing UDP 
support
is the default and enabling it or disabling it shouldn't cause a hang.

Just for completeness....

Prior to starting nfs-server there are no nfs running and only rpciod (which I 
have
no idea as to its purpose)

After starting....

[egreshko@f25f ~]$ ps aux | grep nfs
root      2123  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2124  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2125  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2126  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2127  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2128  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2129  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]
root      2130  0.0  0.0      0     0 ?        S    13:35   0:00 [nfsd]

and

[egreshko@f25f ~]$ ps aux | grep rpc
root       560  0.0  0.0      0     0 ?        S<   13:29   0:00 [rpciod]
rpc       2102  0.0  0.3  57312  4116 ?        Ss   13:35   0:00 
/usr/bin/rpcbind -w -f
rpcuser   2103  0.0  0.2  42524  3424 ?        Ss   13:35   0:00 
/usr/sbin/rpc.statd
root      2104  0.0  0.0  19368   188 ?        Ss   13:35   0:00 
/usr/sbin/rpc.idmapd
root      2115  0.0  0.0  42704   628 ?        Ss   13:35   0:00 
/usr/sbin/rpc.mountd

Also, running nmap from another system shows the following open on the system 
running
nfs-server


PORT     STATE  SERVICE       VERSION
21/tcp   open   ftp           vsftpd 3.0.3
| ftp-anon: Anonymous FTP login allowed (FTP code 230)
|_drwxr-xr-x    1 0        0               0 Dec 01  2016 pub
22/tcp   open   ssh           OpenSSH 7.4 (protocol 2.0)
| ssh-hostkey:
|   2048 83:6c:cf:2c:d3:13:61:c7:56:0c:18:36:95:ff:4b:be (RSA)
|_  256 53:76:a8:e1:3f:d1:65:8b:ea:6d:e4:d5:6f:58:7c:5a (ECDSA)
139/tcp  closed netbios-ssn
445/tcp  closed microsoft-ds
2049/tcp open   nfs           3-4 (RPC #100003)
3389/tcp open   ms-wbt-server Microsoft Terminal Service
5900/tcp closed vnc
5901/tcp open   vnc           VNC (protocol 3.8)
| vnc-info:
|   Protocol version: 3.8
|   Security types:
|     VeNCrypt (19)
|     VNC Authentication (2)
|   VeNCrypt auth subtypes:
|     VNC auth, Anonymous TLS (258)
|_    Unknown security type (2)
5902/tcp closed vnc-2
5903/tcp closed vnc-3

If I am not mistaken, "2049/tcp open   nfs           3-4" is indicating 
versions 3
and 4 are available as I've noted.

Anyway, without knowing more about your configuration I can't explain why it 
would
hang.  But, hopefully you can check when the hang happens and see what processes
aren't being started.


-- 
Fedora Users List - The place to go to speculate endlessly

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Reply via email to