On 11/22/20 11:57 PM, James Linder wrote: >
>> On 23 Nov 2020, at 1:27 pm, Mike Carron <email@example.com> wrote:
>>>> On 23 Nov 2020, at 11:24 am, Mike Carron <firstname.lastname@example.org> wrote:
>>>> I didn't delete it, just renamed it oldmm.lll It doesn't make any difference, mythfrontend goes directly to the waiting for database screen.
>>>> On 11/22/20 4:53 PM, James Abernathy wrote:
>>>>> On Sun, Nov 22, 2020, 7:26 PM Mike Carron <email@example.com> wrote:
>>>>> My backend host recently failed badly enough that I was not able to salvage anything so I replaced the hardware and installed a new Ubuntu 20.04 and a new v31 mythtv-backend-master with xmltv.
>>>>> I then upgraded a remote frontend (Ubuntu 18.04) from MythTV 30 to 31 but that frontend will not connect to the database.
>>>>> I've checked and rechecked the frontend setup screen and everything is correct. The config.xml files for both look like they should work. I've tried the backend config with </host> = localhost and = 192.168.0.222 (the backend machine IP). The frontend config host is 192.168.0.222.
>>>>> I know the ip addresses are good. I can load 192.168.0.222:6544 into the address line of the Firefox on the frontend machine and it finds the database immediately.
>>>>> I'm no doubt missing something obvious but I can't find it. It seems like I have worn out 2 search engines trying.
>>>>> Have you tried deleting the .mythtv/config.xml file on the FE? Then do a search if the frontend does find it automatically
>>> Mike everyone is talking though gloved hand
>>> From frontend box
>>> $ mysql -u mythtv -pmythtv -h dbbox mythconverg
>>> If you can’t connect then fix this first (watch space after -p)
>>> If you can connect, spelunk the password. The packagers for ubuntu in their infinite stupidity, sorry wisdom, have endowed myth with a bizare password so if you installed a frontend it gets a passord of ‘S0m3s111yrubbish” but the backend has a password of ‘0th3rs11yrubbish”.
>>> the mysql line *needs* to succeed with the passwd mythtv is using. Unless you are living in a share-house with a bunch of holligans use ‘mythtv’ everywhere.
>>> You may have to fiddle with the db. Find a mc.sql to guide you.
>> I can log in to mysql on the backend using mythtv and 'mysillyrubbish'
>> but when I use those same credentials in the database page in the
>> frontend setup they don't work. They do work when I log in to mythtv
>> using the backend address (192.168.0.xxx:6544) from my browser.
>> The mc.sql I found doesn't appear to be useful for my needs.
> Clearly "something" is wrong.
> The reference to mc.sql is on my system the backend talks to the db -h localhost.
> The frontend uses 'mythfrontend.box' or '192.168.0.200' (what ever it was, you did post)
> So from backendBox both -h localhost and -h 'IP' must work. If you use name rather than IP then some sort of DNS needs to be done (/etc/hosts, dnsmasq, bind etc)
> Were it me I'd be spelunking hostname and passwords. For me I took mc.sql and duplcated 'localhost' and '192.168.0.%' (I use 5 not 0) ubuntu uses '%' as the wildcard. That did Not work for me I had to use '192.168.5.%'
> Can you run a frontend on your backend. My backend is headless but nomachine is an easy test. SSH was unusable even for testing (openGL ?)
3 hours ago, the OP was asked to run two commands and reported:
nmap --reason -p 3306 192.168.0.222 produces:
PORT STATE SERVICE REASON
3306/tcp closed mysql reset ttl 64
MAC Address: A8:5E:45:E3:5A:9F (Unknown)
mysql --host=192.168.0.222 --user=mythtv --password=<from config.xml>
ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.0.222' (111
So, it's not a password problem, at least then.
After a suggested bind-address change was done, we
only know that it continues to fail. I haven't seen
the output of the nmap and mysql commands.
mythtv-users mailing list
firstname.lastname@example.org http://lists.mythtv.org/mailman/listinfo/mythtv-users http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org