Too stupid to setup - nfs mount issue
#1
Hi,

finally with a few days off during easter holidays I did a few tweaks to my vdr backend setup. I'm now on vdr 1.7.41 with vnsiplugin3 (0.9.1.git20130320-4yavdr0~precise), switched to vnsi (1.6.4 ) from xvdr. I did not set up a new backend server, I just went to vdr-testing within the yavdr 0.5 repos. Anyway, it's working good,

Though I'm a little bit confused. When trying to get the vnsi xbmc-plugin to connect to the backend it did not work at first. PVR Manager was stuck at getting the channel list. I enabled debugging and found these error messages

Code:
11:45:52 T:2805721920   DEBUG: NFS: Old context timed out - destroying it
11:45:52 T:2805721920   DEBUG: NFS: Context for 192.168.178.41 not open - get a new context.
11:45:52 T:2805721920   ERROR: NFS: Failed to mount nfs share:  (mount/mnt call failed with "RPC error: Mount failed with error MNT3ERR_ACCES(13) Permission denied(13)")

Checking the logs on the backend it said the xbmc plugin (?) needs to have nfs '/' access. The yavdr scripts do not export this by default

Code:
Mar 26 11:51:55 vdr330 rpc.mountd[1342]: refused mount request from 192.168.178.39 for / (/): not exported

As quick and dirty workaround I did export '/' manually and everything is working fine and as expected.

So, my question is: Is this (nfs root export) expected and needed behavior or did I do something wrong - well I'm not aware where and how. btw, and for setting the expectations right. I'm a *nix n00b with too less time to get things done. MAybe I do not sse the big picture here.

Thx.
Reply
#2
Quote:Checking the logs on the backend it said the xbmc plugin (?) needs to have nfs '/' access. The yavdr scripts do not export this by default

Where do you see this? vnsi does nothing with nfs by itself.
Reply
#3
It was/is within syslog - well, I scanned nearly all logs due to not knowing where to search first *sigh*

Her's a little bit more from the log

Code:
Mar 26 11:39:51 vdr330 rpc.mountd[1342]: refused mount request from 192.168.178.39 for / (/): not exported
Mar 26 11:45:52 vdr330 rpc.mountd[1342]: refused mount request from 192.168.178.39 for / (/): not exported
Mar 26 11:46:10 vdr330 vdr: [2606] epg data writer thread started (pid=1384, tid=2606, prio=low)
Mar 26 11:46:10 vdr330 vdr: [2606] epg data writer thread ended (pid=1384, tid=2606)
Mar 26 11:51:35 vdr330 vdr: [1494] loading /var/lib/vdr/plugins/vnsiserver3/allowed_hosts.conf
Mar 26 11:51:35 vdr330 vdr: [1494] VNSI: Client with ID 2 connected: 192.168.178.39:41664
Mar 26 11:51:35 vdr330 vdr: [2608] VNSI: Welcome client 'XBMC Media Center' with protocol version '3'
Mar 26 11:51:55 vdr330 rpc.mountd[1342]: refused mount request from 192.168.178.39 for / (/): not exported
Mar 26 11:56:00 vdr330 vdr: [1505] EPGSearch: timer conflict check started
Mar 26 11:56:00 vdr330 vdr: [1505] EPGSearch: timer conflict check finished
Mar 26 11:56:11 vdr330 vdr: [2674] epg data writer thread started (pid=1384, tid=2674, prio=low)
Mar 26 11:56:11 vdr330 vdr: [2674] epg data writer thread ended (pid=1384, tid=2674)
Mar 26 11:57:57 vdr330 vdr: [2711] xmltv2vdr housekeeping thread started (pid=1384, tid=2711, prio=high)
Mar 26 11:57:57 vdr330 vdr: [2711] xmltv2vdr housekeeping thread ended (pid=1384, tid=2711)
Mar 26 11:57:57 vdr330 rpc.mountd[1342]: refused mount request from 192.168.178.39 for / (/): not exported

btw, same behaviour with xvdr plugin. Something wants '/' exported. Maybe some OpenELEC thing?

Anyway, I'm good with it for the moment. Even my ATV2 - updated it today from 11.0 to 12.1 - does the pvr job (w/o HD content - and w/o post precessing the picture quality is somewhat blurry).
Reply

Logout Mark Read Team Forum Stats Members Help
Too stupid to setup - nfs mount issue0