[mythtv-users] mythtv-users Digest, Vol 194, Issue 18

[Stephen Worthington]

On Wed, 15 May 2019 12:42:15 -0500, you wrote:

>
>Hi Bill!
>
>>> Had a thought re: the socket error.? Is it due to having the Ethernet cable to "Backend-3" unplugged? ...
>> Not likely.
>
>OK -- figured might be a potential problem.  LIS to Mike I unplugged to 
>protect myself from the existing system getting clobbered.
>
>
>
>> Make sure the DB server is running:
>>
>>     systemctl status mysql mariadb
>
>We may have found a problem!  Summary as typing vs. copying:
>
>     mariadb .service
>
>     Loaded: loaded
>
>     Active:   failed (result: timeout)
>
>There are four 'Process' lines following which indicate success (they 
>lie! <g>)
>
>
>Ohhh-kayyyy: I don't see anything re: MySql service -- with the command 
>line was sort of expecting two parts.
>
>Maybe not: *service --status-all* only reports mysql (as -, so off), no 
>mariadb.
>
>
>Sort of makes sense as someone posted they are essentially the same to 
>Linux.

If you have MariaDB installed, the mysql.service and mysqld.service
unit files get set up as links to mariadb.service:

root at mypvr:/etc/systemd/system# ll mys*
lrwxrwxrwx 1 root root 35 Oct  6  2018 mysqld.service ->
/lib/systemd/system/mariadb.service
lrwxrwxrwx 1 root root 35 Oct  6  2018 mysql.service ->
/lib/systemd/system/mariadb.service

So if you use the name mysql or mysqld in a systemctl command, you
will actually be referring to mariadb.service.

This is what you should see if MariaDB starts properly:

root at mypvr:/etc/systemd/system# systemctl status mariadb
? mariadb.service - MariaDB 10.1.38 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled;
vendor preset: enabled)
   Active: active (running) since Thu 2019-05-16 02:15:24 NZST; 3h
32min ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 2538 ExecStartPost=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 2530 ExecStartPost=/etc/mysql/debian-start (code=exited,
status=0/SUCCESS)
  Process: 2229 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=exited, st
  Process: 2137 ExecStartPre=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 1865 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root
-d /var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 2489 (mysqld)
   Status: "Taking your SQL requests now..."
    Tasks: 68 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           +-2489 /usr/sbin/mysqld

May 16 02:15:22 mypvr systemd[1]: Starting MariaDB 10.1.38 database
server...
May 16 02:15:23 mypvr mysqld[2489]: 2019-05-16  2:15:23
140682460638336 [Warning] option 'net_buffer_length': unsigned value
8388608 adjusted to 1048576
May 16 02:15:23 mypvr mysqld[2489]: 2019-05-16  2:15:23
140682460638336 [Note] /usr/sbin/mysqld (mysqld
10.1.38-MariaDB-0ubuntu0.18.04.2) starting as process 2489 ...
May 16 02:15:24 mypvr /etc/mysql/debian-start[2541]:
/usr/bin/mysql_upgrade: the '--basedir' option is always ignored
May 16 02:15:24 mypvr /etc/mysql/debian-start[2541]: Looking for
'mysql' as: /usr/bin/mysql
May 16 02:15:24 mypvr /etc/mysql/debian-start[2541]: Looking for
'mysqlcheck' as: /usr/bin/mysqlcheck
May 16 02:15:24 mypvr /etc/mysql/debian-start[2541]: This installation
of MySQL is already upgraded to 10.1.38-MariaDB, use --force if you
still need to run mysql_upgrade
May 16 02:15:24 mypvr /etc/mysql/debian-start[2549]: Checking for
insecure root accounts.
May 16 02:15:24 mypvr systemd[1]: Started MariaDB 10.1.38 database
server.