Mailing List Archive: BE4 – Remote Frontends not connecting

BE4 – Remote Frontends not connecting

Jan 7, 2022, 5:20 PM

Post #1 of 3 (283 views)

Hi Folks!

Me again – different problem with a different backend. Actually I was
working on this new BE to replace the old one that had the crash and
database corruption issue.

New system running Ubuntu 20.04 and MythTV version 31.

Two issues:

    Remote Frontends not connecting.

mythfilldatabase/SchedulesDirect not updating (I have seven days’ of data).

Frontend issues:

    Local FE (on the Backend) works

    From a remote computer: Firefox to 192.168.4.4:6544 works (IP of
the Backend)

    Remote Frontends not connecting

Frontend will see on “MythTV Servers” screen

    MythTV AV Media Server (with a ‘91’ under)

    To the right side 31.20200101-1 and an unlocked lock icon

    Pop-up window: “Cannot login to database”

Frontend Database Configuration Screen appears correct:

    Hostname 192.168.4.4 (correct)

    Ping checked

    Port 3306

    Database Name mythconverg

    User mythtv (tried ‘barry’ too!)

    Password (correct)

    Enter Custom Identifier for Frontend Preferences unchecked

    Enter Database Server Wakeup unchecked

Examining Log to Terminal: typed ‘mythfrontend’ on BE4:

    In red (orange-red?) Cannot load libcuda.so.1

Per https://forum.mythtv.org/viewtopic.php?t=3640
<https://forum.mythtv.org/viewtopic.php?t=3640> “[Solved] Remote
frontend won't connect to DB”

> The backend settings in mythtv-setup define where the backend listens.
> A 127..... address would be for a combined FE/BE with no remotes.

==> mythtv-setup ? General ? Host Address Backend Setup ==>

Security PIN 0000

All Connections on all Subnets unchecked

Listen on All IP Addresses checked

Primary IP Address/DNS Name 192.168.4.4

This Server is the Master Backend checked

Last post of the same topic (t=3640, above) says “I had to edit
mythtv.cnf to correct the bind-address from 127.0.0.1 to my ipaddress.
My version was located in /etc/mysql/conf.d”.

Mine just says:

    [mysqld]

#bind-address=:: <== so commented out by default

max_connections=100

FWIW I was creating this Backend on 10.0.x.x network if that makes any
difference/helps find my error.

Thanks again for all the help!

Barry

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

BE4 – Remote Frontends not connecting [ In reply to ]

barry3martin at gmail

Jan 9, 2022, 2:01 PM

Post #2 of 3 (280 views)

Permalink

Hi Folks!

Found the problem as to why the Frontends weren’t connecting to the new
Backend! Found this:

https://forum.mythtv.org/viewtopic.php?t=3923
<https://forum.mythtv.org/viewtopic.php?t=3923> . Scroll down about
two-thirds and found:

<quote>

On the DB server/backend, this is wrong and /should/ have been
correct based on an answer to a question† when the package was
installed:

Code:

|$ cat /etc/mysql/conf.d/mythtv.cnf|
|[mysqld]|
|#bind-address=::|

The # above means comment and that MySQL is only listening on it's own host.
Remove the #. You may need to restart mysql (sudo systemctl restart mysql)

</quote>

Checked on the old working Backend (BE3 – version 3 ) (the one that
crashed – see my earlier post this month) – the bind-address line is
active / not commented. Ahhh!

Uncommented on the new (BE4 – version 31) - restarted mysql – local FE
(on the BE) works! Checked my test Raspberry Pi Frontend - works! Tested
the ‘real’ Frontend downstairs - works! :)

Rebooted the Backend – deep breath! - everybody still working!!

(Now to figure out the SchedulesDirect problem!)

Barry

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: BE4 ? Remote Frontends not connecting [ In reply to ]

stephen_agent at jsw

Jan 10, 2022, 12:21 AM

Post #3 of 3 (279 views)

Permalink

On Sun, 9 Jan 2022 16:01:28 -0600, you wrote:

>
>
>Hi Folks!
>
>
>Found the problem as to why the Frontends weren?t connecting to the new
>Backend! Found this:
>
>https://forum.mythtv.org/viewtopic.php?t=3923
><https://forum.mythtv.org/viewtopic.php?t=3923> . Scroll down about
>two-thirds and found:
>
><quote>
>
>On the DB server/backend, this is wrong and /should/ have been
>correct based on an answer to a question? when the package was
>installed:
>
>Code:
>
>|$ cat /etc/mysql/conf.d/mythtv.cnf|
>|[mysqld]|
>|#bind-address=::|
>
>The # above means comment and that MySQL is only listening on it's own host.
>Remove the #. You may need to restart mysql (sudo systemctl restart mysql)
>
></quote>
>
>
>Checked on the old working Backend (BE3 ? version 3 ) (the one that
>crashed ? see my earlier post this month) ? the bind-address line is
>active / not commented. Ahhh!
>
>
>Uncommented on the new (BE4 ? version 31) - restarted mysql ? local FE
>(on the BE) works! Checked my test Raspberry Pi Frontend - works! Tested
>the ?real? Frontend downstairs - works! :)
>
>Rebooted the Backend ? deep breath! - everybody still working!!
>
>
>(Now to figure out the SchedulesDirect problem!)
>
>Barry

Be aware that if that bind-address line is in one of the .cnf files
installed by the MySQL/MariaDB packages, when that package is updated,
it may be overwritten. The best solution is to leave that line
commented and create your own new .cnf file that will not be
overwritten and will be read last so any option in it will be read
last and will override any option read earlier in other .cnf files. So
a file like:

/etc/mysql/conf.d/zz-local-options.cnf
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org