[mythtv-users] Mythnews disappears and Music schema update notice

[Ian Evans]

On Wed, Sep 23, 2015 at 6:08 AM, Paul Harrison <mythtv at sky.com> wrote:

> On 23/09/15 10:13, Hika van den Hoven wrote:
>
>> Hoi Paul,
>>
>> Wednesday, September 23, 2015, 10:47:29 AM, you wrote:
>>
>> On 23/09/15 08:55, Hika van den Hoven wrote:
>>>
>>>> Here's the thing...removing mythweather, music and news doesn't delete
>>>>> the
>>>>> corresponding tables, even if you use purge in apt-get.
>>>>> So when you reinstall and fire up the frontend, it gives the same
>>>>> complaints about the tables.
>>>>> HOWEVER, if you drop the tables after purging and reinstalling, the
>>>>> frontend log complains it can't find the tables in order to upgrade
>>>>> them.
>>>>> So purging/reinstalling doesn't seem to recreate/initialize the tables.
>>>>> I gotta sleep...but I appreciate your help. Hopefully you and others
>>>>> will
>>>>> see the issue and I'll fight the good fight when I wake up.
>>>>> Thanks!
>>>>>
>>>> I'm surprised! I would expect the same proces that caused the problem
>>>> to recreate the tables. How then if you add a plug-in to a running
>>>> system? Normally on a fresh or updated system the frontend when first
>>>> run does this!
>>>>
>>>>
>>>> Each plugin has it own schema version and we store the version in the
>>> settings table so for MythNews it's  'NewsDBSchemaVer'.
>>> The database upgrade code looks at the schema version in the settings
>>> table and only attempts to update it if it is lower than the actually
>>> schema version.
>>> Assuming no update to the plugins was performed this looks like a DB
>>> corruption problem of some sort so running optimize_mythdb.pl would be a
>>> good idea.
>>> If you have dropped the MythNews table you will have to remove the
>>> 'NewsDBSchemaVer' schema version setting in the settings table to get
>>> the plugin to recreate the tables.
>>> Paul H.
>>> _______________________________________________
>>>
>> Thanks also on behalf of Ian. So his problem could have come from
>> corruption of that value! Does optimize_mythdb.pl check on those
>> version values? I mean, deeper then just comparing?
>>
>
> All the script does is tell mysql to check the tables and repair/analyse
> them. It doesn't do anything more than that (actually the latest version
> will defrag some of the larger tables but that's all).
>
> The weird thing is that his problem was a wrongfully attempt at
>> upgrading, but when he dropped the table it did nothing?
>>
>
> Must admit it puzzling how it's got in this state even DB corruption
> doesn't really explain the logs.
>
> Take the MythNews table there has only ever been 2 versions of the table
> 1000 was the initial version that goes back many year IIRC and the last one
> is 1001. Unfortunately we are missing from the log snippets what version
> Myth thinks the tables are for MythNews but it is clearly trying to upgrade
> it to 1001. So either the 'NewsDBSchemaVer setting is missing or has a
> strange version?
>
>

Back online for a bit. Just checked for NewsDBSchemaVer and it's showing
1000.

Apart from the weird restart, I have no idea how this happened. I didn't
try to restore any info for the db until last night. Rest of the mythbox is
humming along. Just these three plugins have gone loco. :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20150923/5468edbb/attachment.html>