[mythtv-users] BE3 - Issues with installation and database

Barry Martin barry3martin at gmail.com
Sat May 18 22:30:21 UTC 2019


Hi Folks!


Well, I’m not sure what I did but seems MariaDB is now starting. It’s 
all Bill’s fault: he wrote “Google” and Curious Kitty here got playing 
with the keyboard…. <joke>


Found this site: 
https://stackoverflow.com/questions/40997257/mysql-service-fails-to-start-hangs-up-timeout-ubuntu-mariadb 
OK, similar to my issue. Does suggest turning off apparmor as known bug 
with MySQL previous installed to MariaDB. OK, I don’t make things worse 
so just temporarily turned off apparmor; the system is isolated as the 
Ethernet cable is unplugged.


I had kept a copy of the Terminal session – in the box:



barry at Backend-3:~$ sudo systemctl stop apparmor

[sudo] password for barry:

barry at Backend-3:~$ sudo systemctl disable apparmor

Synchronizing state of apparmor.service with SysV service script with 
/lib/systemd/systemd-sysv-install.

Executing: /lib/systemd/systemd-sysv-install disable apparmor

barry at Backend-3:~$




barry at Backend-3:~$ service --status-all

[ - ] apparmor


/Use the site’s instructions to turn apparmor back on; verify is working/


barry at Backend-3:~$ sudo service mariadb start

<wait a long time....>

Job for mariadb.service failed because a timeout was exceeded.

See "systemctl status mariadb.service" and "journalctl -xe" for details.

barry at Backend-3:~$


So at this point looked I looked at systemctl status mariadb.service – 
it’s off, same as before. The file (in the block, above) has a time 
stamp of 12:32.


I had taken a break, come back to see if could find something 
worthwhile; typed some command to check on things and notice a message 
stating mariadb has been running since approximately 12:30-something. 
The message gives the exact time but I’m rather exited to see something 
positive; insert a thumbdrive to capture but the system locked up. ;(


Now getting this:

barry at Backend-3:~$ systemctl status mariadb.service

● mariadb.service - MariaDB 10.1.38 database server

Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
preset: enabled)

Active: active (running) since Sat 2019-05-18 15:41:17 CDT; 3min 3s ago

Docs: man:mysqld(8)

https://mariadb.com/kb/en/library/systemd/

Process: 1134 ExecStartPost=/bin/sh -c systemctl unset-environment 
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)

Process: 1131 ExecStartPost=/etc/mysql/debian-start (code=exited, 
status=0/SUCCESS)

Process: 903 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] 
&& VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl 
set-environment _WSREP_START_POSITION=$VAR || exit 1 (code

Process: 900 ExecStartPre=/bin/sh -c systemctl unset-environment 
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)

Process: 895 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d 
/var/run/mysqld (code=exited, status=0/SUCCESS)

Main PID: 1005 (mysqld)

Status: "Taking your SQL requests now..."

Tasks: 27 (limit: 4915)

CGroup: /system.slice/mariadb.service

└─1005 /usr/sbin/mysqld


May 18 15:41:10 Backend-3 systemd[1]: Starting MariaDB 10.1.38 database 
server...

May 18 15:41:13 Backend-3 mysqld[1005]: 2019-05-18 15:41:13 
140244898974848 [Note] /usr/sbin/mysqld (mysqld 
10.1.38-MariaDB-0ubuntu0.18.04.2) starting as process 1005 ...

May 18 15:41:17 Backend-3 systemd[1]: Started MariaDB 10.1.38 database 
server.

May 18 15:41:20 Backend-3 /etc/mysql/debian-start[1137]: 
/usr/bin/mysql_upgrade: the '--basedir' option is always ignored

May 18 15:41:20 Backend-3 /etc/mysql/debian-start[1137]: Looking for 
'mysql' as: /usr/bin/mysql

May 18 15:41:20 Backend-3 /etc/mysql/debian-start[1137]: Looking for 
'mysqlcheck' as: /usr/bin/mysqlcheck

May 18 15:41:20 Backend-3 /etc/mysql/debian-start[1137]: This 
installation of MySQL is already upgraded to 10.1.38-MariaDB, use 
--force if you still need to run mysql_upgrade

May 18 15:41:20 Backend-3 /etc/mysql/debian-start[1159]: Checking for 
insecure root accounts.

~


So looks like it/something has started but MythTV (BackendSetup) still 
is not seeing any sign of a Database: “No UPnP backends found”. ...The 
later using the MythTV Backend Setup icon at ‘Show Applications’ and at 
Terminal ‘mythtv-setup’ – what’s the command to enable logging?? --help 
doesn’t display a help screen.


TIA! Hope I didn’t screw something else up!

Barry


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190518/bb01f439/attachment.html>


More information about the mythtv-users mailing list