Solaris Troubleshooting NFS : NFS server error: /usr/lib/nfs/nfsd [###]: t_accept(file descriptor #/transport tcp) TLI error 7

On an NFS server, the following error shows up in /var/adm/messages:

/usr/lib/nfs/nfsd[391]: t_accept(file descriptor 5/transport tcp) TLI error 7




This error may or may not be accompanied by slow NFS performance and NFS server not responding errors. this error is most likely due to multi-threaded connect messages arriving at nfsd out of order.

 

Check for general network connectivity problems by looking at netstat -i and netstat -k on both the client and server.

In netstat -i output, look for high Ierrs or Oerrs.

The output of netstat -k is huge.  Use the example netstat -k command to clip the relevant information (substitute le0 or other network interface if appropriate).

In the netstat -k output, look for Late Collisions, Framing, or CRC errors which may account for the output errors.

Example:

server# netstat -i

Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis Queue
hme0  1500 server        server               283000  0   294000   1010   1733

client# netstat -i

Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis Queue
hme0  1500 client      client        129000  83  127000   5800   1600

server# netstat -k | sed -n /^hme0:/,/^nfs_client:/p

hme0:
ipackets 294399 ierrors 0 opackets 304770 oerrors 1019 collisions 1758
defer 0 framing 0 crc 0 sqe 0 code_violations 0 len_errors 0
ifspeed 100 buff 0 oflo 0 uflo 0 missed 0 tx_late_collisions 993
retry_error 0 first_collisions 0 nocarrier 0 inits 19 nocanput 0
allocbfail 0 runt 0 jabber 0 babble 26 tmd_error 0 tx_late_error 0
rx_late_error 0 slv_parity_error 0 tx_parity_error 0 rx_parity_error 0
slv_error_ack 0 tx_error_ack 0 rx_error_ack 0 tx_tag_error 0
rx_tag_error 0 eop_error 0 no_tmds 0 no_tbufs 0 no_rbufs 0
rx_late_collisions 0 rbytes 138882527 obytes 162938463 multircv 123 multixmt 0
brdcstrcv 4024 brdcstxmt 316 norcvbuf 0 noxmtbuf 0

client# netstat -k | sed -n /^hme0:/,/^nfs_client:/p

hme0:
ipackets 130263 ierrors 84 opackets 127750 oerrors 5775 collisions 16270
defer 0 framing 0 crc 84 sqe 0 code_violations 0 len_errors 0
ifspeed 10 buff 0 oflo 0 uflo 0 missed 0 tx_late_collisions 5706
retry_error 0 first_collisions 0 nocarrier 0 inits 6 nocanput 0
allocbfail 0 runt 0 jabber 0 babble 69 tmd_error 0 tx_late_error 0
rx_late_error 0 slv_parity_error 0 tx_parity_error 0 rx_parity_error 0
slv_error_ack 0 tx_error_ack 0 rx_error_ack 0 tx_tag_error 0
rx_tag_error 0 eop_error 0 no_tmds 0 no_tbufs 0 no_rbufs 0
rx_late_collisions 0 rbytes 80644973 obytes 71215829 multircv 0 multixmt 0
brdcstrcv 4150 brdcstxmt 132 norcvbuf 0 noxmtbuf 0


If you do see evidence of network problems from looking at this output, find the source of those problems first.  For Framing or CRC errors, check hardware, such as cables, hubs, switches, etc. If you see late collisions.  Once the underlying network problems have been resolved, this error should go away.


Ramdev

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

1 Response

  1. September 16, 2015

    […] Read – error: /usr/lib/nfs/nfsd [###]: t_accept(file descriptor #/transport tcp) TLI error 7 […]

What is in your mind, about this post ? Leave a Reply

Close
  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us