Wednesday, May 12, 2010

Myth 0.23 - Upgrade woes

Last night the new install for MythTV 0.23 came down the pike, and showed up in the software updates.

Ya! I thought, and after a lot of downloading and installing it finally arrived, but myth backend had gone away and would start as a service, but would not connect to the database. The backend would run as a program if it was started from the command prompt.

After a lot of looking at files, the internet, and comparisons against the test machine, I discovered that it couldn't access the mysql.txt file, as it was looking for it in /.mythtv, where it should have been in /home/mythtv/.mythtv.

The offending log entries...

2010-05-13 00:46:22.857 mythbackend version: branches/release-0-23-fixes...
2010-05-13 00:46:23.001 Using runtime prefix = /usr
2010-05-13 00:46:23.061 Using configuration directory = /.mythtv
2010-05-13 00:46:23.133 Unable to read configuration file mysql.txt
2010-05-13 00:46:23.193 Empty LocalHostName.
2010-05-13 00:46:23.258 Using localhost value of mythtv
2010-05-13 00:46:23.323 New DB connection, total: 1
2010-05-13 00:46:23.380 Unable to connect to database!
2010-05-13 00:46:23.435 Driver error was [1/1045]:
QMYSQL: Unable to connect
Database error was:
Access denied for user 'mythtv'@'localhost' (using password: YES)


The FIX...

sudo kate /etc/default/mythtv-backend

Change the ARGS line and add the --user $USER command.

ARGS="--user $USER --logfile /var/log/mythtv/mythbackend.log"

Restart the backend service.

sudo /etc/init.d/mythtv-backend restart

If the same problem still exists check the logs first, to determine the correct directory, then check file permissions, or the contents of the mysql.txt file.

Ya!, now I am a happy camper, off to watch some MythTV!

1 comment:

  1. Thanks! Worked perfectly.....

    Too bad the problem wasn't fixed before it was released!

    ReplyDelete