[mythtv-users] troubles after upgrading mariadb

[Paul Harrison]

On 23/11/2021 18:10, Bill Meek wrote:

> On 11/23/21 12:02 PM, Paul Harrison wrote:
>> On 23/11/2021 17:40, Klaus Becker wrote:
>>
>>>
>>> Am 23/11/2021 um 18:36 schrieb Klaus Becker:
>>>> Am 19/11/2021 um 02:40 schrieb stinga:
>>>>> On 19/11/2021 04:48, Klaus Becker wrote:
>>>>>> Am 18/11/2021 um 21:26 schrieb Klaus Becker:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I use Debian unstable, frontend worked fine for a long time. I only watch german tv.
>>>>>>>
>>>>>>> But recently mariadb changed from 10.5 to 10.6 and I lost my database "mythconverg". I got a message that told me that the db cannot be
>>>>>>> upgraded automatically and that I have to restore it manually. Un fortunately I did not pay attention.
>>>>>>>
>>>>>>> Finally I deleted the new db created by mariadb and created an empty db with the same name "mythconverg".
>>>>>>>
>>>>>>> I backuped my db in september, but since this time, I did not use MythTV very often and the db probably did not change very much since
>>>>>>> that time. I watched and then deleted some recordings, but I have no new recordings since a long time.
>>>>>>>
>>>>>>> So I restored my db  with
>>>>>>> # qmysql -u mythtv -p mythconverg < /home/klaus/mythconverg.sql.
>>>>>>>
>>>>>> Finally I did a channel scan successfully, but it did not change anything.
>>>> Hi again,
>>>>
>>>> I struggled a lot to resolve the problem.
>>>>
>>>> I have a backup of Debian unstable from september. I installed it again on another partition (sda7), and there frontend works. So the DB is ok.
>>>>
>>>> I imported the DB as described in the wiki to my actual system (sda1), and there I have the above problems. I verified the DB with
>>>> mysqlcheck, it is ok.
>>>>
>>>> Then I returned to sda7, I put MythTV and MariaDB on hold and then I performed "apt -dist-upgrade" successfully. I observed that Mysql was
>>>> not upgraded. Afterwards I had again the above problems!
>>>>
>>>> So my problems seem not to come from MythTV or DB, but from Debian unstable.
>>>>
>>>> I might be a port-problem, I explain:
>>>>
>>>> https://www.mythtv.org/wiki/Setup_General says that for v29, the serverport is 6543. I spent some time to make it work on sda, without
>>>> success, no connection to the server which is running, I verified with systemctl.
>>>>
>>>> "Nmap localhost" says "3306/tcp open  mysql". So the right port should be 3306. I used this port since I use MythTV (several years) and it
>>>> still works on sda1, but still with the above problems. Mythtv-setup also says that 3306 is the default port.
>>>>
>>>>
>>>>
>>>> While launching frontend by commandline, I see among others:
>>>>
>>>> 2021-11-23 17:43:31.293788 I  Listening on TCP 0.0.0.0:6547
>>>> 2021-11-23 17:43:31.294481 I  Listening on TCP [::]:6547
>>>>
>>>> 2021-11-23 17:43:35.734683 I  Service registration complete: name 'Mythfrontend on 1stein' type '_mythfrontend._tcp.' domain: 'local.'
>>>> 2021-11-23 17:43:53.271600 I  De-registering service '_mythfrontend._tcp.' on 'Mythfrontend on 1stein'
>>>>
>>>> 2021-11-23 17:43:34.551430 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 127.0.0.1:3306 (try 1 of 1)
>>>> 2021-11-23 17:43:34.594742 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 127.0.0.1:3306 (try 1 of 1)
>>>> 2021-11-23 17:43:34.598809 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 127.0.0.1:3306 (try 1 of 1)
>>>> and so on, very often
>>>>
>>>>
>>>>
>>>> Isn't there confusion between port 3306 and 6547 ?
>>>>
>>>> sincerely
>>>>
>>>> Klaus
>>>
>>> I forgot to say:
>>>
>>> the mythtv-versions on the 2 systems
>>>
>>> sda7: 31.0+fixes20210801.git5824c588db-dmo1 all
>>> sda1: 31.0+fixes20211113.git25f1bb1d12-dmo1 all
>>>
>>>
>> I think you are confusing the default port MariaDB/MySQL listens on 3306 and the default port the backend listens on 6544?
>>
>> There are two different servers involved the DB server and the mythbackend server both on different ports both have to configure properly for a
>> frontend to connect.
>>
>>
>> Paul H.
> You can remove MythTV from the issue with the following,
> replacing user, host and password values with the ones
> in your config.xml file:
>
>    mysql --user=mythtv --host=localhost --password=mythtv mythconverg
>
> If that fails, then mythAnyProgram will fail.
>
> Also, for the frontend, 6547 is the port it listens on, not
> a problem, as Paul said.
>

Fixing this would be a step in right direction and may make everything 
just work :) The port should be 6544 not 3306.

2021-11-23 17:43:34.551430 I MythCoreContext::ConnectCommandSocket(): 
Connecting to backend server: 127.0.0.1:3306 (try 1 of 1)


Paul H.