[mythtv-users] BE3 - Issues with installation and database
Barry Martin
barry3martin at gmail.com
Thu May 16 23:29:29 UTC 2019
Hi Bill!
A little searching found that the Aliases only get created when the service
is enabled. If it comes enabled already, the links don't exist (my case.)
sudo systemctl stop mariadb && sudo systemctl disable mariadb && sudo systemctl enable mariadb
created the links. Interesting. systemctl status mysql.service mysqld.service mariadb.service
now returns the same thing three times.
The commands and responses posted earlier were what I got. Apparently, at
one time the mysql LSB version in init.d was installed and started mariadb. I had
removed it and its rc?.d links, but when I went to 19.04 they were put back.
On topic: systemctl status mariadb
is all that's required.
Hi Bill!
More or less talking to Stephen about my problem so I’ll mumble
something here. Ran the last command (the ‘on-topic’ one) – I’m
guessing my configuration is off by going to localhost so mariadb is
starting, can’t find something, and shuts down.
I think I also only copied part of the output in a previous response
so here’;s the whole thing:
barry at Backend-3:~$ systemctl status mariadb
● mariadb.service - MariaDB 10.1.38 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
preset:
Active: failed (Result: timeout) since Thu 2019-05-16 16:25:00 CDT;
1h 52min
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1020 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS
$_WSREP_NEW_CLUSTER $_WS
Process: 918 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery
] && VAR=
Process: 914 ExecStartPre=/bin/sh -c systemctl unset-environment
_WSREP_START_
Process: 899 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root
-d /var/run
Main PID: 1020 (code=exited, status=0/SUCCESS)
May 16 16:23:26 Backend-3 systemd[1]: Starting MariaDB 10.1.38
database server..
May 16 16:23:28 Backend-3 mysqld[1020]: 2019-05-16 16:23:28
140267238837376 [Not
May 16 16:24:57 Backend-3 systemd[1]: mariadb.service: Start
operation timed out
May 16 16:25:00 Backend-3 systemd[1]: mariadb.service: Failed with
result 'timeo
May 16 16:25:00 Backend-3 systemd[1]: Failed to start MariaDB
10.1.38 database s
lines 1-16/16 (END)...skipping...
● mariadb.service - MariaDB 10.1.38 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Thu 2019-05-16 16:25:00 CDT;
1h 52min ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1020 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS
$_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited,
status=0/SUCCESS)
Process: 918 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: 914 ExecStartPre=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 899 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root
-d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 1020 (code=exited, status=0/SUCCESS)
May 16 16:23:26 Backend-3 systemd[1]: Starting MariaDB 10.1.38
database server...
May 16 16:23:28 Backend-3 mysqld[1020]: 2019-05-16 16:23:28
140267238837376 [Note] /usr/sbin/mysqld (mysqld
10.1.38-MariaDB-0ubuntu0.18.04.2) starting as process 1020 ...
May 16 16:24:57 Backend-3 systemd[1]: mariadb.service: Start
operation timed out. Terminating.
May 16 16:25:00 Backend-3 systemd[1]: mariadb.service: Failed with
result 'timeout'.
May 16 16:25:00 Backend-3 systemd[1]: Failed to start MariaDB
10.1.38 database server.
~
Thanks again!
Barry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190516/170e84dc/attachment.html>
More information about the mythtv-users
mailing list