← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 546616] Re: mythbackend cannot find mysql.txt after upgrade

 

geoff@mythtv:/etc/mythtv$ ls -l
total 24
-rw-rw---- 1 mythtv mythtv  422 2010-03-24 23:05 config.xml
-rw-rw-r-- 1 mythtv mythtv 1122 2010-03-24 19:36 mysql.txt
-rw-r--r-- 1 root   root   1990 2009-12-21 05:00 mythweb-canned_searches.conf.php
-rw-r--r-- 1 root   root   4732 2009-12-21 05:00 mythweb-config.php
-rw-r--r-- 1 root   root   1110 2009-01-26 11:38 session-settings

geoff@mythtv:/etc/mythtv$ cat config.xml
<Configuration>
  <UPnP>
    <MythFrontend>
      <DefaultBackend>
        <DBHostName>localhost</DBHostName>
        <DBUserName>mythtv</DBUserName>
        <DBPassword>Br9O078H</DBPassword>
        <DBName>mythconverg</DBName>
        <DBPort>0</DBPort>
      </DefaultBackend>
    </MythFrontend>
    <UDN>
      <MediaRenderer>d11d3572-6a68-4795-b247-dbcedd30fb72</MediaRenderer>
    </UDN>
  </UPnP>
</Configuration>

geoff@mythtv:/etc/mythtv$ cat mysql.txt 
DBHostName=localhost

# By default, Myth tries to ping the DB host to see if it exists.
# If your DB host or network doesn't accept pings, set this to no:
#
DBHostPing=no

DBUserName=mythtv
DBName=mythconverg
DBType=QMYSQL3

# Set the following if you want to use something other than this
# machine's real hostname for identifying settings in the database.
# This is useful if your hostname changes often, as otherwise you
# will need to reconfigure mythtv (or futz with the DB) every time.
# TWO HOSTS MUST NOT USE THE SAME VALUE
#
#LocalHostName=my-unique-identifier-goes-here

# If you want your frontend to be able to wake your MySQL server
# using WakeOnLan, have a look at the following settings:
#
#
# The time the frontend waits (in seconds) between reconnect tries.
# This should be the rough time your MySQL server needs for startup
#
#WOLsqlReconnectWaitTime=0
#
#
# This is the number of retries to wake the MySQL server
# until the frontend gives up
#
#WOLsqlConnectRetry=5
#
#
# This is the command executed to wake your MySQL server.
#
#WOLsqlCommand=echo 'WOLsqlServerCommand not set'
DBPassword=Br9O078H
geoff@mythtv:/etc/mythtv$ 


That config.xml schema doesn't look right to me.  Everything in the UPnP
node?

Now, there's an empty config.xml file in $HOME/.mythtv, but I'm not sure
why that would affect the backend at startup.  I assume that mythbackend
does not run as "geoff".  The mysql.txt there is just a symlink to
/etc/mysql.txt, anyway.

-- 
mythbackend cannot find mysql.txt after upgrade
https://bugs.launchpad.net/bugs/546616
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Incomplete

Bug description:
After upgrading to Mythbuntu 10.04 beta, mythbackend doesn't work.

It's unable to connect to the database, because it can't find mysql.txt, I suppose because in the service mythbackend's context, either MYTHCONFDIR is not set, or HOME is not set.  Since I have a correct mysql.txt both in /etc/mythtv/ and in $HOME/.mythtv.

If I start mythbackend by hand in a terminal, it works fine.

It spews this continually:


................................................................................
2010-03-24 21:44:17.606 UPnPautoconf() - No UPnP backends found
2010-03-24 21:44:17.606 No UPnP backends found

No UPnP backends found

Would you like to configure the database connection now? [no]  
[console is not interactive, using default 'no']
2010-03-24 21:44:17.608 Deleting UPnP client...
2010-03-24 21:44:18.218 Failed to init MythContext, exiting.
2010-03-24 21:44:18.344 mythbackend version: trunk [23623] www.mythtv.org
2010-03-24 21:44:18.345 Using runtime prefix = /usr
2010-03-24 21:44:18.345 Using configuration directory = /.mythtv
2010-03-24 21:44:18.345 Unable to read configuration file mysql.txt
2010-03-24 21:44:18.345 Empty LocalHostName.
2010-03-24 21:44:18.346 Using localhost value of mythtv
2010-03-24 21:44:18.352 New DB connection, total: 1
2010-03-24 21:44:18.359 Unable to connect to database!
2010-03-24 21:44:18.359 Driver error was [1/1045]:
QMYSQL: Unable to connect
Database error was:
Access denied for user 'mythtv'@'localhost' (using password: YES)

................................................................................
2010-03-24 21:44:20.917 UPnPautoconf() - No UPnP backends found
2010-03-24 21:44:20.917 No UPnP backends found

No UPnP backends found

Would you like to configure the database connection now? [no]  
[console is not interactive, using default 'no']
2010-03-24 21:44:20.918 Deleting UPnP client...





Follow ups

References