[mythtv-users] Recordings failing

[Phill Edwards]

>
> My Mythbuntu backend has been working just fine for ages. All of a sudden
> I'm getting 0MB size recordings. I thought it may be that the NFS share on
> which recordings are stored was down, but it seems just fine.
>
> I see this in the MythTV Backend Status > Tuner page on Mythweb, but I
> think it's always been like this (in fact I don't know how to get rid of
> the Encoder 1-6 entries). I don't know why they all say "not recording"
> because there are some recordings in progress (albeit they're producing 0
> size files).
>
> Encoder 1 [ HDHOMERUN : 11100FEA-0 ] is remote on mbe (currently not
> connected).
> Encoder 2 [ HDHOMERUN : 11100FEA-0 ] is remote on mbe (currently not
> connected).
> Encoder 3 [ HDHOMERUN : 11100FEA-1 ] is remote on mbe (currently not
> connected).
> Encoder 4 [ HDHOMERUN : 11100FEA-1 ] is remote on mbe (currently not
> connected).
> Encoder 5 [ HDHOMERUN : 11100FEA-0 ] is remote on mbe (currently not
> connected).
> Encoder 6 [ HDHOMERUN : 11100FEA-1 ] is remote on mbe (currently not
> connected).
> Encoder 25 [ HDHOMERUN : 11100FEA-0 ] is local on mbe2 and is not
> recording.
> Encoder 26 [ HDHOMERUN : 11100FEA-0 ] is local on mbe2 and is not
> recording.
> Encoder 27 [ HDHOMERUN : 11100FEA-1 ] is local on mbe2 and is not
> recording.
> Encoder 28 [ HDHOMERUN : 11100FEA-1 ] is local on mbe2 and is not
> recording.
> Encoder 31 [ DVB : /dev/dvb/adapter0/frontend0 ] is local on mbe2 and is
> not recording.
> Encoder 32 [ DVB : /dev/dvb/adapter0/frontend0 ] is local on mbe2 and is
> not recording.
> Encoder 35 [ DVB : /dev/dvb/adapter1/frontend0 ] is local on mbe2 and is
> not recording.
> Encoder 36 [ DVB : /dev/dvb/adapter1/frontend0 ] is local on mbe2 and is
> not recording.
>
> I'm also seeing entries like this in mythbackend.log which I think may be
> related:
> Dec 16 21:57:28 mbe2 mythbackend: mythbackend[2036]: E ProcessRequest
> programinfo.cpp:2358 (GetPlaybackURL) ProgramInfo(1099_20141216104900.mpg):
> GetPlaybackURL: '1
> 099_20141216104900.mpg' should be local, but it can not be found.
> Dec 16 21:57:28 mbe2 mythbackend: mythbackend[2036]: E ProcessRequest
> programinfo.cpp:2358 (GetPlaybackURL) ProgramInfo(1007_20141216104900.mpg):
> GetPlaybackURL: '1
> 007_20141216104900.mpg' should be local, but it can not be found.
>
> I've read that should be local, but it can not be found" can indicate a
> tuner failure. As I have 4 tuners, what's the best way to find out exactly
> which one is failing? Do you just have to disconnect all of them and
> reconnect each one in turn and try to record something, or is there an
> easier way?
>

I've found some more info on this. If I got into mythtv-setup, on exiting
mythtv-setup I get a message saying "Unable to create file
/mnt/xvdc1/recordings//.test - directory is not writable". I don't
understand why it's reporting not writable because if I go to the command
prompt I can create a file as mythtv in that directory. However, I notice
that the exiting recordings are nobody:nogroup so perhaps that's the
problem, but I don't know how to fix this. Do I somehow change things so
the user nobody can write to that directory, or somehow change mythtv so
that it creates files as mythtv?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20141216/f8c34815/attachment.html>