Rancher + NIFI on Synology DS220j

[coffeeman]

Trying to share out /volume1/kubshare
settings are:
Client *, Privilege R/W, Squash No Mapping, Async Yes, Non-Priv port Allowed, Cross-mount Allowed

I'm getting errors like:

(Nifi requires zookeeper)
Error:
zookeeper couldn’t mount:
MountVolume.SetUp failed for volume "pvc-a1d1e49b-a237-40a7-bb71-84c02cd84cbe" : mount failed: exit status 32 Mounting command: mount Mounting arguments: -t nfs xxx.xxx.xxx.xxx:/volume1/kubshare/nifi-data-nifi-zookeeper-0-pvc-a1d1e49b-a237-40a7-bb71-84c02cd84cbe /var/lib/kubelet/pods/ab8b01e1-468c-4fab-8b18-9dcd10755cb7/volumes/kubernetes.io~nfs/pvc-a1d1e49b-a237-40a7-bb71-84c02cd84cbe Output: mount.nfs: mounting xxx.xxx.xxx.xxx:/volume1/kubshare/nifi-data-nifi-zookeeper-0-pvc-a1d1e49b-a237-40a7-bb71-84c02cd84cbe failed, reason given by server: No such file or directory

I've tried more than a few different settings thus for with nothing working, anyone have any thoughts?

Thx and..
Mo' Coffee

 

[Rusty]

How does etc/exports file looks like on the NAS side (from ssh) not via UI?

 

[coffeeman]

How does etc/exports file looks like on the NAS side (from ssh) not via UI?

Thanks for the response.. turns out by posting this I rubber ducked the answer.
This ended up working:
/volume1/kubshare *(rw,sync,no_subtree_check,no_root_squash,no_all_squash,insecure)
Ill need to add my ips for better security but origonally it was more like this:
/volume1/kubshare *(rw,async,crossmnt,root_squash,no_subtree_check,insecure_locks,anonuid=1024,anongid=100)

Need to read up more on what all these mean cause I do find it odd that both no_root and no_all squash are both in the line that is working. Found the info here.

 

[Rusty]

insecure_locks is usually the problem but glad you got it going. Mark it as solved if you are certain this is working for you now.

tnx

 

[coffeeman]

Not sure if the Synology is resetting something but its not apparent in the /etc/exports

This morning I woke up and my containers are all having errors again. Example:

MountVolume.SetUp failed for volume "pvc-42b1e502-6140-4a28-8b56-76bbdde719de" : mount failed: exit status 32 Mounting command: mount Mounting arguments: -t nfs xxx.xxx.xxx.xxx:/volume1/kubshare/zookeeper-data-zookeeper-0-pvc-42b1e502-6140-4a28-8b56-76bbdde719de /var/lib/kubelet/pods/c4369ce8-3147-4974-a7cb-7a4468737d7a/volumes/kubernetes.io~nfs/pvc-42b1e502-6140-4a28-8b56-76bbdde719de Output: mount.nfs: mounting xxx.xxx.xxx.xxx:/volume1/kubshare/zookeeper-data-zookeeper-0-pvc-42b1e502-6140-4a28-8b56-76bbdde719de failed, reason given by server: No such file or directory

/ect/exports/ (This is the only line related to kubshare in this file)

/volume1/kubshare    *(rw,sync,no_subtree_check,no_root_squash,no_all_squash,insecure)

I rebooted the Synology device and tried redeploying and the same issue. Any thoughts?

 

[one-eyed-king]

Hmm, it almost looks like the pvc target folders can not be created on the nfs share.. Do you mind sharing the output of stat /volume1/kubshare/?

Is it safe to assume that your installed the nfs client provisioner using the helm chart instead of applying a bunch of manifests?

My experience is that nfsv4 or v4.1 shares work reliable while nfsv3 sometimes cause trouble..

 

[coffeeman]

Hmm, it almost looks like the pvc target folders can not be created on the nfs share.. Do you mind sharing the output of stat /volume1/kubshare/?

Is it safe to assume that your installed the nfs client provisioner using the helm chart instead of applying a bunch of manifests?

My experience is that nfsv4 or v4.1 shares work reliable while nfsv3 sometimes cause trouble..

Yes, nfs client was using helm chart.

stat /volume1/kubshare/
File: ‘/volume1/kubshare/’
Size: 12288 Blocks: 24 IO Block: 4096 directory
Device: fd00h/64768d Inode: 243662849 Links: 23
Access: (0777/drwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2020-11-25 10:41:18.764525019 -0600
Modify: 2020-11-17 08:46:22.365504121 -0600
Change: 2020-11-17 08:46:22.365504121 -0600
Birth: -