[mythtv-users] .29 won't connect to backend

[Bill Meek]

On 10/15/2018 06:57 PM, Jack McGee wrote:
> On 10/15/2018 02:04 PM, Jack McGee wrote:
>> I upgraded a 16.04 frontend and 16.04 backend from .28 to .29.
> 
> and this might be helpful:
> 
> mythuser at amethi:/home/mythtv/.mythtv$ cat config.xml
> <Configuration>
>    <LocalHostName>my-unique-identifier-goes-here</LocalHostName>
>    <Database>
>      <PingHost>1</PingHost>
>      <Host>localhost</Host>
>      <UserName>mythtv</UserName>
>      <Password>mythtv</Password>
>      <DatabaseName>mythconverg</DatabaseName>
>      <Port>6543</Port>
>    </Database>
>    <WakeOnLAN>
>      <Enabled>0</Enabled>
>      <SQLReconnectWaitTime>0</SQLReconnectWaitTime>
>      <SQLConnectRetry>5</SQLConnectRetry>
>      <Command>echo 'WOLsqlServerCommand not set'</Command>
>    </WakeOnLAN>
> </Configuration>
> 
> mythuser at mythfrontend1:~$ nmap -p3306,6543 --reason 192.168.1.105
> 
> Starting Nmap 7.01 ( https://nmap.org ) at 2018-10-15 18:20 CDT
> Nmap scan report for 192.168.1.105
> Host is up, received syn-ack (0.00062s latency).
> PORT     STATE  SERVICE REASON
> 3306/tcp open   mysql   syn-ack
> 6543/tcp closed mythtv  conn-refused

<Port> should be 3306. If the backend can't talk to the DB,
then it's no surprise that the backend isn't running. Be
sure that all copies of config.xml are changed (sometimes
links to one in /etc get broken.) Fix it and try again. nmap
is a good tool, so is the backend log.

sudo systemctl start mythtv-backend.service is most likely
what you want to use.

-- 
Bill