[mythtv-users] mythbackend not starting on slave (FOUND WHY!)

[Steve Malenfant]

Ok... So I run updatedb and "locate mysql.txt"  Found one in
/.mythtv/mysql.txt.  I'm not sure why the file was there and why it
was set to localhost.  So I've changed that param and it started
working!  PREFIX at atrpms set to "/" ?  I tried to use the MYTHTVDIR
env but it doesn't seems to work.

So, for the debug message I was trying to get, it's there... just
embedded in some code that will never really run.

    if (QDir(m_installprefix).isRelative())
.....
        VERBOSE(VB_ALL, QString("Using runtime prefix = %1")
                                .arg(m_installprefix));

Maybe it would be worthwhile to move to the after the "if" when debug
is enabled.
Maybe an extra VB_ALL message should be put in
MythContextPrivate::LoadDatabaseSettings.

Anyway, I found it, I'm happy now.  Now does WOL work on my machine...

Steve M.

On 1/14/06, Steve Malenfant <smalenfant at gmail.com> wrote:
> From what I can see... It's not even trying to connect to any remote
> database, it's using the mysql.lock file.  The MYTHTV_HOME directory
> is set to /var/lib/mythtv in the init script :
>
> : ${MYTHTV_HOME=/var/lib/mythtv}
>
> So I've put the file /var/lib/mythtv/mysql.txt and
> /var/lib/mythtv/.mythtv/mysql.txt and nothing happened (that's all
> stuff I've tried before writing the first e-mail.
>
> At least when we lunch with the "-v all" options, I woud expect
> mythbackend to print the location of the mysql.txt file.
>
> Seems that all the post I've seen, all the documentation I read point
> to the home directory or the /usr/local/share/mythtv/mysql.txt, which
> I also put /usr/share/mythtv/mysql.txt because my install is not SVN,
> but the one from ATRPMS.
>
> Root is the user being used when starting with "service mythbackend
> start" right?  Or maybe when service is used, the profile are not
> loaded?  Is there anybody in this forum running a slave that's working
> with the "service mythbackend start" script?
>
> I'll check the source tonight to see what's going on, which env it
> looks for and see if I can find out something.  Most of the post I've
> seen don't include their resolution or maybe gave up.
>
> Steve M.
>
> On 1/13/06, Kevin Kuphal <kuphal at dls.net> wrote:
> > Bruce Markey wrote:
> > > Well, the problem is clearly that it is finding a valid mysql.txt
> > > when start from the commandline but not when started in the init
> > > script. This is most likely the $HOME environment variable and not
> > > a lack of reading mythtv docs ;-).
> > >
> > > Root's $HOME may be /root when logged in but may be / during init.
> > > You could "export $HOME=/root" in the script or make a synlink for
> > > /mysql.txt or copy mysql.txt to / or whatever.
> > >
> > Perhaps.  I've been thinking at times it might be nice to have a line in
> > the log for the hostname that hosts the DB that the backend connected to
> > in order to be able to easily determine which machine.  It's hard to say
> > if he is connecting to the master DB or a local DB he has configured
> > tuners on mistakenly.  Or perhaps I could be totally mistaken and not
> > understand the logs in detail :)
> >
> > Kevin
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>