I got this error in the log: <0.5> 2019-08-12 10:26:17 Telcontar kernel - - - [138139.721655] rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket <0.5> 2019-08-12 10:26:17 Telcontar kernel - - - [138139.722238] rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket An awful number of them! cer@Telcontar:~> grep "nfsd: got error -95" /var/log/messages | wc -l 119341 cer@Telcontar:~> Google does not say what error -95 is about. It started this morning at 10:25, till I stopped "Stopped NFS server and services" at 10:26:17. Ie, I got spammed by 119341 lines in one minute! It happened when another machine tried to mount an NFS directory. If I try again, restarting the service, and try from client, the thing starts again. I tried restarting client nfs, does not clear the issue. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 12/08/2019 10.40, Carlos E. R. wrote:
I got this error in the log:
<0.5> 2019-08-12 10:26:17 Telcontar kernel - - - [138139.721655] rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket <0.5> 2019-08-12 10:26:17 Telcontar kernel - - - [138139.722238] rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket
An awful number of them!
cer@Telcontar:~> grep "nfsd: got error -95" /var/log/messages | wc -l 119341 cer@Telcontar:~>
Google does not say what error -95 is about.
It started this morning at 10:25, till I stopped "Stopped NFS server and services" at 10:26:17. Ie, I got spammed by 119341 lines in one minute!
It happened when another machine tried to mount an NFS directory. If I try again, restarting the service, and try from client, the thing starts again.
I tried restarting client nfs, does not clear the issue.
It is related to nfs using IPv6. See iptraf output: iptraf-ng 1.1.4 ┌ TCP Connections (Source Host:Port) ────────────────────────────────────────────────────── Packets ─────────────── Bytes ──── Flag ──── Iface ────────────┐ │┌Isengard.valinor:22 > 18 4140 -PA- eth0 │ │└Telcontar.valinor:51536 > 22 1288 --A- eth0 │ │┌par21s03-in-f13.1e100.net:443 = 11 4781 -PA- eth0 │ │└Telcontar.valinor:52612 = 15 2139 --A- eth0 │ │┌par21s05-in-f138.1e100.net:443 > 1 52 --A- eth0 │ │└Telcontar.valinor:37488 = 0 0 ---- eth0 │ │┌fc00::14:2049 = 0 0 ---- eth0 │ │└fc00::16:713 > 1 116 -PA- eth0 │ │┌Telcontar.valinor:49962 = 14 2130 --A- eth0 │ │└par10s29-in-f3.1e100.net:80 = 13 2788 --A- eth0 │ │┌fc00::14:2049 > 1 72 --A- eth0 │ │└fc00::16:788 = 0 0 ---- eth0 │ │┌fc00::16:829 = 0 0 ---- eth0 │ │└fc00::14:2049 > 1 72 --A- eth0 │ │┌fc00::14:2049 = 0 0 ---- eth0 │ │└fc00::16:822 > 1 116 -PA- eth0 │ │┌fc00::16:901 = 1 80 S--- eth0 │ │└fc00::14:2049 = 0 0 ---- eth0 │ │┌fc00::14:2049 > 1 72 --A- eth0 │ │└fc00::16:665 = 0 0 ---- eth0 │ │┌fc00::16:733 = 4 340 CLOS eth0 │ I have removed the IPv6 entries from name service on both machines, restarted nfs service, and now it works again. Farewell IPv6 :-/ -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (1)
-
Carlos E. R.