Mailing List Archive

I think I had the process correct. But I have a question about mythconverg
passwords.

Does the restore process change the /etc/mythtv/config.xml password or does
it change the database to the password created on the new backend?

What I did was install Ubuntu 22.10 desktop on the RPI4 with the same
hostname as on the old failed mythtv-backend, then added the mythbuntu
repository for fixes/33. Next I installed mariadb-server and then mythtv.
Once that was completed I ran mythtv-setup and added my user 'jim' to the
mythtv group and then I rebooted.

At this point I copied over all the old recordings and other files, then
did:

mythconverg_restore.pl --drop_database --create_database --filename
mythconverg-?????.sql.gz


I ran mythtv-setup and everything looked good and then I ran
mythfrontend and it worked.

However, I had written down the mythconverg password on the old system
before doing this and the new /etc/mythtv/config.xml passwords are
different. I can only assume mythconverg_restore.pl fixes all of this??

Jim A

On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:


I think I had the process correct. But I have a question about mythconverg
passwords.


Does the restore process change the /etc/mythtv/config.xml password or does
it change the database to the password created on the new backend?


What I did was install Ubuntu 22.10 desktop on the RPI4 with the same
hostname as on the old failed mythtv-backend, then added the mythbuntu
repository for fixes/33. Next I installed mariadb-server and then mythtv.
Once that was completed I ran mythtv-setup and added my user 'jim' to the
mythtv group and then I rebooted.


At this point I copied over all the old recordings and other files, then
did:
mythconverg_restore.pl --drop_database --create_database --filename
mythconverg-?????.sql.gz


I ran mythtv-setup and everything looked good and then I ran mythfrontend
and it worked.


However, I had written down the mythconverg password on the old system
before doing this and the new /etc/mythtv/config.xml passwords are
different. I can only assume mythconverg_restore.pl fixes all of this??


Jim A


mythconverg_restore.pl restores the mythconverg DB. Passwords etc. are
stored in the mysql DB.


l--
Bill

On Thu, Mar 16, 2023 at 10:38?AM Bill Meek <keemllib@gmail.com> wrote:

>
>
> On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:
>
> I think I had the process correct. But I have a question about
> mythconverg passwords.
>
> Does the restore process change the /etc/mythtv/config.xml password or
> does it change the database to the password created on the new backend?
>
> What I did was install Ubuntu 22.10 desktop on the RPI4 with the same
> hostname as on the old failed mythtv-backend, then added the mythbuntu
> repository for fixes/33. Next I installed mariadb-server and then mythtv.
> Once that was completed I ran mythtv-setup and added my user 'jim' to the
> mythtv group and then I rebooted.
>
> At this point I copied over all the old recordings and other files, then
> did:
>
> mythconverg_restore.pl
> --drop_database --create_database --filename
> mythconverg-?????.sql.gz
>
>
> I ran mythtv-setup and everything looked good and then I ran
> mythfrontend and it worked.
>
> However, I had written down the mythconverg password on the old system
> before doing this and the new /etc/mythtv/config.xml passwords are
> different. I can only assume mythconverg_restore.pl fixes all of this??
>
> Jim A
>
>
> mythconverg_restore.pl restores the mythconverg DB. Passwords etc. are
> stored in the mysql DB.
>
> l--
> Bill
> _______________________________________________
>
>
So that may explain why I'm having issues now. I rebooted and now
mythtv-setup and mythfrontend will not connect to the database. How do I
make this work? I really don't care what the database password is. When I
build from source I use mythtv for both user and password. I removed the
comment from /etc/mysql/conf.d/mythtv.cnf bind statement and that's all
except rebooting

Jim A

On Thursday 16 March 2023 10:53:03 AM (-05:00), James Abernathy wrote:






On Thu, Mar 16, 2023 at 10:38?AM Bill Meek <keemllib@gmail.com> wrote:



On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:


I think I had the process correct. But I have a question about mythconverg passwords.


Does the restore process change the /etc/mythtv/config.xml password or does it change the database to the password created on the new backend?


What I did was install Ubuntu 22.10 desktop on the RPI4 with the same hostname as on the old failed mythtv-backend, then added the mythbuntu repository for fixes/33. Next I installed mariadb-server and then mythtv. Once that was completed I ran mythtv-setup and added my user 'jim' to the mythtv group and then I rebooted.


