[mythtv-users] Best Way to Run Commercial Detection Jobs Not On Master Backend

Drew Tomlinson drew at mykitchentable.net
Tue Jan 28 01:43:34 UTC 2014


On 1/27/2014 3:10 PM, Hika van den Hoven wrote:
> Hoi Drew,
>
> This is the backend adres, not the database adres. The top should be
> local 127.0.0.1, the bottom your master IP.
> If you still have problems connecting to mysql, you have to configure
> mysql to not only listen locally on 127.0.0.1
> in /etc/mysql/my.cnf (or where yours is located) on your master
> change bind-address from 127.0.0.1 to 192.168.1.26 and restart mysql.
Thank you for your reply.

I believe my mythconverg database does listen on 192.168.1.26 as I can 
access it remotely using MySQL Workbench and also with a remote frontend 
on my laptop.  In my my.cnf file, I do not specify bind-address which by 
default, binds to all available addresses I think.

 From my mythbackend.log file, I have this snippet.  I don't understand 
it 100% but why is it trying to connect though mysqld.sock?  That seems 
weird to me.  I have no mysqld running (or even installed) on the slave 
backend.  It's a standard mythbuntu "backend only" install.

Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: N 
thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration 
directory = /home/mythtv/.mythtv
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: I CoreContext 
mythcorecontext.cpp:249 (Init) Assumed character encoding: en_US.UTF-8
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: E CoreContext 
mythdbparams.cpp:39 (IsValid) DBHostName is not set in config.xml
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: N CoreContext 
mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: I CoreContext 
mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of 
mythbuntu
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: E CoreContext 
mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: E CoreContext 
mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/2002]:#012QMYSQL: 
Unable to connect#012Database error was:#012Can't connect to local MySQL 
server through socket '/var/run/mysqld/mysqld.sock' (2)
Jan 27 17:34:07 mythbuntu mythbackend: mythbackend[3213]: C CoreContext 
main.cpp:116 (main) Failed to init MythContext.

On 1/27/2014 2:57 PM, Drew Tomlinson wrote:
>>> On 1/27/2014 9:55 AM, Michael T. Dean wrote:
>>>> On 01/27/2014 12:50 PM, Hika van den Hoven wrote:
>>>>> Hoi Drew,
>>>>>
>>>>> There always is just one database, so set it to the ip or hostname
>>>>> of your master! It needs the information in there!
>>>> Exactly.  And the database hostname is allowed to be either a
>>>> hostname or IP address.  It should generally be either localhost or
>>>> 127.0.0.1 on the host that's running the MySQL server instance and
>>>> should be the addressible IP or resolvable hostname of the host
>>>> that's running the MySQL server instance on all other hosts.
>>>>
>>>> Note that the "this server" and "master server" "IP address" settings
>>>> /must/ be IP addresses (not host names) and are talking about
>>>> mythbackend server host (not MySQL server).
>>> Thank you for your replies.  My master backend (and where MySQL is)
>>> has an IP of 192.168.1.26.  My slave is 192.168.1.17.  If I run
>>> mythtv-setup on my slave backend, my only choices for local database
>>> are 192.168.1.17 or 127.0.0.1.  I cannot type directly in the field.
>>> I can only choose one of the two choices.  How do I put 192.168.1.26
>>> in the local database field?  Do I have to edit the MySQL table
>>> directly?  If so, which one?
>>>
>>> I'm running 0.27 on mythbuntu on the slave if that makes any difference.
>> I've put up a picture of my mythtv-setup screen where I can't figure out
>> how to enter 192.168.1.26 in the "local database" field.
>> http://i39.tinypic.com/2ljt8ps.jpg



More information about the mythtv-users mailing list