[mythtv-users] 0.27 Front end Profile Issues

Philip Nourse pjn at pobox.com
Mon Oct 28 01:33:59 UTC 2013


On 2013-10-27 7:43 PM, Michael T. Dean wrote:
> On 10/27/2013 03:42 PM, Philip Nourse wrote:
>> On 2013-10-27 2:06 PM, Philip Nourse wrote:
>>> I just upgraded to 0.27, and I have an issue with the playback 
>>> profiles. Every time I start the front end, it adds another 10 
>>> profiles to the initial group as if it didn't have any profiles to 
>>> start with.  Even worse, if I try to add another frontend, it trys 
>>> to do the same, but faults for trying to add a duplicate key.  It's 
>>> like it doesn't realize that the profiles are already there. Anybody 
>>> else experience this, and how did you resolve it?
>>
>> I just figured it out.  When I migrated the database to the new 
>> server (or when it upgraded -  Devs may want to look into it to be 
>> sure) , the auto increment for the ids was removed for the two 
>> tables.  I put it back in, wiped the tables, and all is corrected.
>
> This is just one of the problems that occurs when you use mysqldump to 
> create a database backup and do not pass the right arguments.  Thus 
> our recommendation to use the official mythconverg_backup.pl and 
> mythconverg_restore.pl scripts for database backups and restore.
>
> http://www.mythtv.org/wiki/Database_Backup_and_Restore
>
> Oh, and the same thing that caused this problem will cause other 
> problems with MythTV, you should consider your schema corrupt and do a 
> partial restore to throw away the bad schema and import the 
> non-recreatable data (recordings, recording history, and such) in your 
> database--otherwise, expect problems down the line.
>
> http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup 
>
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
Fortunately, I used a Migration tool, and ignored the warnings.  I went 
back and restarted the migration (without actually migrating) to get the 
warnings back.   There were only three tables corrupted. I fixed them :)


More information about the mythtv-users mailing list