mount.nfs: Connection refused since last Arch update [solved]

audiomuze · 2020-12-24 10:13:26

I run Arch as a desktop OS and also a 2nd PC which acts as file server. I've used NFS exclusively to access files on the server via my desktop PC.

Last night I ran the usual

pacman -Syyu --noconfirm

on both machines before retiring. Both completed without issue and both were subsequently rebooted.

On attempting to mount two NFS shares from terminal using

for i in {e..f}; do sudo mount -o noacl,nocto,noatime,rsize=32768,wsize=32768 192.168.1.88:/srv/nfs/ext4"$i" /alib/alsd"$i"; done

I'm now getting

Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.

followed by a long wait then

mount.nfs: Connection refused
mount.nfs: Connection refused

dmesg on the client side shows:

[  189.606468] RPC: Registered named UNIX socket transport module.
[  189.606470] RPC: Registered udp transport module.
[  189.606471] RPC: Registered tcp transport module.
[  189.606471] RPC: Registered tcp NFSv4.1 backchannel transport module.
[  189.642701] FS-Cache: Netfs 'nfs' registered for caching
[  189.826051] NFS: Registering the id_resolver key type
[  189.826060] Key type id_resolver registered
[  189.826061] Key type id_legacy registered
[  189.846981] NFS4: Couldn't follow remote path
[  189.886097] audit: type=1130 audit(1608805444.807:115): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd-notify comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  189.914329] audit: type=1130 audit(1608805444.837:116): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpcbind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  189.954596] audit: type=1130 audit(1608805444.877:117): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  189.973726] audit: type=1334 audit(1608805444.897:118): prog-id=8 op=UNLOAD
[  189.973731] audit: type=1334 audit(1608805444.897:119): prog-id=7 op=UNLOAD
[  189.978130] audit: type=1334 audit(1608805444.901:120): prog-id=6 op=UNLOAD
[  191.174759] NFS4: Couldn't follow remote path
[  193.200557] NFS4: Couldn't follow remote path
[  197.227537] NFS4: Couldn't follow remote path
[  205.255323] NFS4: Couldn't follow remote path
[  213.243649] kauditd_printk_skb: 9 callbacks suppressed
[  213.243655] audit: type=1334 audit(1608805468.160:130): prog-id=18 op=LOAD
[  213.243681] audit: type=1334 audit(1608805468.160:131): prog-id=19 op=LOAD
[  213.410704] audit: type=1130 audit(1608805468.330:132): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  215.282543] NFS4: Couldn't follow remote path
[  225.310092] NFS4: Couldn't follow remote path
[  235.334947] NFS4: Couldn't follow remote path
[  245.360919] NFS4: Couldn't follow remote path
[  255.387939] NFS4: Couldn't follow remote path
[  265.415115] NFS4: Couldn't follow remote path
[  275.442943] NFS4: Couldn't follow remote path
[  285.465831] NFS4: Couldn't follow remote path
[  295.488142] NFS4: Couldn't follow remote path
[  305.512750] NFS4: Couldn't follow remote path
[  315.530057] NFS4: Couldn't follow remote path
[  315.550480] audit: type=1106 audit(1608805570.487:133): pid=1250 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[  315.550605] audit: type=1104 audit(1608805570.487:134): pid=1250 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[  315.561837] audit: type=1101 audit(1608805570.497:135): pid=1790 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="x" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[  315.562112] audit: type=1110 audit(1608805570.497:136): pid=1790 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[  315.566266] audit: type=1105 audit(1608805570.500:137): pid=1790 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
[  315.572074] NFS4: Couldn't follow remote path
[  316.592344] NFS4: Couldn't follow remote path
[  318.616869] NFS4: Couldn't follow remote path
[  322.640538] NFS4: Couldn't follow remote path
[  330.663714] NFS4: Couldn't follow remote path
[  340.689184] NFS4: Couldn't follow remote path
[  350.713071] NFS4: Couldn't follow remote path
[  360.736302] NFS4: Couldn't follow remote path
[  370.761847] NFS4: Couldn't follow remote path
[  380.788660] NFS4: Couldn't follow remote path
[  390.814785] NFS4: Couldn't follow remote path
[  400.841064] NFS4: Couldn't follow remote path
[  410.866895] NFS4: Couldn't follow remote path
[  420.891439] NFS4: Couldn't follow remote path
[  430.915726] NFS4: Couldn't follow remote path
[  440.941251] NFS4: Couldn't follow remote path

Config on server side is as follows:

/etc/fstab

UUID=d57236af-dfeb-4ed4-a056-44a97fdd15d0      /alib/ext4e     ext4    defaults,noatime        0       0
UUID=04b2f712-8b00-46ab-8bd5-71adcb68ff0a      /alib/ext4f     ext4    defaults,noatime        0       0

