[mythtv-users] ts File Migration to New Backend

[Stephen Worthington]

On Sun, 17 Nov 2024 22:53:23 +0000, you wrote:

>On 17/11/2024 20:40, Barry Martin wrote:
>>
>> Hi Folks!
>>
>>
>> Follow-up to this morning
. Thought I was unable to play the files because of a permission error;
>> sort of made sense as the storage hard drive was also saying zero’s. Changed permission to
>> myth:myth, recursive switch. Nope. Stop and restart mythbackend? Nope.  Power boot? Nope

Good thought, the numbers used to represent a user or group can differ
between systems, so you do want to do "chown mythtv:mythtv" on all the
recording files.

>>
>> Tidbits from the mythfrontend Terminal log:
>>
>> No plugins directory /usr/lib/mythtv/plugins
>>
>> ==> This for options like Weather, Streaming, etc?

Yes.  You will need to install the appropriate MythTV plugin packages.
I have mythmusic and mytharchive installed:

root at mypvr:~# ll /usr/lib/mythtv/plugins/
total 2084
drwxr-xr-x 2 root root    4096 Nov  6 03:20 ./
drwxr-xr-x 3 root root    4096 Oct  7  2020 ../
-rw-r--r-- 1 root root  623824 Nov  5 03:18 libmytharchive.so
-rw-r--r-- 1 root root 1496584 Nov  5 03:18 libmythmusic.so


This lists all packages that are installed and have "myth" in the
name:

root at mypvr:~# apt list --installed | grep myth

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

kodi-pvr-mythtv/now 6:21.0.5-1~jammy amd64 [installed,local]
libmyth-dev/noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64 [installed]
libmyth-python/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all
[installed,automatic]
libmyth/noble,now 2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1
amd64 [installed,automatic]
libmythtv-perl/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all
[installed,automatic]
mytharchive/noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64 [installed]
mythexport/now 2.2.4-0ubuntu5-jsw2 amd64 [installed,local]
mythfrontend-qml/noble,now
3:0.0.14.alpha~stable.202411011028.cc9fce2~ubuntu24.04.1 amd64
[installed]
mythimport/now 2.2.4-0ubuntu5-jsw2 amd64 [installed,local]
mythmusic/noble,now 2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1
amd64 [installed]
mythtv-backend-master/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]
mythtv-backend/noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64
[installed,automatic]
mythtv-common/noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64
[installed,automatic]
mythtv-database/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all
[installed,automatic]
mythtv-doc/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]
mythtv-frontend/noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64
[installed,automatic]
mythtv-status/noble,noble,now 1.1.0-1 all [installed]
mythtv-theme-mythbuntu/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]
mythtv-transcode-utils/noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64
[installed,automatic]
mythtv/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]
mythweb/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]
php-mythtv/noble,noble,now
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]
python3-mythtvservices/now 0.2.4-0~14~precise1 all [installed,local]


>>
>> 2024-11-17 11:13:49.761229 W SSL: SSL Host key file (/home/barry/.mythtv/certificates/key.pem) does
>> not exist or is not readable

This is not a problem, unless you are using a particular feature (I am
not sure exactly which) where another device is streaming from MythTV
and needs to have a properly signed certificate before it will
connect.

>> 2024-11-17 11:14:11.150167 E PlaybackBoxHelper: CHECK_AVAILABILITY
>> 'myth://be5/14705_20230926043500.ts' file not found
>>
>> ==> Looking at non-existent subdir?? Files at /mount/WD_4TB/Default/ (the one I did the chown on.)
>>
>>
>> Stranger (to me): the new system (BE5) did a recording. The show was added to the Media Library >
>> Recordings properly but file not found (and x’d like everyone else). Thought I could find it –
>> filenames seem to follow the pattern of station id(?)_YYYYMMDD time something.ts, so should be able
>> to find today: 20241117. Nope: not anywhere on the system. Also tried tomorrow and yesterday – also
>> nope. (Loss of that particular recording no big deal, just thought might tell me where the system is
>> looking.)

Mythfrontend can now tell you where a recording is stored, as long as
it can find it (not marked with an X).  On a recording in the list,
hit I on the keyboard twice and scroll if necessary to find the
storage location (look for "Recorded Pathname").

If there are no valid storage directories to record to, I suspect that
mythbackend has a default directory it will use.  It is likely
somewhere under /var, so this should find it, if it exists:

sudo find /var -iname "*.ts"

>>
>> The only other thing I can think of is something not configured correctly in fstab. The line is:
>> /dev/disk/by-uuid/75d4f7d7-<snip>8de /mount/WD_4TB auto
>> nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=WD_4TB 0 0

So, can you see that drive mounted on /mount/WD_4TB?

First, does the mountpoint exist?

sudo ls -al /mount

Does the system think the drive is mounted?

sudo mount | grep WD_4TB

Then does the mountpoint have any directories or files under it?

sudo ls -al /mount/WD_4TB/

My best guess for the problem would be that you forgot to create the
mountpoint directory.  I do that all the time!.  To fix that:

sudo su
mkdir -p /mount/WD_4TB
chown mythtv:mythtv /mount/WD_4TB
chmod a-rwx /mount/WD_4TB
mount /mount/WD_4TB
exit

The "chmod" line is optional - what it does is remove all permissions
on the mountpoint directory itself, before anything is mounted on the
mountpoint.  So if nothing is mounted on the mountpoint, software that
expects something to be mounted and goes ahead and writes to the
mountpoint directory or to directories below the mountpoint directory
will get an error, instead of working and creating files below the
mountpoint directory that will then be masked when something gets
mounted on the mountpoint.  Do NOT do the "chmod" command if there is
a drive mounted on the mountpoint - it would be changing the
permissions on the mounted drive rather than the mountpoint itself.

I normally want any software to be able to create new mountpoints, so
I have my /mnt directory freely accessible.  To do that for your
/mount directory:

sudo chmod a+rwx /mount

>Quick thought: have a look at your storage groups, see where they have been set to.

Yes, that sounds like the problem.  MythTV will only see recording
files that are in a storage group directory.  On BE5, the restored
database will have the storage groups set to the same directories as
they were on BE4.  So the directories in your storage group settings
have to exist in the same places on BE5 as they were on BE4.

To see all the storage groups:

sudo mysql
select * from storagegroup order by groupname,dirname;
exit