[mythtv-users] ugraded to 0.29, cannot connect to backend

Greg Woods greg at gregandeva.net
Sun May 27 14:28:43 UTC 2018


For now at least I am forced to admit defeat, I cannot solve this. I
completely uninstalled all the mythtv packages and reinstalled them, and
the problem persists. I also tried removing all the config.xml files and
recreating one via mythtv-setup, and the problem persists.

As a last-ditch effort before resorting to paying for the Comcrap DVR, I
have these lines from the backend log. I am convinced that the MythSocket
failures here are somehow related to my problem, which almost has to be in
the database since everything else has been wiped and recreated.

2018-05-27 08:12:03.847784 I [2791/2791] CoreContext schemawizard.cpp:120
(Compare) - Current MythTV Schema Version (DBSchemaVer): 13
48
2018-05-27 08:12:03.847924 I [2791/2791] CoreContext mythtranslation.cpp:73
(load) - Loading en_us translation for module mythfronten
d
2018-05-27 08:12:03.847936 I [2791/2791] CoreContext mythsocket.cpp:98
(MythSocket) - MythSocket(279c490:-1): MythSocket(-1, 0x0) cto
r
2018-05-27 08:12:03.848894 I [2791/2798] MythSocketThread(-1)
mythsocket.cpp:666 (ConnectToHostReal) - MythSocket(279c490:-1): IP is
local, using loopback address instead
2018-05-27 08:12:03.848906 I [2791/2798] MythSocketThread(-1)
mythsocket.cpp:670 (ConnectToHostReal) - MythSocket(279c490:-1): attemp
ting connect() to (127.0.0.1:6543)
2018-05-27 08:12:03.849036 E [2791/2798] MythSocketThread(-1)
mythsocket.cpp:698 (ConnectToHostReal) - MythSocket(279c490:-1): Failed
 to connect to (127.0.0.1:6543) Connection refused
2018-05-27 08:12:03.849063 I [2791/2791] CoreContext
referencecounter.cpp:145 (DecrRef) - (0x279c4a0)::DecrRef() -> 0
2018-05-27 08:12:03.849069 I [2791/2791] CoreContext mythsocket.cpp:163
(~MythSocket) - MythSocket(279c490:-1): MythSocket dtor : cb
0x0
2018-05-27 08:12:03.850073 N [2791/2791] CoreContext main_helpers.cpp:601
(run_backend) - MythBackend: Running as a slave backend.

The settings table has one MasterServerIP entry:

| MasterServerIP        | 192.168.1.33 | mongoliad.gregandeva.net   |

This is correct and matches what is in the config.xml files (I have
identical ones in /root/.mythtv/config.xml,
/home/mythtv/.mythtv/config.xml, and /etc/mythtv/config.xml)

<Configuration>
  <LocalHostName>mongoliad.gregandeva.net</LocalHostName>
  <Database>
    <PingHost>1</PingHost>
    <Host>mongoliad.gregandeva.net</Host>
    <UserName>mythtv</UserName>
    <Password>mythtv</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>

I am at a complete loss as to how I can fix this. Perhaps when I get more
energy back I will try completely wiping the database, but of course that
means I would have to recreate all my recording rules and I would lose
access to stored recordings (I know there is a find_orphans script that can
help with that part).

--Greg



On Fri, May 25, 2018 at 6:45 PM jk90090 <jk90090 at gmail.com> wrote:

> Just a thought, did you check your MasterServerIP setting in the
> mythconverg database?
>
>
> mysql -Dmythconverg -umythtv -p
>
> select * from settings where value='MasterServerIP';
>
>
>
> On 5/25/18 5:16 PM, Greg Woods wrote:
> > Some progress but still no joy. It is still starting as a slave
> > backend and the frontend still won't connect.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180527/9a136aba/attachment.html>


More information about the mythtv-users mailing list