[mythtv-users] Network affecting standalone mbe/fe?

[Michael T. Dean]

On 08/28/2011 09:22 PM, Robert McNamara wrote:
> On Sun, Aug 28, 2011 at 6:15 PM, Richard Morton wrote:
>> Try hostname.local
>>
>> If your backend is called server then it is server.local this is if you
>> don't have it connected to a domain.
> Bear in mind that using hostnames in for the backend IP values MythTV
> is not supported and will cause breakage.  Stuart Morgan added code in
> master that detects when Myth is attempting to a local interface, and
> uses the loopback, which will avoid exactly the issue being seen here.
>   The code will not be backported, but will be present in .25.
>

Note, however, that using hostnames and/or localhost for the DB Host 
Name (and /only/ the DB Host Name) is fine, even in a mutli-host MythTV 
setup.

I specifically set up my master backend (the host that also runs mysqld) 
config.xml/mysql.txt to use DBHostName of localhost, because a) it will 
always resolve, b) it will allow Qt-MySQL drivers to choose to use the 
significantly-faster Unix-socket-based connections (rather than TCP/IP 
connections), and c) it is completely independent of the network--even 
on a distro whose utilities detect a network's going up or down and 
ripping the IP address out from under every app on the system.

On my remote backend and remote frontend systems, I use the (static) IP 
address of the master backend host for DBHostName because a) if the 
network goes down, it will lose connection to the database, anyway, b) 
using IP address specifically means that if name resolution/DNS goes 
down on my network, it won't have any effect on MythTV/Qt-MySQL's 
ability to use the database.

That said, all master/this backend "IP Address" settings /must/ use 
(static) IP addresses.  Using host names will cause issues, as Robert 
mentioned.  (So, in short, the only place you can use a host name--but 
shouldn't, other than localhost--is config.xml/mysql.txt's DBHostName 
setting.)

Mike