Mailing List Archive: MythTV: Users

Re: Configuring a slave server with additional tuners [SOLVED]

Index | Next | Previous | View Threaded

mailinglists at vanhlebarsoftware

Aug 25, 2009, 4:11 PM

Post #1 of 6 (708 views)
Permalink

Re: Configuring a slave server with additional tuners [SOLVED]

On Tuesday 25 August 2009 18:59:47 Jim Stichnoth wrote:
> On Tue, Aug 25, 2009 at 2:41 PM, Eric A.
>
> Boney<mailinglists [at] vanhlebarsoftware> wrote:
> > I am having some issues getting my slave backend to connect to the mysql
> > database on the master backend.
> >
> > Somehow the master sees that the slave has an additional tuner card
> > available, but it doesn't show it as connected. In the logs on the slave
> > I see errors about not being able to connect to the database. I have
> > verified that the ip address is correct, that the password is correct and
> > that the slave backend is actually running.
> >
> > I have looked at the permissions of the "mythtv" user in mysql and it has
> > complete access both locally and with the "%" sign. I do not have MySQL
> > installed on the slave server at all.
> >
> > I looked at the my.cnf configuration file on my master backend and I have
> > tried both commenting and un-commenting the line bind: 192.168.1.xxx out.
> > Neither seems to allow the slave to access the database on the master.
> >
> > I am at a loss currently. If there are other items from either of the
> > logs that might help, please just ask.
> >
> > Thanks,
> >
> > -Eric
>
> Check that you actually have a valid mysql.txt file in the location
> where the backend is looking for it. That location depends on the
> home directory of the user that starts up the backend process. And if
> the backend is started up at boot time, there may not be a user and
> home directory associated. I think I have mysql.txt files set up in
> ~mythtv/.mythtv/mysql.txt, ~root/.mythtv/mysql.txt, and
> /.mythtv/mysql.txt, and possibly other locations. Maybe someone can
> clarify exactly where one should keep these files.
>
> Jim
Ok so I found the issue! one of the stupid mysql.txt files did not have the
actual ip address listed but had localhost instead. Once I changed this to the
actual ip address and restarted the backend, presto! Everything working now.

Thanks again to everyone for the help, but man do we really need to have 4
different locations for such an important configuration file on the backends?
Why isn't there just one location for this file and it be updated from the
mythtv-setup environment?

-Eric

stichnot at gmail

Aug 25, 2009, 6:57 PM

Post #2 of 6 (652 views)
Permalink

Re: Configuring a slave server with additional tuners [SOLVED] [In reply to]

On Tue, Aug 25, 2009 at 4:11 PM, Eric A.
Boney<mailinglists [at] vanhlebarsoftware> wrote:
> Thanks again to everyone for the help, but man do we really need to have 4
> different locations for such an important configuration file on the
> backends? Why isn't there just one location for this file and it be updated
> from the mythtv-setup environment?

Or at the very least, the logs at the default logging level could
detail which mysql.txt files are being consulted.

Jim
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

bderman at gmail

Aug 25, 2009, 7:17 PM

Post #3 of 6 (648 views)
Permalink

Re: Configuring a slave server with additional tuners [SOLVED] [In reply to]

On Aug 25, 2009, at 6:57 PM, Jim Stichnoth wrote:

> On Tue, Aug 25, 2009 at 4:11 PM, Eric A.
> Boney<mailinglists [at] vanhlebarsoftware> wrote:
>> Thanks again to everyone for the help, but man do we really need to
>> have 4
>> different locations for such an important configuration file on the
>> backends? Why isn't there just one location for this file and it be
>> updated
>> from the mythtv-setup environment?
>
> Or at the very least, the logs at the default logging level could
> detail which mysql.txt files are being consulted.

Or get rid of them all and connect via upnp. Only a couple more months
or so until the next version which includes this ability.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Aug 25, 2009, 7:34 PM

Post #4 of 6 (648 views)
Permalink

Re: Configuring a slave server with additional tuners [SOLVED] [In reply to]

On 08/25/2009 10:17 PM, Brad DerManouelian wrote:
> On Aug 25, 2009, at 6:57 PM, Jim Stichnoth wrote:
>> On Tue, Aug 25, 2009 at 4:11 PM, Eric A. Boney wrote:
>>> Thanks again to everyone for the help, but man do we really need to
>>> have 4
>>> different locations for such an important configuration file on the
>>> backends? Why isn't there just one location for this file and it be
>>> updated
>>> from the mythtv-setup environment?
>>
>> Or at the very least, the logs at the default logging level could
>> detail which mysql.txt files are being consulted.
>
> Or get rid of them all and connect via upnp. Only a couple more months
> or so until the next version which includes this ability.

