On Wed, 2021-02-17 at 11:43 -0700, Jerry James wrote: > On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille <jerome.lille@xxxxxxxxxx> > wrote: > > After the latest update there are some errors in the log that I > > haven't > > seen before. > > > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > > > There are two of those per minute continuously. I haven't noticed any > > other problems with the system, but wondering about those messages > > are > > about. > > Error 107 is ENOTCONN (transport endpoint is not connected). See > /usr/include/asm-generic/errno.h for error numbers. > > The xs_tcp_setup_socket function is part of the RPC code in the > kernel. Something on your system is trying to make an RPC call once > every 30 seconds, but is failing to connect to the server. If you > enable debug-level logging, you should see a log message showing what > address it is trying to connect to. See if this does the trick: > > $ echo 0xffff > /proc/sys/sunrpc/rpc_debug > [Wait for the log messages to appear] > $ echo 0 > /proc/sys/sunrpc/rpc_debug 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. /Jerome _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
