You are not logged in.

#1 2024-04-06 10:25:43

masenko
Member
Registered: 2022-12-09
Posts: 29

[SOLVED] NFS: mount program didn't pass remote address.

Hi, i recently reinstalled arch and on my previous install and any other linux distro i've used, this always worked perfectly fine. But now i'm running into this problem, i've tried searching it up a couple times but usually i find no solution, so i thought i'd ask here.

My fstab has this entry:

192.0.1.100:/test /mnt/nfs nfs rw,async,nfsvers=4,nosuid,_netdev,nofail 0 0

And then the journal outputs this (when filtering for the word nfs with grep):

systemd[1]: Mounting /mnt/nfs...
kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
mount[1677]: mount: /mnt/nfs: fsconfig system call failed: NFS: mount program didn't pass remote address.
systemd[1]: mnt-nfs.mount: Mount process exited, code=exited, status=32/n/a
systemd[1]: mnt-nfs.mount: Failed with result 'exit-code'.
systemd[1]: Failed to mount /mnt/nfs.

 
When i try to mount it myself with:

sudo mount 192.0.1.100:/test /mnt/nfs
sudo mount -o rw,async,nfsvers=4,nosuid,_netdev,nofail 192.0.1.100:/test /mnt/nfs

I get the same output every time:

mount: /mnt/nfs: fsconfig system call failed: NFS: mount program didn't pass remote address.
       dmesg(1) may have more information after failed mount system call.

 
Here is the nfs server /etc/exports:

/test 192.0.1.101/32(rw,async,no_subtree_check)

I am user 1000, and the permissions on the nfs server folder /test is:

drwx------ 1000 1000

 
Why can i not mount this nfs share?

Last edited by masenko (2024-04-12 20:09:40)

Offline

#2 2024-04-10 17:39:52

masenko
Member
Registered: 2022-12-09
Posts: 29

Re: [SOLVED] NFS: mount program didn't pass remote address.

Bump

Offline

#3 2024-04-10 18:38:20

loqs
Member
Registered: 2014-03-06
Posts: 17,425

Re: [SOLVED] NFS: mount program didn't pass remote address.

Offline

#4 2024-04-10 19:23:23

seth
Member
Registered: 2012-09-03
Posts: 51,608

Re: [SOLVED] NFS: mount program didn't pass remote address.

nmap 192.0.1.100
ip a # the /32 is kinda pointless, you're exporting to a single IP

and try to add "insecure" to the exports.

Offline

#5 2024-04-11 19:01:33

masenko
Member
Registered: 2022-12-09
Posts: 29

Re: [SOLVED] NFS: mount program didn't pass remote address.

Ah i'm sorry, i looked at the forum and it had a rule post so i thought those had all the rules. I didn't know there were more rules on the wiki.

Offline

#6 2024-04-11 19:41:23

masenko
Member
Registered: 2022-12-09
Posts: 29

Re: [SOLVED] NFS: mount program didn't pass remote address.

seth wrote:
nmap 192.0.1.100
ip a # the /32 is kinda pointless, you're exporting to a single IP

and try to add "insecure" to the exports.

Nmap scan report for 192.0.1.100
PORT     STATE  SERVICE
53/tcp   closed domain
111/tcp  open   rpcbind
2049/tcp open   nfs

I've got 2 other machines that work perfectly like this and right when i switched from gnome to xfce, this started happening. The one thing i changed on the nfs host are these /etc/sysctl.conf lines:

2,3c2,3
< #net.ipv4.ip_forward=1
< #net.ipv4.ip_nonlocal_bind=1
---
> net.ipv4.ip_forward=1
> net.ipv4.ip_nonlocal_bind=1
5,10c5,10
< #net.ipv6.conf.all.forwarding=1
< #net.ipv6.ip_nonlocal_bind=1
< #net.ipv6.conf.eth0.dad_transmits=0
< #net.ipv6.conf.all.autoconf=0
< #net.ipv6.conf.all.accept_ra=0
< net.ipv6.conf.all.disable_ipv6 = 1
---
> net.ipv6.conf.all.forwarding=1
> net.ipv6.ip_nonlocal_bind=1
> net.ipv6.conf.eth0.dad_transmits=0
> net.ipv6.conf.all.autoconf=0
> net.ipv6.conf.all.accept_ra=0
> #net.ipv6.conf.all.disable_ipv6 = 1

Offline

#7 2024-04-11 21:14:41

seth
Member
Registered: 2012-09-03
Posts: 51,608

Re: [SOLVED] NFS: mount program didn't pass remote address.

How can you have to other machines if you're limiting the access to a single IP?
You didn't post the output of "ip a"

Though it should be default you can try to explicitly use "resvport"

right when i switched from gnome to xfce, this started happening

If you have a theory how the desktop session of some regular user could impact the behavior of a systemwide fstab mount, I'm all ears.
The only related thing could be some gvfs attempt to mount the share directly (not using the mount filesystem) using an "insecure" port (>1024) and the server blocking the IP for this - but even then xfce4 and gnome would both use gvfs ¯\_(ツ)_/¯

Offline

#8 2024-04-12 18:27:10

masenko
Member
Registered: 2022-12-09
Posts: 29

Re: [SOLVED] NFS: mount program didn't pass remote address.

seth wrote:

How can you have to other machines if you're limiting the access to a single IP?

I have different shares setup for those machines

seth wrote:

You didn't post the output of "ip a"

On nfs host or nfs client?

seth wrote:

right when i switched from gnome to xfce, this started happening

If you have a theory how the desktop session of some regular user could impact the behavior of a systemwide fstab mount, I'm all ears.
The only related thing could be some gvfs attempt to mount the share directly (not using the mount filesystem) using an "insecure" port (>1024) and the server blocking the IP for this - but even then xfce4 and gnome would both use gvfs ¯\_(ツ)_/¯

That's why it's weird to me, it shouldn't affect anything. I'm just stating what i changed for the problem to occur.

Offline

#9 2024-04-12 20:01:53

masenko
Member
Registered: 2022-12-09
Posts: 29

Re: [SOLVED] NFS: mount program didn't pass remote address.

I fixed it by installing the nfs-utils package, that explains why the error appeared after a fresh install. Thank you both for your help.

Offline

Board footer

Powered by FluxBB