mapping NFS storage from XO fails, but works fine from terminal?

linkandzelda

Hi all, I'm very new to xcp-ng and am getting ready to migrate my home lab to xcp-ng + xo from an ubuntu setup.

As such I'm currently running xcp-ng in KVM to try and get things as ready as possible, and have ran into a weird problem mapping some network storage via NFS

briefly, in pictures:
https://imgur.com/a/3JY8ztj

XO gave would just sit there after I enter the nfs server IP until eventually giving me the error "Cannot ready property 'nfs-exports' of null.

intially I went to the server and checked ufw logs and saw it was blocking traffic from the xcp-ng VM ip of 192.168.100.202 on port 111, which I had blocked (I followed a guide that said to unblock port 2049 for nfs). I unblocked 111 as well but it didn't seem to change anything

after that I went to the console for xcp-ng and tried to map the folder manually and it worked fine.

I'm not uh...I guess I'm not looking for a solution cuz I'm fine with just using the console to map for now, but curious if this is something I did wrong in the GUI or what.

Danp

You failed to show us your settings in XO where you attempted to establish the NFS connection. I assume you were doing this under Settings > Remotes, correct?

linkandzelda

I went to the plus icon on the bottom of the left menu bar in XO, then storage
I selected my host (mind you there's only one)
gave it a name/description
then chose "NFS" under select storage type.

I added another pic to the imgur album

edit: also tried through the settings > remotes menu for fun, also doesn't work

Danp

From your recent screenshots, I assume that you are wanting to create an NFS SR. If that's correct, then you can ignore my earlier comment about Settings > Remotes.

Are you receiving the error when you click the Search button (magnifying glass icon) after entering the IP address?

linkandzelda

@Danp yes, it takes a long time but eventually I get the error messages you can see in the screenshot of logs

that is: "Cannot read property 'nfs-exports' of null"

if it helps any the server is running nfs 4, I'm struggling to figure out how to monitor logs from it but if anyone wants to give me a tip on that I can then post any error messages I get from the server side too.

Danp

I assume you are running XO from sources. Have you tried with XOA?

Also, you may want to review this issue -- https://github.com/vatesfr/xen-orchestra/issues/1845

hoerup created this issue in vatesfr/xen-orchestra

closed Can't create ISO NFS SR via XOA #1845

linkandzelda

@Danp yeah I used the installerupdater script, not 100% sure what the difference is between the two but I'll read up, and will check that link, ty

tony

@dewittgarry whats the result of

showmount -e 192.168.100.1

linkandzelda

@tony
"rpc mount export: RPC: Timed out"

some more images, I also tried on a laptop I had lying around, same issue, and I found some entries in firewall logs showing it blocking xcp-ng at some random ephemeral ports.

also not that it really helps but I can showmount from the server to the server so at least nfs is replying to requests even if it's just from itself

https://imgur.com/a/1ILqExG

Forza

@dewittgarry a small tip. You can upload or "paste" images directly here in the forum instead of going through imgurl

linkandzelda

@S-Pam Thank you. Got too used to reddit's garbage handling of images imgur became a habit.

tony

@linkandzelda what OS do you use as the NFS server?

confirm with rpcinfo

rpcinfo -p 192.168.100.1

Danp

There was a recent commit on Github dealing with NFS mounts. Suggest that you rebuild with the latest source and then try setting up the NFS storage again.