On Wed, Feb 17, 2021 at 12:08 PM Jerome Lille <jerome.lille(a)ownbay.net> wrote:
Thanks for the suggestion. I did get more logging
RPC: 000000005d78dc3a connect status 107 connected 0 sock state 7
xs_tcp_setup_socket: connect returned unhandled error -107
RPC: xs_tcp_state_change client 000000005d78dc3a...
RPC: state 7 conn 0 dead 0 zapped 1 sk_shutdown 3
RPC: set up xprt to 192.168.1.101 (port 111) via tcp
RPC: xs_connect scheduled xprt 0000000064ac8be5
RPC: worker connecting xprt 0000000064ac8be5 via tcp to
192.168.1.101 (port 111)
RPC: 0000000064ac8be5 connect status 115 connected 0 sock state 2
RPC: xs_tcp_state_change client 0000000064ac8be5...
RPC: state 1 conn 0 dead 0 zapped 1 sk_shutdown 0
RPC: xs_tcp_send_request(80) = 0
RPC: xs_data_ready...
RPC: setting port for xprt 000000005d78dc3a to 44982
RPC: xs_connect scheduled xprt 000000005d78dc3a
RPC: destroy backchannel transport
RPC: backchannel list empty= true
RPC: xs_bind 0.0.0.0:902: ok (0)
RPC: xs_destroy xprt 0000000064ac8be5
RPC: xs_close xprt 0000000064ac8be5
192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora
desktop that produces these error messages has some shares from it
mounted. No errors on the NFS server and the nfs shares seems to work
fine.
Hmm. Somebody else will have to step in here. My knowledge of NFS is
about 15 years out of date. :-)
--
Jerry James
http://www.jamezone.org/