[mythtv-users] Mythfrontend will not start

[Jack McGee]

On 08/30/2016 11:28 PM, Bill Meek wrote:
> On 08/30/2016 09:14 PM, Jack McGee wrote:
>> Aug 30 20:53:13 mythuser-ZBOX-ID84 mythfrontend.real: 
>> mythfrontend[8735]: E CoreContext mythdbparams.cpp:39 (IsValid)
>> DBHostName is not set in config.xml
>
> I would start looking at the line above and see why
> /home/mythuser/.mythtv/config.xml doesn't have the
> information needed to access the backend.
>
> This may help: https://www.mythtv.org/wiki/Config.xml#Troubleshooting
>

I changed <Host> from local host to 192.168.0.105, but that did not fix 
the problem.

mythuser at mythuser-ZBOX-ID84:~$ cat /home/mythtv/.mythtv/config.xml
<Configuration>
   <Database>
     <PingHost>1</PingHost>
     <Host>192.168.0.105</Host>
     <UserName>mythtv</UserName>
     <Password>Tj4zOBwM</Password>
     <DatabaseName>mythconverg</DatabaseName>
     <Port>3306</Port>
   </Database>
   <WakeOnLAN>
     <Enabled>0</Enabled>
     <SQLReconnectWaitTime>0</SQLReconnectWaitTime>
     <SQLConnectRetry>5</SQLConnectRetry>
     <Command>echo 'WOLsqlServerCommand not set'</Command>
   </WakeOnLAN>
</Configuration>



> And much like the ping you tried, this is a nice
> independent test:
>
>     nmap -p3306,6543 --reason yourBackendAndDbHost
>
> You expect something like this in the response:
>
> PORT     STATE SERVICE REASON
> 3306/tcp open  mysql   syn-ack
> 6543/tcp open  mythtv  syn-ack
>

This might be a problem:
mythuser at mythuser-ZBOX-ID84:~$ nmap -p3306,6543 --reason 192.168.0.105

Starting Nmap 7.01 ( https://nmap.org ) at 2016-08-31 05:48 CDT
Nmap scan report for 192.168.0.105
Host is up, received syn-ack (0.00067s latency).
PORT     STATE  SERVICE REASON
3306/tcp open   mysql   syn-ack
6543/tcp closed mythtv  conn-refused