<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Sep 23, 2015 at 3:23 AM, Hika van den Hoven <span dir="ltr"><<a href="mailto:hikavdh@gmail.com" target="_blank">hikavdh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hoi Ian,<br>
<div><div class="h5"><br>
Wednesday, September 23, 2015, 9:09:56 AM, you wrote:<br>
<br>
> On Wed, Sep 23, 2015 at 2:42 AM, Hika van den Hoven <<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a>><br>
> wrote:<br>
<br>
>> Hoi Ian,<br>
>><br>
>> Wednesday, September 23, 2015, 8:38:27 AM, you wrote:<br>
>><br>
>> > On Wed, Sep 23, 2015 at 2:01 AM, Hika van den Hoven <<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a>><br>
>> > wrote:<br>
>><br>
>> >> Hoi Hika,<br>
>> >><br>
>> >> Wednesday, September 23, 2015, 7:52:51 AM, you wrote:<br>
>> >><br>
>> >> > Hoi Ian,<br>
>> >><br>
>> >> > Wednesday, September 23, 2015, 8:00:54 AM, you wrote:<br>
>> >><br>
>> >> >> On Wed, Sep 23, 2015 at 1:15 AM, Ian Evans <<a href="mailto:dheianevans@gmail.com">dheianevans@gmail.com</a>><br>
>> >> wrote:<br>
>> >><br>
>> >> >>> On Wed, Sep 23, 2015 at 12:21 AM, Ian Evans <<a href="mailto:dheianevans@gmail.com">dheianevans@gmail.com</a>><br>
>> >> wrote:<br>
>> >> >>><br>
>> >> >>>> Been running Mythnews since I started with Myth in 2011. Running<br>
>> >> >>>> .27-fixes.<br>
>> >> >>>><br>
>> >> >>>> Tonight, went to check my feeds and News Feeds wasn't in my<br>
>> >> Information<br>
>> >> >>>> Center at all. I decided to exit and restart the frontend (I'm on a<br>
>> >> >>>> combined FE/BE BTW) and was presented with a message that Myth<br>
>> wanted<br>
>> >> to<br>
>> >> >>>> upgrade the Music schema from 1000 to 1020. Did I miss something or<br>
>> >> has my<br>
>> >> >>>> setup gone haywire?<br>
>> >> >>>><br>
>> >> >>>> Thanks.<br>
>> >> >>>><br>
>> >> >>><br>
>> >> >>> after I fired up the frontend again, I checked the log. Seems Myth<br>
>> is<br>
>> >> >>> trying to add fields that already exist. Myhnews is also still not<br>
>> >> showing<br>
>> >> >>> up:<br>
>> >> >>><br>
>> >> >>> Sep 23 01:04:30 buster mythfrontend.real: mythfrontend[3090]: I<br>
>> >> >>> CoreContext schemawizard.cpp:118 (Compare) Current MythMusic Schema<br>
>> >> Version<br>
>> >> >>> (MusicDBSchemaVer): 1000<br>
>> >> >>> Sep 23 01:04:30 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext dbutil.cpp:604 (DoBackup) Backing up database with<br>
>> script:<br>
>> >> >>> '/usr/share/mythtv/<a href="http://mythconverg_backup.pl" rel="noreferrer" target="_blank">mythconverg_backup.pl</a>'<br>
>> >> >>> Sep 23 01:04:54 buster mythfrontend.real: mythfrontend[3090]: C<br>
>> >> >>> CoreContext dbutil.cpp:625 (DoBackup) Database Backup complete.<br>
>> >> >>> Sep 23 01:04:54 buster mythfrontend.real: mythfrontend[3090]: C<br>
>> >> >>> CoreContext dbutil.cpp:656 (DoBackup) Backed up database to file:<br>
>> >> >>> '/var/lib/mythtv/db_backups/mythconverg-1317-20150923050430.sql.gz'<br>
>> >> >>> Sep 23 01:04:56 buster mythfrontend.real: mythfrontend[3090]: I<br>
>> >> >>> CoreContext bonjourregister.cpp:115 (BonjourCallback) Bonjour:<br>
>> Service<br>
>> >> >>> registration complete: name 'Mythfrontend on buster' type<br>
>> >> >>> '_mythfrontend._tcp.' domain: 'local.'<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext main.cpp:685 (mythplugin_init) Couldn't upgrade music<br>
>> >> database<br>
>> >> >>> schema, exiting.<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext mythplugin.cpp:166 (init_plugin) Unable to initialize<br>
>> >> plugin<br>
>> >> >>> 'mythmusic'.<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: I<br>
>> >> >>> CoreContext mythtranslation.cpp:65 (load) Loading en_us translation<br>
>> for<br>
>> >> >>> module mythnetvision<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: N<br>
>> >> >>> CoreContext dbcheck.cpp:38 (performActualUpdate) Upgrading to<br>
>> MythNews<br>
>> >> >>> schema version 1001<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext dbcheck.cpp:53 (performActualUpdate) DB Error<br>
>> (Performing<br>
>> >> >>> database upgrade): #012Query was: ALTER TABLE `newssites` ADD<br>
>> `podcast`<br>
>> >> >>> BOOL NOT NULL DEFAULT '0'; #012<br>
>> >> >>> Error was: Driver error was [2/1060]:#012QMYSQL: Unable to execute<br>
>> >> >>> query#012Database error was:#012Duplicate column name 'podcast'#012<br>
>> >> #012new<br>
>> >> >>> version: 1001<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext main.cpp:69 (mythplugin_init) Couldn't upgrade database<br>
>> to<br>
>> >> new<br>
>> >> >>> schema, exiting.<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext mythplugin.cpp:166 (init_plugin) Unable to initialize<br>
>> >> plugin<br>
>> >> >>> 'mythnews'.<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: N<br>
>> >> >>> CoreContext dbcheck.cpp:31 (performActualUpdate) Upgrading to<br>
>> >> MythWeather<br>
>> >> >>> schema version 1001<br>
>> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E<br>
>> >> >>> CoreContext dbcheck.cpp:48 (performActualUpdate) DB Error<br>
>> (Performing<br>
>> >> >>> database upgrade): #012Query was: ALTER TABLE weathersourcesettings<br>
>> ADD<br>
>> >> >>> COLUMN updated TIMESTAMP NOT NU<br>
>> >> >>> LL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP;<br>
>> >> >>> #012Error was: Driver error was [2/1060]:#012QMYSQL: Unable to<br>
>> execute<br>
>> >> >>> query#012Database error was:#012Duplicate column name 'updated'#012<br>
>> >> #012new<br>
>> >> >>> version: 1001<br>
>> >> >>><br>
>> >> >>><br>
>> >><br>
>> >> >> Looking at this Michael Dean email from 2014, I see the only option<br>
>> may<br>
>> >> ne<br>
>> >> >> to go back to a database backup from a few days ago before the schema<br>
>> >> >> upgrade attempt:<br>
>> >> >><br>
>> >><br>
>> <a href="http://lists.mythtv.org/pipermail/mythtv-users/2014-December/374753.html" rel="noreferrer" target="_blank">http://lists.mythtv.org/pipermail/mythtv-users/2014-December/374753.html</a><br>
>> >><br>
>> >> >> May be a terribly obvious question, but what happens to the recording<br>
>> >> >> entries done after the last clean backup? Do I lose those entries?<br>
>> The<br>
>> >> >> timing of this is a real WAF storm...I can't fix this right now and a<br>
>> >> Law &<br>
>> >> >> Order marathon for the missus starts at 9am.<br>
>> >><br>
>> >> > The simple answer yes, on a full restore you lose all changes to the<br>
>> >> > database since the backup, no you don't lose the files. You can import<br>
>> >> > them in the video library.<br>
>> >><br>
>> >> > You can however, if you're handy enough do a partial restore of just<br>
>> >> > the broken table.<br>
>> >><br>
>> >> > I suggest before you do anything to make a fresh backup.<br>
>> >><br>
>> >> > And if you secure your backups, so they won't rotate out, you can do<br>
>> >> > all this after your misses marathon!<br>
>> >><br>
>> >> > Tot mails,<br>
>> >> > Hika mailto:<a href="mailto:hikavdh@gmail.com">hikavdh@gmail.com</a><br>
>> >><br>
>> >> What I would do in order:<br>
>> >> - make a backup<br>
>> >> - bring mythbackend down<br>
>> >> - go into phpmyadmin and rename the mythconverg database<br>
>> >> - restore the backup<br>
>> >> - drop the broken table from the renamed database<br>
>> >> - copy the table from the backup to the renamed database<br>
>> >> - drop the backup<br>
>> >> - rename the renamed database back to mythconverg<br>
>> >> - restart the backend and see what happens<br>
>> >><br>
>><br>
>> > Just to clarify...shouldn't I be restoring an older backup (pre the error<br>
>> > messages in the logs) and then copying those tables over to the renamed<br>
>> > mythconverg?<br>
>><br>
>> Yes of course<br>
>><br>
>><br>
> I went back several days to a backup from before the error messages started<br>
> happening and copied those tables over.<br>
<br>
> Here's a tired, very sleepy question: since this issue is just affecting<br>
> plugins (Weather, News, Music) if I uninstall them and reinstall them, will<br>
> it delete those tables and create new ones? Very little customization so I<br>
> don't mind reinstalling them.<br>
<br>
</div></div>I do not know. But I was later thinking in that line. I think if you<br>
simply drop that table and restart, they will get recreated. If I<br>
remember correct the plug-in initialization is done by the frontend.<br>
However DO MAKE A BACKUP before you do anything.<br>
<span class="im HOEnZb"><br>
<br><br></span></blockquote><div>Heading off to bed...341am in Toronto.<br><br></div><div>Here's the thing...removing mythweather, music and news doesn't delete the corresponding tables, even if you use purge in apt-get.<br><br></div><div>So when you reinstall and fire up the frontend, it gives the same complaints about the tables.<br><br></div><div>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.<br><br></div><div>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.<br><br></div><div>Thanks!<br></div></div><br></div></div>