[mythtv-users] Migration Mythbuntu 10.04 to Mythbuntu 12.04 stuck, Need Help

[Craig Huff]

On Fri, Apr 4, 2014 at 2:08 AM, Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:
> You can just try blindly answering the question it is asking at that
> point, about updating the mythmusic database.  Check the log to make
> sure it has finished its backup, then wait a few seconds more and try
> hitting the Enter key, and if that does not work, try Y and then
> Enter, or even Yes and then Enter.  There should be disk activity when
> it does the schema update to let you know it has happened.  And it is
> likely there will be some more log activity too.

Well, none of those reasonable ideas worked.  In addition (don't know why I
didn't check this before), I noticed today that top shows
mythfrontend.regoing into 100% of one cpu time right after the backup
completes.  I will
see if I can get any more clues by upping the verbosity.  I started
mythfrontend from an xterm and got a few more messages lines than were
showing up in the message log.  Here are the last few lines in the terminal
window:

2014-04-04 15:26:10.001764 N  Registering Internal as a media playback
plugin.
2014-04-04 15:26:10.197372 I  Current MythMusic Schema Version
(MusicDBSchemaVer): 1017
2014-04-04 15:26:10.197406 C  MythMusic database schema is old. Waiting to
see if DB is being upgraded.
2014-04-04 15:26:11.201008 I  Current MythMusic Schema Version
(MusicDBSchemaVer): 1017
2014-04-04 15:26:12.203377 I  Current MythMusic Schema Version
(MusicDBSchemaVer): 1017
2014-04-04 15:26:13.205479 I  Current MythMusic Schema Version
(MusicDBSchemaVer): 1017
2014-04-04 15:26:13.205558 C  Timed out waiting.
2014-04-04 15:26:13.220509 E  Backing up database with script:
'/usr/share/mythtv/mythconverg_backup.pl'
2014-04-04 15:27:37.705289 C  Database Backup complete.
2014-04-04 15:27:38.166414 C  Backed up database to file:
'/video5/recordings/mythconverg-1299-20140404152613.sql.gz'
ICE default IO error handler doing an exit(), pid = 3465, errno = 32
QThreadStorage: Thread 0x923e610 exited after QThreadStorage 5 destroyed
QThreadStorage: Thread 0x9264eb8 exited after QThreadStorage 5 destroyed

If Mike reads this thread: I know, I know, I should pastebin the whole log,
but other than the timestamps, everything above this point is consistent
every time I run the backend, and the last three lines don't appear in the
log file, anywhere.

--
Craig.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140404/543b2e5a/attachment.html>