0.21-fixes supports $HOME/.mythtv/config.xml , which is the file that
specifies information that can be used to automatically discover the
master backend using UPnP; however, it does not require
autodiscovery/UPnP connections.

Therefore, your advice (get rid of all mysql.txt files) applies whether
users are on 0.21-fixes or trunk.

The use of mysql.txt was supposed to be deprecated before 0.21 was
release and only config.xml is supposed to exist on any machines. And
config.xml can /only/ exist in $HOME/.mythtv , so there's no need to say
which config.xml is in use.

Unfortunately, the config.xml didn't turn out to provide all the
benefits it was meant to provide (basically because we had to support
legacy apps and scripts) and distros haven't caught up with the change,
yet. So, most users have systems that rely on mysql.txt files for
configuration. And, most distros like to hide the actual mysql.txt file
somewhere where the distro feels config files belong. So, real systems
tend to have a ton of them--only one of which is used, the specific one
either determined by the default order of precedence for the mysql.txt
files specified in MythTV or modified by distro scripts (i.e. that set
HOME to allow using a mysql.txt in some "not-normally-a-home" directory).

With an "ideal" setup, you'd just have a $HOME/.mythtv/config.xml for
every user who runs mythtv applications. If you do remove all mysql.txt
files and set up your system with proper config.xml files, it will
always work, regardless of how your distro set things up,
originally--i.e. even if your distro normally uses mysql.txt files to
configure Myth.

Therefore, I won't go through the order in which locations are searched
to find mysql.txt, as, ideally, you would never use one. (Though if you
decide to use mysql.txt, your best bet is /always/ to make every single
one of them correct as different ones will be used in different contexts.)

Mike "rm mysql.txt and let config.xml sort them out" Dean
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

sonofzev at iinet

Aug 25, 2009, 8:07 PM

Post #5 of 6 (667 views)
Permalink

Re: Configuring a slave server with additional tuners [SOLVED] [In reply to]

>With an "ideal" setup, you'd just have a $HOME/.mythtv/config.xml for
>every user who runs mythtv applications. If you do remove all mysql.txt
>files and set up your system with proper config.xml files, it will
>always work, regardless of how your distro set things up,
>originally--i.e. even if your distro normally uses mysql.txt files to
>configure Myth.
>
>Therefore, I won't go through the order in which locations are searched
>to find mysql.txt, as, ideally, you would never use one. (Though if you
>decide to use mysql.txt, your best bet is /always/ to make every single
>one of them correct as different ones will be used in different contexts.)
>
>Mike "rm mysql.txt and let config.xml sort them out" Dean

Just a warning..
Australian Shepherd users need mysql.txt in the user that shepherd is running as.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Aug 25, 2009, 9:09 PM

Post #6 of 6 (650 views)
Permalink

Re: Configuring a slave server with additional tuners [SOLVED] [In reply to]

On 08/25/2009 11:07 PM, sonofzev wrote:
>> With an "ideal" setup, you'd just have a $HOME/.mythtv/config.xml for
>> every user who runs mythtv applications. If you do remove all mysql.txt
>> files and set up your system with proper config.xml files, it will
>> always work, regardless of how your distro set things up,
>> originally--i.e. even if your distro normally uses mysql.txt files to
>> configure Myth.
>>
>> Therefore, I won't go through the order in which locations are searched
>> to find mysql.txt, as, ideally, you would never use one. (Though if you
>> decide to use mysql.txt, your best bet is /always/ to make every single
>> one of them correct as different ones will be used in different contexts.)
>>
>> Mike "rm mysql.txt and let config.xml sort them out" Dean
>>
> Just a warning..
> Australian Shepherd users need mysql.txt in the user that shepherd is running as.

Would be wonderful if some Australian Shepherd user could have the
script updated to use the config.xml, instead of (or, at least, in
preference to) mysql.txt...

See the Perl bindings or the Python bindings for examples of how to do
so. And updating such legacy scripts to support config.xml instead of
the deprecated mysql.txt also has the huge benefit of a) making the
script simpler (as config.xml can only exist in the one location) and b)
making things easier for the user (as config.xml can only exist in one
location)... :)

Mike

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads