[mythtv-users] mythbackend does not have access to mysql.txt after .22 upgrade to .23

[Andrew]

On Sat, May 8, 2010 at 12:14 PM, Nick Morrott <knowledgejunkie at gmail.com>wrote:

> On 8 May 2010 18:03, Andrew <mythtv at heathsworld.com> wrote:
> > On Sat, May 8, 2010 at 10:11 AM, Andrew <mythtv at heathsworld.com> wrote:
> >>
> >> I just upgraded to JYA .23 and now when I start mythfront is tells me it
> >> cannot connect to the database.  What I found is the backend is showing
> the
> >> error below (BE and FE on same machine).  As it turns out, when the
> system
> >> tries to start the back end it gets permission denied when trying to
> access
> >> the database.  Yet if i start it as a user or root using "mythbackend"
> >> command it connects just fine.  Did the configuration file location get
> >> changed or something?  Obviously /.myth doesn't exist and show below.
> >>
> >> Would you like to configure the database connection now? [no]
> >> [console is not interactive, using default 'no']
> >> 2010-05-08 10:04:39.354 Deleting UPnP client...
> >> 2010-05-08 10:04:39.942 Failed to init MythContext, exiting.
> >> 2010-05-08 10:04:40.032 mythbackend version: branches/release-0-23-fixes
> >> [24473] www.mythtv.org
> >> 2010-05-08 10:04:40.032 Using runtime prefix = /usr
> >> 2010-05-08 10:04:40.032 Using configuration directory = /.mythtv
> >> 2010-05-08 10:04:40.033 Unable to read configuration file mysql.txt
> >> 2010-05-08 10:04:40.033 Empty LocalHostName.
> >> 2010-05-08 10:04:40.033 Using localhost value of myth
> >> 2010-05-08 10:04:40.037 New DB connection, total: 1
> >> 2010-05-08 10:04:40.042 Unable to connect to database!
> >> 2010-05-08 10:04:40.043 Driver error was [1/1045]:
> >> QMYSQL: Unable to connect
> >> Database error was:
> >> Access denied for user 'mythtv'@'localhost' (using password: YES)
> >>
> >> To summarize, only using the upscript to start the backend fails.  Any
> >> starting with the mythbackend command from the terminal and it works
> fine.
> >>
> >
> > Oddly enough, ps -aux shows the upscript running as root.
> >
> > root     18020  0.5  0.6 287324 39032 ?        D    11:45   0:00
> > /usr/bin/mythbackend --logfile /var/log/mythtv/mythbackend.log
> >
> > but it cannot access the database.  Why would running it directly from a
> > root terminal work, but the upstart script running as root not work?
> What
> > happened with .23 that may have changed this and what did it change?
>
> It's likely that $HOME is not defined in the upstart script, so it is
> looking in /.mythtv/ instead of /root/.mythtv/ (or wherever your
> config is stored). This issue has similarly reared its head frequently
> when using the older init scripts.
>
> Nick
>
> --
> Nick Morrott
>

Looks like ubuntu has committed to upstart and it's now broken with mythtv.
Using the new upstart method breaks.  I can't seem to find a fix yet.

$ start mythtv-backend
start: Rejected send message, 1 matched rules; type="method_call",
sender=":1.93" (uid=1000 pid=21758 comm="start)
interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)"
requested_reply=0 destination="com.ubuntu.Upstart" (uid=0 pid=1
comm="/sbin/init"))
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100508/0f530814/attachment.htm>