Hi,
I have a mythtv setup I've been running off and on for over a decade.
While bringing it back to life I have found a show that I believe is
only a mySQL entry. And I can not get rid of (delete) it! My fear is
that mythtv scripts will fail and exit on this entry and soon there will
be a backlog of old entries and recordings.
I'm running mythbackend version v32.0. When I run ./find_orphan.py it
generates a Warning and fails to delete the offending orphaned recording
entry:
>> ./find_orphans.py
> Recordings with missing files
> myth: Sleepy Hollow - Paradise Lost 1321_20150308020000.mpg
> Count: 1
> Database backups
> myth: /mnt/space_002/recordings/mythconverg-1350-20230102182941.sql.gz 101.9MB
> myth: /mnt/space_002/recordings/mythconverg-1361-20230108043803.sql.gz 103.1MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql 494.7MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql.gz 5.9MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032610.sql.gz 101.9MB
> Total: 807.4MB
> Please select from the following
> 1. Delete orphaned recording entries
> 2. Refresh list
>> 1
> The following recordings will be deleted
> myth: Sleepy Hollow - Paradise Lost 1321_20150308020000.mpg
> Count: 1
> Are you sure you want to continue?
>> yes
> Warning: Failed to delete 'myth: Sleepy Hollow - Paradise Lost'
> Recordings with missing files
> myth: Sleepy Hollow - Paradise Lost 1321_20150308020000.mpg
> Count: 1
> Database backups
> myth: /mnt/space_002/recordings/mythconverg-1350-20230102182941.sql.gz 101.9MB
> myth: /mnt/space_002/recordings/mythconverg-1361-20230108043803.sql.gz 103.1MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql 494.7MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql.gz 5.9MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032610.sql.gz 101.9MB
> Total: 807.4MB
> Please select from the following
> 1. Delete orphaned recording entries
> 2. Refresh list
>>
... I edited the Python scrip to print out the data base entry retrieved
just before it attempted the call to rec.delete():
> <Recorded 'Sleepy Hollow','2015-03-07 20:00:00-06:00' at 0x7f2e3c15e570>
... Anyone know if that entry is badly formed? Or, if possible, to
simply delete the entry manually?
-thanks
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
I have a mythtv setup I've been running off and on for over a decade.
While bringing it back to life I have found a show that I believe is
only a mySQL entry. And I can not get rid of (delete) it! My fear is
that mythtv scripts will fail and exit on this entry and soon there will
be a backlog of old entries and recordings.
I'm running mythbackend version v32.0. When I run ./find_orphan.py it
generates a Warning and fails to delete the offending orphaned recording
entry:
>> ./find_orphans.py
> Recordings with missing files
> myth: Sleepy Hollow - Paradise Lost 1321_20150308020000.mpg
> Count: 1
> Database backups
> myth: /mnt/space_002/recordings/mythconverg-1350-20230102182941.sql.gz 101.9MB
> myth: /mnt/space_002/recordings/mythconverg-1361-20230108043803.sql.gz 103.1MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql 494.7MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql.gz 5.9MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032610.sql.gz 101.9MB
> Total: 807.4MB
> Please select from the following
> 1. Delete orphaned recording entries
> 2. Refresh list
>> 1
> The following recordings will be deleted
> myth: Sleepy Hollow - Paradise Lost 1321_20150308020000.mpg
> Count: 1
> Are you sure you want to continue?
>> yes
> Warning: Failed to delete 'myth: Sleepy Hollow - Paradise Lost'
> Recordings with missing files
> myth: Sleepy Hollow - Paradise Lost 1321_20150308020000.mpg
> Count: 1
> Database backups
> myth: /mnt/space_002/recordings/mythconverg-1350-20230102182941.sql.gz 101.9MB
> myth: /mnt/space_002/recordings/mythconverg-1361-20230108043803.sql.gz 103.1MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql 494.7MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032536.sql.gz 5.9MB
> myth: /mnt/space_003/recordings/mythconverg-1350-20200913032610.sql.gz 101.9MB
> Total: 807.4MB
> Please select from the following
> 1. Delete orphaned recording entries
> 2. Refresh list
>>
... I edited the Python scrip to print out the data base entry retrieved
just before it attempted the call to rec.delete():
> <Recorded 'Sleepy Hollow','2015-03-07 20:00:00-06:00' at 0x7f2e3c15e570>
... Anyone know if that entry is badly formed? Or, if possible, to
simply delete the entry manually?
-thanks
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org