At this point I copied over all the old recordings and other files, then did:
mythconverg_restore.pl
--drop_database --create_database --filename
mythconverg-?????.sql.gz


I ran mythtv-setup and everything looked good and then I ran mythfrontend and it worked.


However, I had written down the mythconverg password on the old system before doing this and the new /etc/mythtv/config.xml passwords are different. I can only assume mythconverg_restore.pl fixes all of this??


Jim A


mythconverg_restore.pl restores the mythconverg DB. Passwords etc. are stored in the mysql DB.


l--
Bill
_______________________________________________




So that may explain why I'm having issues now. I rebooted and now mythtv-setup and mythfrontend will not connect to the database. How do I make this work? I really don't care what the database password is. When I build from source I use mythtv for both user and password. I removed the comment from /etc/mysql/conf.d/mythtv.cnf bind statement and that's all except rebooting


Jim A


I always use the commands here to adjust as required: https://github.com/MythTV/mythtv/blob/master/mythtv/database/mc.sql


Done as the SQL root user. Depends on the distribution, but: sudo mysql mysql works for me.


--
Bill

On Thu, Mar 16, 2023 at 11:20?AM Bill Meek <keemllib@gmail.com> wrote:

> On Thursday 16 March 2023 10:53:03 AM (-05:00), James Abernathy wrote:
>
>
>
> On Thu, Mar 16, 2023 at 10:38?AM Bill Meek <keemllib@gmail.com> wrote:
>
>>
>>
>> On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:
>>
>> I think I had the process correct. But I have a question about
>> mythconverg passwords.
>>
>> Does the restore process change the /etc/mythtv/config.xml password or
>> does it change the database to the password created on the new backend?
>>
>> What I did was install Ubuntu 22.10 desktop on the RPI4 with the same
>> hostname as on the old failed mythtv-backend, then added the mythbuntu
>> repository for fixes/33. Next I installed mariadb-server and then mythtv.
>> Once that was completed I ran mythtv-setup and added my user 'jim' to the
>> mythtv group and then I rebooted.
>>
>> At this point I copied over all the old recordings and other files, then
>> did:
>>
>> mythconverg_restore.pl
>> --drop_database --create_database --filename
>> mythconverg-?????.sql.gz
>>
>>
>> I ran mythtv-setup and everything looked good and then I ran
>> mythfrontend and it worked.
>>
>> However, I had written down the mythconverg password on the old system
>> before doing this and the new /etc/mythtv/config.xml passwords are
>> different. I can only assume mythconverg_restore.pl fixes all of this??
>>
>> Jim A
>>
>>
>> mythconverg_restore.pl restores the mythconverg DB. Passwords etc. are
>> stored in the mysql DB.
>>
>> l--
>> Bill
>> _______________________________________________
>>
>>
> So that may explain why I'm having issues now. I rebooted and now
> mythtv-setup and mythfrontend will not connect to the database. How do I
> make this work? I really don't care what the database password is. When I
> build from source I use mythtv for both user and password. I removed the
> comment from /etc/mysql/conf.d/mythtv.cnf bind statement and that's all
> except rebooting
>
> Jim A
>
>
> I always use the commands here to adjust as required:
> https://github.com/MythTV/mythtv/blob/master/mythtv/database/mc.sql
>
> Done as the SQL root user. Depends on the distribution, but: sudo mysql
> mysql works for me.
>
> --
> Bill
>

