[mythtv-users] update still generating 1 error.

[Jim Abernathy]

On 3/28/20 8:03 AM, Jim Abernathy wrote:
>
> I updated to 2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1 this 
> morning and I'm still getting the error on setting up mythtv-database. 
> Otherwise the system continues to work fine recording and playing TV 
> programs and updating the EPG.
>
> I can login to mysql with:
>
> sudo mysql --defaults-extra-file=/etc/mysql/debian.cnf
>
> jim at mythbuntu:~$ sudo mysql --defaults-extra-file=/etc/mysql/debian.cnf
> Welcome to the MariaDB monitor.  Commands end with ; or \g.
> Your MariaDB connection id is 918
> 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 [(none)]> quit
> Bye
>
> and the contents of /etc/mysql/debian.cnf is:
>
> # Automatically generated for Debian scripts. DO NOT TOUCH!
> [client]
> host     = localhost
> user     = root
> password =
> socket   = /var/run/mysqld/mysqld.sock
> [mysql_upgrade]
> host     = localhost
> user     = root
> password =
> socket   = /var/run/mysqld/mysqld.sock
> basedir  = /usr
>
> Any help would be appreciated, but keep in mind, I'm no expert on 
> mysql syntax.
>
> The backend in on Ubuntu Server 18.04.4 and is up to date.
>
> jim at mythbuntu:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID:    Ubuntu
> Description:    Ubuntu 18.04.4 LTS
> Release:    18.04
> Codename:    bionic
>
> Kernel:
>
> Linux mythbuntu 4.15.0-88202002241620-generic 
> #0+mediatree+hauppauge-Ubuntu SMP Thu Feb 27 01:05:48 UTC 2020 x86_64 
> x86_64 x86_64 GNU/Linux
>
> Console log below:
>
>
> Setting up mythtv-database 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Failed to create or modify database (incorrect admin username/password?)
> Try:
> sudo dpkg-reconfigure mythtv-database
> Setting up mythtv-backend 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythtv-frontend 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythmusic (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythtv (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythtv-dbg 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythnews (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythgame (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythweather 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mytharchive 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythbrowser 
> (2:31.0+fixes.202003271742.f496eb1~ubuntu18.04.1) ...
> Setting up mythplugins 
> (2:31.0+fixes.202003271742.f496eb1~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:~$
>
> Jim A
>

I just check on another one of my systems that use MySQL Workbench and 
the setup there to get into the database is user='mythtv' and 
password='JebbVE2c', which is the password in my /etc/mythtv/config.xml 
file on the backend.

Could this be the source of the update issue or is this the way it's 
suppose to work on a standard mythtv install?  My original install was 
back in v.29 days on mythbuntu 16.04. Since then I've brought the 
database forward with a backup and then a restore on a new system with a 
fresh OS install and fresh mythtv install.

Jim A



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200328/08f76565/attachment.htm>