[mythtv-users] error during upgrade from V30 to V31

[James Abernathy]

On Tue, Mar 24, 2020 at 11:11 AM James Abernathy <jfabernathy at gmail.com>
wrote:

>
>
> On Tue, Mar 24, 2020 at 6:52 AM Jim Abernathy <jfabernathy at gmail.com>
> wrote:
>
>>
>> On 3/23/20 5:55 PM, James Abernathy wrote:
>>
>>
>>
>> On Mon, Mar 23, 2020 at 5:49 PM Bill Meek <keemllib at gmail.com> wrote:
>>
>>> On 3/23/20 4:03 PM, James Abernathy wrote:
>>> > $ sudo mysql -u root mythconverg
>>>
>>> Just change mythconverg to mysql.
>>>
>>> --
>>> Bill
>>>
>> jim at mythbuntu:~$ sudo mysql -u root mysql
>> [sudo] password for jim:
>> Reading table information for completion of table and column names
>> You can turn off this feature to get a quicker startup with -A
>>
>> Welcome to the MariaDB monitor.  Commands end with ; or \g.
>> Your MariaDB connection id is 657
>> Server version: 10.0.36-MariaDB-0ubuntu0.16.04.1 Ubuntu 16.04
>>
>> Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
>>
>> Type 'help;' or '\h' for help. Type '\c' to clear the current input
>> statement.
>>
>> MariaDB [mysql]> SELECT User,Host,plugin,authentication_string FROM user
>> WHERE User='mythtv';
>> +--------+------+--------+-----------------------+
>> | User   | Host | plugin | authentication_string |
>> +--------+------+--------+-----------------------+
>> | mythtv | %    |        |                       |
>> +--------+------+--------+-----------------------+
>> 1 row in set (0.00 sec)
>>
>> MariaDB [mysql]>
>>
>>
>> More information overnight.
>>
>> 1. I used the newly upgraded backend last night to record and watch
>> programs via remote FE's as normal.
>>
>> 2. My custom daily cron job ran at the normal time to check, backup, and
>> optimize the database successfully.
>>
>> 3. Mythfilldatabase ran successfully overnight.
>>
>> 4. Mythweb works correctly.
>>
>> So I'm not sure what didn't work during the upgrade of the packages
>> during dpkg-reconfigure mythtv-database command.
>>
>> I'm pretty sure the error was not related to the message immediately
>> before it. I got the warning about keeping or replacing the cron.weekly job
>> because I didn't have one. I have a daily backup which the upgrade didn't
>> mess with and I did get the backup that mythtv-setup does during it's
>> process.
>>
>> Jim A
>>
>>
>> I checked for an update today and there was one;
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1)
> part of the update console log:
> ...
> Setting up php-mythtv (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.6) ...
> Setting up libasound2-data (1.1.3-5ubuntu0.4) ...
> Setting up mount (2.31.1-0.4ubuntu3.6) ...
> Setting up libasound2:amd64 (1.1.3-5ubuntu0.4) ...
> Setting up uuid-runtime (2.31.1-0.4ubuntu3.6) ...
> Setting up libglib2.0-data (2.56.4-0ubuntu0.18.04.6) ...
> Setting up libmyth-python
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up libmythtv-perl
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up libglib2.0-bin (2.56.4-0ubuntu0.18.04.6) ...
> Setting up libmyth (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythtv-common (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1)
> ...
> Setting up mythweb (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythtv-frontend
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythtv-transcode-utils
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythmusic (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythtv-dbg (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythnews (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythgame (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythtv-database
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Failed to create or modify database (incorrect admin username/password?)
> Try:
> sudo dpkg-reconfigure mythtv-database
> Setting up mythweather (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1)
> ...
> Setting up mytharchive (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1)
> ...
> Setting up mythbrowser (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1)
> ...
> Setting up mythtv-backend
> (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythtv (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1) ...
> Setting up mythplugins (2:31.0+fixes.202003231432.9579662~ubuntu18.04.1)
> ...
> Processing triggers for ureadahead (0.100.0-21) ...
> ureadahead will be reprofiled on next reboot
> Processing triggers for libc-bin (2.27-3ubuntu1) ...
> Processing triggers for systemd (237-3ubuntu10.39) ...
> Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
> Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
> Processing triggers for mime-support (3.60ubuntu1) ...
> jim at mythbuntu:~$ sudo dpkg-reconfigure mythtv-database
> Failed to create or modify database (incorrect admin username/password?)
> Try:
> sudo dpkg-reconfigure mythtv-database
>
> The dpkg-reconfigure mythtv-database popped up a question about will other
> computer use this backend, to which I said yes and it ended without an
> error this time.
>
> So maybe this upgrade issue I had yesterday is fixed and will not return
> the next time mythtv is upgraded.
> Jim A
>
I miss spoke.  It did generate the error.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200324/686b9754/attachment.htm>