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

[Ross Boylan]

I'm running Debian testing in a chroot with the Marillat's
respositories.  I just upgraded from 0.24 to 0.25 today, and can no
longer run mythbackend.  I get the error
# date; /etc/init.d/mythtv-backend start
Sat May 12 14:05:56 PDT 2012
Starting MythTV server: mythbackend .
root at corn:/etc/mythtv#
Cannot login to database?

Would you like to configure the database connection now? [no]
[console is not interactive, using default 'no']

/var/log/mythtv/mythbackend.log has not been touched since the upgrade,
and I don't see much in any logs.

Using mysql command line I am able to login to mythconverg using the
same account and password as in /etc/mythtv/mysql.txt.

Hoping to get more diagnostics I did
# mythbackend --help
running as root.  Immediately mythbackend started using all the CPU it
could and its memory use grew rapidly until the system became entirely
unresponsive.  I got it back many minutes later after several processes
were killed by the out of memory monitor, one was killed after long
non-response, and mythbackend failed with an allocation error.

First, is the backend session run as root likely to have caused any
damage to myth or its database?

Second, how can I got login working again?  It was fine before the
upgrade.

Here are some possibly relevant facts:
1. mysql is running in the chroot and the host system mysql is shut
down.
2. A few days ago the chroot disk filled (from mythtranscode "no more
queue slots" messages) and one of the mysql tables was reported corrupt
when I cleared space and restarted.  myisamchk appeared to have fixed
it.
3. My initial upgrade failed with a message it could not find libicu,
and then the same login failures as shown above.  I installed libicu.
4. I have fiddled with settings trying to get remote access to the
mythbacked.  I did not succeed.
5. Even before the upgrade I got
Error parsing: /var/lib/mythtv/.mythtv/config.xml at line: 1  column: 1
on startup.  That file is empty, though there is a config.xml~ file with
stuff in it.
6. I may have changed the system name after installing myth (though that
change may have preceded the myth install).
7. /var/lib/mythtv/.mythtv/mysql.txt is completely unlike the other
mysql.txt; different password and DBType=QMYSQL3. /var/lib/mythtv is the
home directory for the mythtv user, and the init.d script executes
mythbacked as user mythtv.
8. syslogging from the chroot is going to the host machine.
9. mysql (5.1) was upgraded at the same time as myth. mysql got a bunch
of security fixes, which perhaps could make it harder to access.

Thanks for any help.
Ross Boyan