I just tried that and all commands worked fine in mariadb mysql but no
success. /etc/mythtv/config.xml password is set to 'mythtv', so I was
hoping this would fix it.
This is what I see in the log:
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: N
thread_unknown mythdirs.cpp:204 (InitializeMythDirs) Using configuration
directory = /home/mythtv/.mythtv
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcorecontext.cpp:261 (Init) Assumed character encoding: en_US.UTF-8
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I LogForward
loggingserver.cpp:219 (SyslogLogger) Added syslogging
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:584 (LoadDatabaseSettings) Empty LocalHostName. This is
typical.
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:635 (LoadDatabaseSettings) Using a profile name of:
'den-pc' (Usually the same as this host's name.)
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 0, status dbAwake, Delay: 2000
Mar 16 11:25:52 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 1, status dbAwake, Delay: 2000
Mar 16 11:26:24 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 2, status dbAwake, Delay: 2000
Mar 16 11:26:29 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 3, status dbAwake, Delay: 2000
Mar 16 11:26:34 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 4, status dbAwake, Delay: 2000
Mar 16 11:26:39 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 5, status dbAwake, Delay: 2000
Mar 16 11:26:44 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 6, status dbAwake, Delay: 2000
Mar 16 11:26:49 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 7, status dbAwake, Delay: 2000
Mar 16 11:26:54 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 8, status dbAwake, Delay: 2000
Mar 16 11:26:59 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 9, status dbAwake, Delay: 2000
Mar 16 11:27:04 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
localhost, BE , attempt 10, status dbAwake, Delay: 2000
Mar 16 11:27:09 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:1000 (TestDBconnection) Start up failure. host localhost,
status dbAwakeFail
Mar 16 11:27:10 den-pc mythbackend[2290]: Cannot login to database
Mar 16 11:27:10 den-pc mythbackend[2290]: Would you like to configure the
database connection now? [no]
Mar 16 11:27:10 den-pc mythbackend[2290]: [console is not interactive,
using default 'no']
Mar 16 11:27:10 den-pc mythbackend[2290]: mythbackend[2290]: C CoreContext
mythbackend.cpp:134 (main) Failed to init MythContext.
Mar 16 11:27:11 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
mythcontext.cpp:1684 (~MythContext) Exiting
Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Main process
exited, code=exited, status=130/n/a
Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Failed with
result 'exit-code'.

On 16/03/2023 16:32, James Abernathy wrote:
> On Thu, Mar 16, 2023 at 11:20?AM Bill Meek <keemllib@gmail.com> wrote:
>
>> On Thursday 16 March 2023 10:53:03 AM (-05:00), James Abernathy wrote:
>>
>>
>>
>> On Thu, Mar 16, 2023 at 10:38?AM Bill Meek <keemllib@gmail.com> wrote:
>>
>>>
>>>
>>> On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:
>>>
>>> I think I had the process correct. But I have a question about
>>> mythconverg passwords.
>>>
>>> Does the restore process change the /etc/mythtv/config.xml password or
>>> does it change the database to the password created on the new backend?
>>>
>>> What I did was install Ubuntu 22.10 desktop on the RPI4 with the same
>>> hostname as on the old failed mythtv-backend, then added the mythbuntu
>>> repository for fixes/33. Next I installed mariadb-server and then mythtv.
>>> Once that was completed I ran mythtv-setup and added my user 'jim' to the
>>> mythtv group and then I rebooted.
>>>
>>> At this point I copied over all the old recordings and other files, then
>>> did:
>>>
>>> mythconverg_restore.pl
>>> --drop_database --create_database --filename
>>> mythconverg-?????.sql.gz
>>>
>>>
>>> I ran mythtv-setup and everything looked good and then I ran
>>> mythfrontend and it worked.
>>>
>>> However, I had written down the mythconverg password on the old system
>>> before doing this and the new /etc/mythtv/config.xml passwords are
>>> different. I can only assume mythconverg_restore.pl fixes all of this??
>>>
>>> Jim A
>>>
>>>
>>> mythconverg_restore.pl restores the mythconverg DB. Passwords etc. are
>>> stored in the mysql DB.
>>>
>>> l--
>>> Bill
>>> _______________________________________________
>>>
>>>
>> So that may explain why I'm having issues now. I rebooted and now
>> mythtv-setup and mythfrontend will not connect to the database. How do I
>> make this work? I really don't care what the database password is. When I
>> build from source I use mythtv for both user and password. I removed the
>> comment from /etc/mysql/conf.d/mythtv.cnf bind statement and that's all
>> except rebooting
>>
>> Jim A
>>
>>
>> I always use the commands here to adjust as required:
>> https://github.com/MythTV/mythtv/blob/master/mythtv/database/mc.sql
>>
>> Done as the SQL root user. Depends on the distribution, but: sudo mysql
>> mysql works for me.
>>
>> --
>> Bill
>>
>
> I just tried that and all commands worked fine in mariadb mysql but no
> success. /etc/mythtv/config.xml password is set to 'mythtv', so I was
> hoping this would fix it.
> This is what I see in the log:
> Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: N
> thread_unknown mythdirs.cpp:204 (InitializeMythDirs) Using configuration
> directory = /home/mythtv/.mythtv
> Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcorecontext.cpp:261 (Init) Assumed character encoding: en_US.UTF-8
> Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I LogForward
> loggingserver.cpp:219 (SyslogLogger) Added syslogging
> Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:584 (LoadDatabaseSettings) Empty LocalHostName. This is
> typical.
> Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:635 (LoadDatabaseSettings) Using a profile name of:
> 'den-pc' (Usually the same as this host's name.)
> Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 0, status dbAwake, Delay: 2000
> Mar 16 11:25:52 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 1, status dbAwake, Delay: 2000
> Mar 16 11:26:24 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 2, status dbAwake, Delay: 2000
> Mar 16 11:26:29 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 3, status dbAwake, Delay: 2000
> Mar 16 11:26:34 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 4, status dbAwake, Delay: 2000
> Mar 16 11:26:39 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 5, status dbAwake, Delay: 2000
> Mar 16 11:26:44 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 6, status dbAwake, Delay: 2000
> Mar 16 11:26:49 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 7, status dbAwake, Delay: 2000
> Mar 16 11:26:54 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 8, status dbAwake, Delay: 2000
> Mar 16 11:26:59 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 9, status dbAwake, Delay: 2000
> Mar 16 11:27:04 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> localhost, BE , attempt 10, status dbAwake, Delay: 2000
> Mar 16 11:27:09 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:1000 (TestDBconnection) Start up failure. host localhost,
> status dbAwakeFail
> Mar 16 11:27:10 den-pc mythbackend[2290]: Cannot login to database
> Mar 16 11:27:10 den-pc mythbackend[2290]: Would you like to configure the
> database connection now? [no]
> Mar 16 11:27:10 den-pc mythbackend[2290]: [console is not interactive,
> using default 'no']
> Mar 16 11:27:10 den-pc mythbackend[2290]: mythbackend[2290]: C CoreContext
> mythbackend.cpp:134 (main) Failed to init MythContext.
> Mar 16 11:27:11 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext
> mythcontext.cpp:1684 (~MythContext) Exiting
> Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Main process
> exited, code=exited, status=130/n/a
> Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Failed with
> result 'exit-code'.
>
This isn't a password failure, it looks like it isn't finding the db at all.

Check your mysql/mariadb configs, remembering that if you have mariadb, then the config files may
have slightly different names and override the default mysql ones!

--

Mike Perkins


_______________________________________________
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

On Thursday 16 March 2023 11:32:33 AM (-05:00), James Abernathy wrote:






On Thu, Mar 16, 2023 at 11:20?AM Bill Meek <keemllib@gmail.com> wrote:

On Thursday 16 March 2023 10:53:03 AM (-05:00), James Abernathy wrote:






On Thu, Mar 16, 2023 at 10:38?AM Bill Meek <keemllib@gmail.com> wrote:



On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:


I think I had the process correct. But I have a question about mythconverg passwords.


Does the restore process change the /etc/mythtv/config.xml password or does it change the database to the password created on the new backend?


What I did was install Ubuntu 22.10 desktop on the RPI4 with the same hostname as on the old failed mythtv-backend, then added the mythbuntu repository for fixes/33. Next I installed mariadb-server and then mythtv. Once that was completed I ran mythtv-setup and added my user 'jim' to the mythtv group and then I rebooted.


At this point I copied over all the old recordings and other files, then did:
mythconverg_restore.pl
--drop_database --create_database --filename
mythconverg-?????.sql.gz


I ran mythtv-setup and everything looked good and then I ran mythfrontend and it worked.


However, I had written down the mythconverg password on the old system before doing this and the new /etc/mythtv/config.xml passwords are different. I can only assume mythconverg_restore.pl fixes all of this??


Jim A


mythconverg_restore.pl restores the mythconverg DB. Passwords etc. are stored in the mysql DB.


l--
Bill
_______________________________________________




So that may explain why I'm having issues now. I rebooted and now mythtv-setup and mythfrontend will not connect to the database. How do I make this work? I really don't care what the database password is. When I build from source I use mythtv for both user and password. I removed the comment from /etc/mysql/conf.d/mythtv.cnf bind statement and that's all except rebooting


Jim A


I always use the commands here to adjust as required: https://github.com/MythTV/mythtv/blob/master/mythtv/database/mc.sql


Done as the SQL root user. Depends on the distribution, but: sudo mysql mysql works for me.


--
Bill


I just tried that and all commands worked fine in mariadb mysql but no success. /etc/mythtv/config.xml password is set to 'mythtv', so I was hoping this would fix it.
This is what I see in the log:
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: N thread_unknown mythdirs.cpp:204 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcorecontext.cpp:261 (Init) Assumed character encoding: en_US.UTF-8
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I LogForward loggingserver.cpp:219 (SyslogLogger) Added syslogging
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:584 (LoadDatabaseSettings) Empty LocalHostName. This is typical.
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:635 (LoadDatabaseSettings) Using a profile name of: 'den-pc' (Usually the same as this host's name.)
Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 0, status dbAwake, Delay: 2000
Mar 16 11:25:52 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 1, status dbAwake, Delay: 2000
Mar 16 11:26:24 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 2, status dbAwake, Delay: 2000
Mar 16 11:26:29 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 3, status dbAwake, Delay: 2000
Mar 16 11:26:34 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 4, status dbAwake, Delay: 2000
Mar 16 11:26:39 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 5, status dbAwake, Delay: 2000
Mar 16 11:26:44 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 6, status dbAwake, Delay: 2000
Mar 16 11:26:49 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 7, status dbAwake, Delay: 2000
Mar 16 11:26:54 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 8, status dbAwake, Delay: 2000
Mar 16 11:26:59 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 9, status dbAwake, Delay: 2000
Mar 16 11:27:04 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB localhost, BE , attempt 10, status dbAwake, Delay: 2000
Mar 16 11:27:09 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:1000 (TestDBconnection) Start up failure. host localhost, status dbAwakeFail
Mar 16 11:27:10 den-pc mythbackend[2290]: Cannot login to database
Mar 16 11:27:10 den-pc mythbackend[2290]: Would you like to configure the database connection now? [no]
Mar 16 11:27:10 den-pc mythbackend[2290]: [console is not interactive, using default 'no']
Mar 16 11:27:10 den-pc mythbackend[2290]: mythbackend[2290]: C CoreContext mythbackend.cpp:134 (main) Failed to init MythContext.
Mar 16 11:27:11 den-pc mythbackend[2290]: mythbackend[2290]: I CoreContext mythcontext.cpp:1684 (~MythContext) Exiting
Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Main process exited, code=exited, status=130/n/a
Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Failed with result 'exit-code'.



Take MythTV out of the picture and get this to work:


mysql --user=mythtv --password=mythtv --host=localhost mythconverg


Adjust the above with the correct password and host. I assume: systemctl status mysql.service
shows that the DB is running.

--
Bill

On Thu, Mar 16, 2023 at 11:46?AM Mike Perkins <mikep@randomtraveller.org.uk>
wrote:

> On 16/03/2023 16:32, James Abernathy wrote:
> > On Thu, Mar 16, 2023 at 11:20?AM Bill Meek <keemllib@gmail.com> wrote:
> >
> >> On Thursday 16 March 2023 10:53:03 AM (-05:00), James Abernathy wrote:
> >>
> >>
> >>
> >> On Thu, Mar 16, 2023 at 10:38?AM Bill Meek <keemllib@gmail.com> wrote:
> >>
> >>>
> >>>
> >>> On Thursday 16 March 2023 10:14:55 AM (-05:00), James Abernathy wrote:
> >>>
> >>> I think I had the process correct. But I have a question about
> >>> mythconverg passwords.
> >>>
> >>> Does the restore process change the /etc/mythtv/config.xml password or
> >>> does it change the database to the password created on the new backend?
> >>>
> >>> What I did was install Ubuntu 22.10 desktop on the RPI4 with the same
> >>> hostname as on the old failed mythtv-backend, then added the mythbuntu
> >>> repository for fixes/33. Next I installed mariadb-server and then
> mythtv.
> >>> Once that was completed I ran mythtv-setup and added my user 'jim' to
> the
> >>> mythtv group and then I rebooted.
> >>>
> >>> At this point I copied over all the old recordings and other files,
> then
> >>> did:
> >>>
> >>> mythconverg_restore.pl
> >>> --drop_database --create_database --filename
> >>> mythconverg-?????.sql.gz
> >>>
> >>>
> >>> I ran mythtv-setup and everything looked good and then I ran
> >>> mythfrontend and it worked.
> >>>
> >>> However, I had written down the mythconverg password on the old system
> >>> before doing this and the new /etc/mythtv/config.xml passwords are
> >>> different. I can only assume mythconverg_restore.pl fixes all of
> this??
> >>>
> >>> Jim A
> >>>
> >>>
> >>> mythconverg_restore.pl restores the mythconverg DB. Passwords etc.
> are
> >>> stored in the mysql DB.
> >>>
> >>> l--
> >>> Bill
> >>> _______________________________________________
> >>>
> >>>
> >> So that may explain why I'm having issues now. I rebooted and now
> >> mythtv-setup and mythfrontend will not connect to the database. How do
> I
> >> make this work? I really don't care what the database password is.
> When I
> >> build from source I use mythtv for both user and password. I removed
> the
> >> comment from /etc/mysql/conf.d/mythtv.cnf bind statement and that's all
> >> except rebooting
> >>
> >> Jim A
> >>
> >>
> >> I always use the commands here to adjust as required:
> >> https://github.com/MythTV/mythtv/blob/master/mythtv/database/mc.sql
> >>
> >> Done as the SQL root user. Depends on the distribution, but: sudo mysql
> >> mysql works for me.
> >>
> >> --
> >> Bill
> >>
> >
> > I just tried that and all commands worked fine in mariadb mysql but no
> > success. /etc/mythtv/config.xml password is set to 'mythtv', so I was
> > hoping this would fix it.
> > This is what I see in the log:
> > Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: N
> > thread_unknown mythdirs.cpp:204 (InitializeMythDirs) Using configuration
> > directory = /home/mythtv/.mythtv
> > Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcorecontext.cpp:261 (Init) Assumed character encoding: en_US.UTF-8
> > Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I LogForward
> > loggingserver.cpp:219 (SyslogLogger) Added syslogging
> > Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:584 (LoadDatabaseSettings) Empty LocalHostName. This is
> > typical.
> > Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:635 (LoadDatabaseSettings) Using a profile name of:
> > 'den-pc' (Usually the same as this host's name.)
> > Mar 16 11:25:51 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 0, status dbAwake, Delay: 2000
> > Mar 16 11:25:52 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 1, status dbAwake, Delay: 2000
> > Mar 16 11:26:24 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 2, status dbAwake, Delay: 2000
> > Mar 16 11:26:29 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 3, status dbAwake, Delay: 2000
> > Mar 16 11:26:34 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 4, status dbAwake, Delay: 2000
> > Mar 16 11:26:39 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 5, status dbAwake, Delay: 2000
> > Mar 16 11:26:44 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 6, status dbAwake, Delay: 2000
> > Mar 16 11:26:49 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 7, status dbAwake, Delay: 2000
> > Mar 16 11:26:54 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 8, status dbAwake, Delay: 2000
> > Mar 16 11:26:59 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 9, status dbAwake, Delay: 2000
> > Mar 16 11:27:04 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:872 (TestDBconnection) Start up testing connections. DB
> > localhost, BE , attempt 10, status dbAwake, Delay: 2000
> > Mar 16 11:27:09 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:1000 (TestDBconnection) Start up failure. host localhost,
> > status dbAwakeFail
> > Mar 16 11:27:10 den-pc mythbackend[2290]: Cannot login to database
> > Mar 16 11:27:10 den-pc mythbackend[2290]: Would you like to configure the
> > database connection now? [no]
> > Mar 16 11:27:10 den-pc mythbackend[2290]: [console is not interactive,
> > using default 'no']
> > Mar 16 11:27:10 den-pc mythbackend[2290]: mythbackend[2290]: C
> CoreContext
> > mythbackend.cpp:134 (main) Failed to init MythContext.
> > Mar 16 11:27:11 den-pc mythbackend[2290]: mythbackend[2290]: I
> CoreContext
> > mythcontext.cpp:1684 (~MythContext) Exiting
> > Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Main process
> > exited, code=exited, status=130/n/a
> > Mar 16 11:27:11 den-pc systemd[1]: mythtv-backend.service: Failed with
> > result 'exit-code'.
> >
> This isn't a password failure, it looks like it isn't finding the db at
> all.
>
> Check your mysql/mariadb configs, remembering that if you have mariadb,
> then the config files may
> have slightly different names and override the default mysql ones!
>
> --
>
> Mike Perkins
>
>
Thanks Mike, that was it. I restored my changes in /etc/mysql to original
and the backend and frontend are working on localhost. I just need to find
the changes for mariadb to allow remote frontends to work. Bonus is I now
have mythtv as my password for mythconverg. I really hate all the random
password issues with the Ubuntu install. It's not like my Ubuntu backend
is storing nuclear launch codes. :-)

jim A

On 2023-03-16 16:59, James Abernathy wrote:

> Thanks Mike, that was it. I restored my changes in /etc/mysql to
> original and the backend and frontend are working on localhost. I just
> need to find the changes for mariadb to allow remote frontends to work.
> Bonus is I now have mythtv as my password for mythconverg. I really
> hate all the random password issues with the Ubuntu install. It's not
> like my Ubuntu backend is storing nuclear launch codes. :-)

But it is storing all your treasured recorded TV, ripped DVD and Bluray
discs, photos and CDs. Be a shame if some hacker decided to delete them
all for fun.

Just make sure you don't have mythweb or the mythbackend web service
accessible from the internet. Or pick a password you don't announce on
the internet.
Cheers,
Tim.

On Thu, Mar 16, 2023 at 12:15?PM TimP <mythtv@corky.co> wrote:

> On 2023-03-16 16:59, James Abernathy wrote:
>
> Thanks Mike, that was it. I restored my changes in /etc/mysql to original
> and the backend and frontend are working on localhost. I just need to find
> the changes for mariadb to allow remote frontends to work. Bonus is I now
> have mythtv as my password for mythconverg. I really hate all the random
> password issues with the Ubuntu install. It's not like my Ubuntu backend
> is storing nuclear launch codes. :-)
>
>
> But it is storing all your treasured recorded TV, ripped DVD and Bluray
> discs, photos and CDs. Be a shame if some hacker decided to delete them all
> for fun.
> Just make sure you don't have mythweb or the mythbackend web service
> accessible from the internet. Or pick a password you don't announce on the
> internet.
> Cheers,
> Tim.
>

I think the hackers would have to break OpenVPN. besides I have lots of
backends local and offline, cloud and encrypted,

Jim A

On Thu, 16 Mar 2023 11:59:32 -0500, you wrote:

>Thanks Mike, that was it. I restored my changes in /etc/mysql to original
>and the backend and frontend are working on localhost. I just need to find
>the changes for mariadb to allow remote frontends to work.

Fairly recently there were changes to what the * and :: addresses do
in the bind_address= config line. With current MariaDB versions, you
need to use * instead of :: to allow all access (including IPv6) to
MariaDB. So do this:

sudo su
cd /etc/mysql
grep -ir bind-address *

to find all the places you have bind-address set. Then comment them
all out by adding a # at the start of the each of the bind-address
lines. Add a new file by running these commands:

cat <<EOF >/etc/mysql/conf.d/zz-local-options.cnf
[mysqld]
bind-address=*
EOF

Then restart MariaDB:

systemctl restart mariadb
exit

Putting the bind-address line in a separate file ensures that it will
be there forever and not get overwritten by updates of the MariaDB
packages. You may already have such a separate file - if so, you can
just put the bind-address line there.
_______________________________________________
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

> On 17 Mar 2023, at 1:13 am, TimP <mythtv@corky.co> wrote:
>
>> Thanks Mike, that was it. I restored my changes in /etc/mysql to original and the backend and frontend are working on localhost. I just need to find the changes for mariadb to allow remote frontends to work. Bonus is I now have mythtv as my password for mythconverg. I really hate all the random password issues with the Ubuntu install. It's not like my Ubuntu backend is storing nuclear launch codes. :-)
>>
> But it is storing all your treasured recorded TV, ripped DVD and Bluray discs, photos and CDs. Be a shame if some hacker decided to delete them all for fun.
> Just make sure you don't have mythweb or the mythbackend web service accessible from the internet. Or pick a password you don't announce on the internet.

Tim is this the reason for the assine “You shalt not …” from the ubuntu/debian devs …
Lets see:
The hackers teleport into my lounge … no
Every Forwarder on route from them to me is broken and routes a private address (RFC) and my router firmware is broken/hacked to allow them to portforward either maria or ssh port .. no
I know: my wife hacks my myth

Our illustrious premier accidently left his mike on and muttered to a collegue “king storm in a teacup if you ask me”

likewise the paranoia about mythconverg password
James


_______________________________________________
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