/alib/ext4e     /srv/nfs/ext4e          none bind 0 0
/alib/ext4f     /srv/nfs/ext4f          none bind 0 0

/etc/exports

/srv/nfs/ext4e 192.168.1.0/24(rw,no_subtree_check,all_squash,anonuid=1000,anongid=100)
/srv/nfs/ext4f 192.168.1.0/24(rw,no_subtree_check,all_squash,anonuid=1000,anongid=100)

Apart from the pacman update nothing has changed on either PC. Anyone else that's running an up to date Arch now experiencing NFS mount issues?

Last edited by audiomuze (2020-12-24 21:01:45)

seth · 2020-12-24 13:53:41

pacman -Syyu --noconfirm

Usually wrong, please check the pacman manpage and stop using "-yy" unless you want to.

Step #1, rule out network errors and check the server presence:

ping <server_ip>
nmap <server_ip>

audiomuze · 2020-12-24 14:12:12

seth wrote:

pacman -Syyu --noconfirm
ping <server_ip>
nmap <server_ip>

Pretty sure there was a reason I used -Syyu, but I'll revisit, thx.

The server is up and accessible, I can access it via ssh and mount shares using SAMBA.

PING 192.168.1.88 (192.168.1.88) 56(84) bytes of data.
64 bytes from 192.168.1.88: icmp_seq=1 ttl=64 time=0.254 ms
64 bytes from 192.168.1.88: icmp_seq=2 ttl=64 time=0.246 ms
64 bytes from 192.168.1.88: icmp_seq=3 ttl=64 time=0.247 ms

nmap 192.168.1.88
Starting Nmap 7.91 ( [url]https://nmap.org[/url] ) at 2020-12-24 14:13 GMT
Nmap scan report for 192.168.1.88
Host is up (0.00015s latency).
Not shown: 992 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
9100/tcp open  jetdirect
9101/tcp open  jetdirect
9102/tcp open  jetdirect
9103/tcp open  jetdirect

Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds

Last edited by audiomuze (2020-12-24 14:17:13)

seth · 2020-12-24 14:17:44

Does't mean the rpc and nfs ports are open, does it?
=> nmap?

Edit, no 2049 - nfs server isn't open. Check the server.

Last edited by seth (2020-12-24 14:19:58)

audiomuze · 2020-12-24 17:27:49

Doh! My apologies, it should've been the first thing I checked.

● nfs-server.service - NFS server and services
     Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
    Drop-In: /run/systemd/generator/nfs-server.service.d
             └─order-with-mounts.conf
     Active: failed (Result: exit-code) since Thu 2020-12-24 16:25:25 GMT; 59min ago
    Process: 615 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
    Process: 616 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
    Process: 617 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)

Dec 24 16:25:25 alib exportfs[615]: point 2
Dec 24 16:25:25 alib exportfs[615]: point 3
Dec 24 16:25:25 alib systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE
Dec 24 16:25:25 alib exportfs[616]: point 1
Dec 24 16:25:25 alib exportfs[616]: point 2
Dec 24 16:25:25 alib exportfs[616]: point 3
Dec 24 16:25:25 alib exportfs[617]: point 1
Dec 24 16:25:25 alib exportfs[617]: point 2
Dec 24 16:25:25 alib systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Dec 24 16:25:25 alib systemd[1]: Stopped NFS server and services.

I seem to recall there ws a recent update to NFS so something broke. Will investigate and roll back.

audiomuze · 2020-12-24 20:48:18

Right, I've found the cause. What I'd forgotten to include in my original post is I'd added an additional export to /etc/exports.

Commenting out the offending line resolved it.

#/srv/nfs/roonpool 192.168.1.0/24(rw,no_subtree_check,all_squash,anonuid=1000,anongid=100)

It's a mergerfs mount, so that's likely the issue <<< and so it is, so solved.

Last edited by audiomuze (2020-12-24 21:00:48)

Arch Linux

#1 2020-12-24 10:13:26

mount.nfs: Connection refused since last Arch update [solved]

#2 2020-12-24 13:53:41

Re: mount.nfs: Connection refused since last Arch update [solved]

#3 2020-12-24 14:12:12

Re: mount.nfs: Connection refused since last Arch update [solved]

#4 2020-12-24 14:17:44

Re: mount.nfs: Connection refused since last Arch update [solved]

#5 2020-12-24 17:27:49

Re: mount.nfs: Connection refused since last Arch update [solved]

#6 2020-12-24 20:48:18

Re: mount.nfs: Connection refused since last Arch update [solved]

Board footer