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

[Tony Lill]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Isn't the big clue on line 3 of the log:

DBHostName is not set in config.xml

My experience is a bit outdated, since I'm still on 0.24, but the code
gets it's database info from config.xml. It then connects to the
database listed there and pulls the IP address of the master backend
from the database.

As for configuring IP addessses, as mentioned before, you should
always use the real IP address for all backends, both master and
slave, and not 127.0.0.1

Once that is done, you can run either mythtv-setup or mythfrontend, I
forget which, on each backend and select which and how many jobs are
run locally. There is also a switch that controls if jobs are to be
run on the recording host or not. I'm not sure if that's a global
option or not.

Some of this might have changed since 0.24 so YMMV

On 01/28/2014 09:02 AM, Michael T. Dean wrote:
> On 01/27/2014 08:43 PM, Drew Tomlinson wrote:
>> 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.
> 
> You're cutting out a lot of the log, so it's hard to figure out 
> exactly what's happening (and where this appeared during the run), 
> but attempting to connect to a local database is a fallback that's 
> performed when there's no config.xml (or an invalid one) and we 
> can't find a master backend on the network from which to get 
> database connection information (or there are multiple and we
> can't ask which).
> 
> You just need to properly configure your backend 
> settings--including "this server" and "master server" IP address 
> information.  You must also ensure that you do not use 127.0.0.1 
> /anywhere/ in your MythTV configuration--including on your master 
> backend.
> 
> See, also, http://www.mythtv.org/wiki/Posting_Logs (and note the 
> "without trimming any information from the log file" part... :)
> 
> Mike _______________________________________________ mythtv-users 
> mailing list mythtv-users at mythtv.org 
> http://www.mythtv.org/mailman/listinfo/mythtv-users

- -- 
Tony Lill, OCT,                    Tony.Lill at AJLC.Waterloo.ON.CA
President, A. J. Lill Consultants                 (519) 650 0660
539 Grand Valley Dr., Cambridge, Ont. N3H 2S2     (519) 241 2461
- --------------- http://www.ajlc.waterloo.on.ca/ ----------------


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLn0gMACgkQGS8yZq1uvxA70wCfSr5ndWvGnKAEw+T24/9Ihpfa
CrYAn1ZomBv40Pj5f+0vLeTFT7Q5X3qI
=Gs/t
-----END PGP SIGNATURE-----