[mythtv-users] Upgrade 0.24->0.25 goes poorly.

[Ross Boylan]

On Sun, 2012-05-13 at 12:15 -0500, Bill Meek wrote:
> On 05/13/2012 11:57 AM, Ross Boylan wrote:
> > On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
> >> On 05/12/2012 09:22 PM, Ross Boylan wrote:
> >> ...
> >>> /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
> >>> and I don't see much in any logs.
> ...
> >> Check your /etc/init.d/mythtv-backend file. It will tell you where your
> >> logs are going. It won't be the file you looked at above. Expect:
> >>    --syslog sonething or --logpath somethingElse.
> > It is the file I looked at.  Here are the key parts of the init.d file
> >
> > DAEMON=/usr/bin/mythbackend
> > ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile $RUNDIR/$NAME.pid"
> > start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
> >                    --chuid $USER --nicelevel $NICE --exec $DAEMON -- $ARGS
> 
> --logpath must point to a directory, not a file. I understand from your original
> post that --help didn't help, so: http://www.mythtv.org/wiki/Logging#File_Logging.
> In other words:  --logpath /var/log/mythtv.
Thanks.  That's much better.
> 
> >> Copy a good config.xml file to the user's .mythtv directory whose running
> >> the backend. That may be root, or if you're using the --user switch, that
> >> user, most likely mythtv.
Yes, the user is mythtv.  I copied the non-empty version of config.xml
over the file.
> >>
> > Is 0.25 more sensitive to this and 0.24?
> 
> I remember seeing posts on this list saying that config.xml had been zeroed.
> And I've had it happen to me too.

After various false starts and dpkg-reconfigure's my latest log is this:
2012-05-13 21:57:41.204974 C [845/845] thread_unknown mythcommandlineparser.cpp:2534 (ConfigureLogging) - mythbackend version:  [v0.25pre] www.mythtv.org
2012-05-13 21:57:41.205064 N [845/845] thread_unknown mythcommandlineparser.cpp:2536 (ConfigureLogging) - Enabled verbose msgs:  general
2012-05-13 21:57:41.205978 N [845/845] thread_unknown logging.cpp:1176 (logStart) - Setting Log Level to LOG_INFO
2012-05-13 21:57:41.206415 I [845/845] thread_unknown logging.cpp:229 (FileLogger) - Added logging to the console
2012-05-13 21:57:41.206511 I [845/845] thread_unknown logging.cpp:238 (FileLogger) - Added logging to /var/log/mythtv/mythbackend.20120513215741.845.log
2012-05-13 21:57:41.206530 I [845/845] thread_unknown logging.cpp:425 (DatabaseLogger) - Added database logging to table logging
2012-05-13 21:57:41.234081 N [845/845] thread_unknown logging.cpp:1215 (logStart) - Setting up SIGHUP handler
2012-05-13 21:57:41.235416 N [845/845] thread_unknown mythdirs.cpp:51 (InitializeMythDirs) - Using runtime prefix = /usr
2012-05-13 21:57:41.235458 N [845/845] thread_unknown mythdirs.cpp:64 (InitializeMythDirs) - Using configuration directory = /var/lib/mythtv/.mythtv
2012-05-13 21:57:41.235745 I [845/845] CoreContext mythcorecontext.cpp:227 (Init) - Assumed character encoding: en_US.UTF-8
2012-05-13 21:57:41.237495 N [845/845] CoreContext mythcontext.cpp:477 (LoadDatabaseSettings) - Empty LocalHostName.
2012-05-13 21:57:41.237519 I [845/845] CoreContext mythcontext.cpp:481 (LoadDatabaseSettings) - Using localhost value of corn
2012-05-13 21:57:41.403991 N [845/845] CoreContext mythcorecontext.cpp:1270 (InitLocale) - Setting QT default locale to en_US
2012-05-13 21:57:41.404285 I [845/845] CoreContext mythcorecontext.cpp:1303 (SaveLocaleDefaults) - Current locale en_US
2012-05-13 21:57:41.404395 N [845/845] CoreContext mythlocale.cpp:121 (LoadDefaultsFromXML) - Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
2012-05-13 21:57:41.417933 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:41.417972 C [845/845] CoreContext schemawizard.cpp:135 (CompareAndWait) - MythTV database schema is old. Waiting to see if DB is being upgraded.
2012-05-13 21:57:42.422112 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:43.424333 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:44.427462 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:45.430694 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:46.433719 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:46.433846 C [845/845] CoreContext schemawizard.cpp:179 (CompareAndWait) - Timed out waiting.
2012-05-13 21:57:46.434699 C [845/845] CoreContext dbutil.cpp:217 (BackupDB) - Database backups disabled.  Skipping backup.
2012-05-13 21:57:46.437245 I [845/845] CoreContext schemawizard.cpp:316 (PromptForUpgrade) - Console is non-interactive, can't prompt user...
2012-05-13 21:57:46.437263 C [845/845] CoreContext schemawizard.cpp:341 (PromptForUpgrade) - Upgrading.
2012-05-13 21:57:46.437719 C [845/845] CoreContext dbcheck.cpp:495 (UpgradeTVDatabaseSchema) - Newest MythTV Schema Version : 1299
2012-05-13 21:57:46.445251 E [845/845] CoreContext videodbcheck.cpp:369 (doUpgradeVideoDatabaseSchema) - Unrecognized video database schema version. Unable to upgrade database.
2012-05-13 21:57:46.445272 E [845/845] CoreContext videodbcheck.cpp:372 (doUpgradeVideoDatabaseSchema) - Please see mythplugins/mythvideo/README.database for more information.
2012-05-13 21:57:46.445290 E [845/845] CoreContext videodbcheck.cpp:375 (doUpgradeVideoDatabaseSchema) - mythvideo.DBSchemaVer: '1011', VideoDBSchemaVer: '', DVDDBSchemaVer: ''
2012-05-13 21:57:46.445304 E [845/845] CoreContext dbcheck.cpp:509 (UpgradeTVDatabaseSchema) - Database Schema upgrade FAILED, unlocking.
2012-05-13 21:57:46.445505 E [845/845] CoreContext main_helpers.cpp:529 (run_backend) - Couldn't upgrade database to new schema

I'm not sure if the message about the old schema means mythbackend
actually did reach the database, or if it just reflects info cached
somewhere else.  At any rate, the end is clearly a failure.  I can't
find README.Database on my system.

Even info on whether this looks like a problem contacting/logging into
the database (which doesn't seem to be producing any logs, even when I
connect successfully from the command line with mysql) or something
after that would be useful.

Ross