[Offsprin]

There's a few github reports about this, but they seem pretty stale, but the gist of it is that there seems to be an issue with Leia that blocks NFS shares from working properly, with Kodi failing to load the directory listing. Other services work fine. For me specifically the error I'm seeing is as follows:

Code:

2020-12-08 22:25:25.131 T:139923037506240   ERROR: GetDirectory - Error getting nfs://
2020-12-08 22:25:25.131 T:139923037506240   ERROR: CGUIDialogFileBrowser::GetDirectory(nfs://) failed
2020-12-08 22:25:29.894 T:139923037506240   ERROR: GetDirectory - Error getting nfs://
2020-12-08 22:25:29.894 T:139923037506240   ERROR: CGUIDialogFileBrowser::GetDirectory(nfs://) failed

This used to work with older versions of Kodi, so I'm not sure when this broke but I'm able to repro it across numerous devices.

[DaveBlake]

@Offsprin with the limited information that you give it is impossible for any dev to do anything with this even if someone had the time, skill and interest. File access via NFS works perfectly for me and a great many other users on all versions of Kodi since v15.

[Offsprin]

Point taken. I've attached a crash log, with debug level enabled, where I attempted to browse to a new video library share under the NFS section and the problem being seen appeared: crash.log.

And here's the full Kodi log: kodi.log.

The problem is that whenever I try to browse to or open an NFS share, I'm getting the empty pathing so I'm unable to use it for loading any libraries. https://github.com/xbmc/xbmc/issues/16768 is the original github issue I found related to this. Behavior is being seen on Ubuntu 20.04 and Android devices.

The issue, where it errors out stating NFS:// is seen either when manually setting a path in sources.xml or by attempting to browse. Version of NFS on client is 1:1.3.4-2.5ubuntu3.3, version of NFS on server is 1:1.3.4-2.5ubuntu3.3.

[Offsprin]

You're right, my bad. Here's the original github issue I was referring to: https://github.com/xbmc/xbmc/issues/16768. The problem being exhibited is that for some reason when trying to load NFS sources either from manually edited sources.xml, or crafted through the UI the system will return an error regarding NFS:// and simply not respond. I enabled debug logging, and then wound up getting a crash when I browsed for a new library via the UI to the NFS Browser. Here's the crash log and here is the kodi log. On both the server and client for Ubuntu 20.04, I'm running 1:1.3.4-2.5ubuntu3.3. I'm seeing this both on Ubuntu 20.04 and at least two different Android devices: an Android SHIELD and a Samsung Galaxy Tab A 10.

[DaveBlake]

Good to have more information @Offsprin. From the errors in the log I would say that you have a different problem from the op of the issue on Github. No idea about the other "me too" there, without logs they could be having completely different issues.

Unfortuneately I know very little about NFS other than it is essential to get the server setup correctly. Any issues I have experienced have always been on that side of things, so just in case it helps have a look at https://kodi.wiki/view/NFS

With it mounted at OS level, can you use something else to verify the device(s) has access to the server OK without Kodi client?

[Offsprin]

Good to have more information @Offsprin. From the errors in the log I would say that you have a different problem from the op of the issue on Github. No idea about the other "me too" there, without logs they could be having completely different issues.

Unfortuneately I know very little about NFS other than it is essential to get the server setup correctly. Any issues I have experienced have always been on that side of things, so just in case it helps have a look at https://kodi.wiki/view/NFS

With it mounted at OS level, can you use something else to verify the device(s) has access to the server OK without Kodi client?

Yeah, if I mount it at the OS level I can browse the share normally.

[DaveBlake]

So the issue is being unable to mount a new share via Kodi?
To step through and ensure I am understanding: You are trying to add a new music or video source and on the "Browse for new share" dialog you click on the "Network File System (NFS)" item.

At that point Koid makes a libnfs call to nfs_find_local_servers which probes all local networks for NFS servers.
Having log "ERROR: GetDirectory - Error getting nfs://" implies that libnfs call is unsucessfull.

Digging more I found some previous discussion here https://forum.kodi.tv/showthread.php?tid...pid2778801 and an issue was raised against libnfs https://github.com/sahlberg/libnfs/issues/270 which concludes:
"rpcbind doesn't respond to broadcast requests when using the default build configuration. But adding

Code:

--enable-rmtcalls

fixed the issue for me"

So do you have the refered to version of rpcbind installed on your Ubuntu server?

If not that then it seems something else in libnsf has broken the "magic" way Kodi uses to find NFS servers to access, and so you would need to mount as shares at OS level.

[Offsprin]

So the issue is being unable to mount a new share via Kodi?
To step through and ensure I am understanding: You are trying to add a new music or video source and on the "Browse for new share" dialog you click on the "Network File System (NFS)" item.

At that point Koid makes a libnfs call to nfs_find_local_servers which probes all local networks for NFS servers.
Having log "ERROR: GetDirectory - Error getting nfs://" implies that libnfs call is unsucessfull.

Digging more I found some previous discussion here https://forum.kodi.tv/showthread.php?tid...pid2778801 and an issue was raised against libnfs https://github.com/sahlberg/libnfs/issues/270 which concludes:
"rpcbind doesn't respond to broadcast requests when using the default build configuration. But adding

Code:

--enable-rmtcalls

fixed the issue for me"

So do you have the refered to version of rpcbind installed on your Ubuntu server?

If not that then it seems something else in libnsf has broken the "magic" way Kodi uses to find NFS servers to access, and so you would need to mount as shares at OS level.

It's not just attempting to add a new music or video source through Kodi, if I've already mounted the source it also throws the same error. I'm not sure about the rpcbind, I'll check that and let you know.

EDIT: I've got rpcbind 1.2.5-8 installed, so I don't have the special version installed. But like I said, even if I was mounting the share via the OS it was erroring out. That said, I'll try it again and let you know what I find.

EDIT 2: Mounting the share through the OS does work, but I'm still crashing and the crash logs aren't showing anything other than "Kodi quit." which is odd, and I have to believe unrelated.

[Offsprin]

As an additional note: my Windows 10 fresh Kodi install is experiencing the same issue, so it's something to do with the NFS server share itself.