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

Wed Sep 23 07:09:56 UTC 2015

On Wed, Sep 23, 2015 at 2:42 AM, Hika van den Hoven <hikavdh at gmail.com>
wrote:

> Hoi Ian,
>
> Wednesday, September 23, 2015, 8:38:27 AM, you wrote:
>
> > On Wed, Sep 23, 2015 at 2:01 AM, Hika van den Hoven <hikavdh at gmail.com>
> > wrote:
>
> >> Hoi Hika,
> >>
> >> Wednesday, September 23, 2015, 7:52:51 AM, you wrote:
> >>
> >> > Hoi Ian,
> >>
> >> > Wednesday, September 23, 2015, 8:00:54 AM, you wrote:
> >>
> >> >> On Wed, Sep 23, 2015 at 1:15 AM, Ian Evans <dheianevans at gmail.com>
> >> wrote:
> >>
> >> >>> On Wed, Sep 23, 2015 at 12:21 AM, Ian Evans <dheianevans at gmail.com>
> >> wrote:
> >> >>>
> >> >>>> Been running Mythnews since I started with Myth in 2011. Running
> >> >>>> .27-fixes.
> >> >>>>
> >> >>>> Tonight, went to check my feeds and News Feeds wasn't in my
> >> Information
> >> >>>> Center at all. I decided to exit and restart the frontend (I'm on a
> >> >>>> combined FE/BE BTW) and was presented with a message that Myth
> wanted
> >> to
> >> >>>> upgrade the Music schema from 1000 to 1020. Did I miss something or
> >> has my
> >> >>>> setup gone haywire?
> >> >>>>
> >> >>>> Thanks.
> >> >>>>
> >> >>>
> >> >>> after I fired up the frontend again, I checked the log. Seems Myth
> is
> >> >>> trying to add fields that already exist. Myhnews is also still not
> >> showing
> >> >>> up:
> >> >>>
> >> >>> Sep 23 01:04:30 buster mythfrontend.real: mythfrontend[3090]: I
> >> >>> CoreContext schemawizard.cpp:118 (Compare) Current MythMusic Schema
> >> Version
> >> >>> (MusicDBSchemaVer): 1000
> >> >>> Sep 23 01:04:30 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext dbutil.cpp:604 (DoBackup) Backing up database with
> script:
> >> >>> '/usr/share/mythtv/mythconverg_backup.pl'
> >> >>> Sep 23 01:04:54 buster mythfrontend.real: mythfrontend[3090]: C
> >> >>> CoreContext dbutil.cpp:625 (DoBackup) Database Backup complete.
> >> >>> Sep 23 01:04:54 buster mythfrontend.real: mythfrontend[3090]: C
> >> >>> CoreContext dbutil.cpp:656 (DoBackup) Backed up database to file:
> >> >>> '/var/lib/mythtv/db_backups/mythconverg-1317-20150923050430.sql.gz'
> >> >>> Sep 23 01:04:56 buster mythfrontend.real: mythfrontend[3090]: I
> >> >>> CoreContext bonjourregister.cpp:115 (BonjourCallback) Bonjour:
> Service
> >> >>> registration complete: name 'Mythfrontend on buster' type
> >> >>> '_mythfrontend._tcp.' domain: 'local.'
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext main.cpp:685 (mythplugin_init) Couldn't upgrade music
> >> database
> >> >>> schema, exiting.
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext mythplugin.cpp:166 (init_plugin) Unable to initialize
> >> plugin
> >> >>> 'mythmusic'.
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: I
> >> >>> CoreContext mythtranslation.cpp:65 (load) Loading en_us translation
> for
> >> >>> module mythnetvision
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: N
> >> >>> CoreContext dbcheck.cpp:38 (performActualUpdate) Upgrading to
> MythNews
> >> >>> schema version 1001
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext dbcheck.cpp:53 (performActualUpdate) DB Error
> (Performing
> >> >>> database upgrade): #012Query was: ALTER TABLE `newssites` ADD
> `podcast`
> >> >>> BOOL NOT NULL DEFAULT '0'; #012
> >> >>> Error was: Driver error was [2/1060]:#012QMYSQL: Unable to execute
> >> >>> query#012Database error was:#012Duplicate column name 'podcast'#012
> >> #012new
> >> >>> version: 1001
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext main.cpp:69 (mythplugin_init) Couldn't upgrade database
> to
> >> new
> >> >>> schema, exiting.
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext mythplugin.cpp:166 (init_plugin) Unable to initialize
> >> plugin
> >> >>> 'mythnews'.
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: N
> >> >>> CoreContext dbcheck.cpp:31 (performActualUpdate) Upgrading to
> >> MythWeather
> >> >>> schema version 1001
> >> >>> Sep 23 01:05:31 buster mythfrontend.real: mythfrontend[3090]: E
> >> >>> CoreContext dbcheck.cpp:48 (performActualUpdate) DB Error
> (Performing
> >> >>> database upgrade): #012Query was: ALTER TABLE weathersourcesettings
> ADD
> >> >>> COLUMN updated TIMESTAMP NOT NU
> >> >>> LL DEFAULT CURRENT_TIMESTAMP           ON UPDATE CURRENT_TIMESTAMP;
> >> >>> #012Error was: Driver error was [2/1060]:#012QMYSQL: Unable to
> execute
> >> >>> query#012Database error was:#012Duplicate column name 'updated'#012
> >> #012new
> >> >>> version: 1001
> >> >>>
> >> >>>
> >>
> >> >> Looking at this Michael Dean email from 2014, I see the only option
> may
> >> ne
> >> >> to go back to a database backup from a few days ago before the schema
> >> >> upgrade attempt:
> >> >>
> >>
> http://lists.mythtv.org/pipermail/mythtv-users/2014-December/374753.html
> >>
> >> >> May be a terribly obvious question, but what happens to the recording
> >> >> entries done after the last clean backup? Do I lose those entries?
> The
> >> >> timing of this is a real WAF storm...I can't fix this right now and a
> >> Law &
> >> >> Order marathon for the missus starts at 9am.
> >>
> >> > The simple answer yes, on a full restore you lose all changes to the
> >> > database since the backup, no you don't lose the files. You can import
> >> > them in the video library.
> >>
> >> > You can however, if you're handy enough do a partial restore of just
> >> > the broken table.
> >>
> >> > I suggest before you do anything to make a fresh backup.
> >>
> >> > And if you secure your backups, so they won't rotate out, you can do
> >> > all this after your misses marathon!
> >>
> >> > Tot mails,
> >> >   Hika                            mailto:hikavdh at gmail.com
> >>
> >> What I would do in order:
> >>  - make a backup
> >>  - bring mythbackend down
> >>  - go into phpmyadmin and rename the mythconverg database
> >>  - restore the backup
> >>  - drop the broken table from the renamed database
> >>  - copy the table from the backup to the renamed database
> >>  - drop the backup
> >>  - rename the renamed database back to mythconverg
> >>  - restart the backend and see what happens
> >>
>
> > Just to clarify...shouldn't I be restoring an older backup (pre the error
> > messages in the logs) and then copying those tables over to the renamed
> > mythconverg?
>
> Yes of course
>
>
I went back several days to a backup from before the error messages started
happening and copied those tables over.

Here's a tired, very sleepy question: since this issue is just affecting
plugins (Weather, News, Music) if I uninstall them and reinstall them, will
it delete those tables and create new ones? Very little customization so I
don't mind reinstalling them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20150923/527aa60f/attachment.html>