On Tue, 14 Nov 2017, SternData wrote:
So, with F26, all was happy. Now, not so much.
# systemctl start mariadb
Job for mariadb.service failed because the control process exited with
error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
[root@sds-desk lib]# systemctl status mariadb.service
● mariadb.service - MariaDB 10.2 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-11-14 16:13:38 CST;
2s ago
Process: 10961 ExecStart=/usr/libexec/mysqld --basedir=/usr
$MYSQLD_OPTS $_WSREP_NEW_CLUSTER (code=exited, status=1/FAILURE)
Process: 10924 ExecStartPre=/usr/libexec/mysql-prepare-db-dir
mariadb.service (code=exited, status=0/SUCCESS)
Process: 10899 ExecStartPre=/usr/libexec/mysql-check-socket
(code=exited, status=0/SUCCESS)
Main PID: 10961 (code=exited, status=1/FAILURE)
Status: "Starting final batch to recover 7 pages from redo log"
Nov 14 16:13:37 sds-desk.local mysql-check-socket[10899]: Socket file
/var/lib/mysql/mysql.sock exists.
Nov 14 16:13:37 sds-desk.local mysql-check-socket[10899]: No process is
using /var/lib/mysql/mysql.sock, which means it is a garbage, so it will
be removed automatically.
Nov 14 16:13:37 sds-desk.local mysql-prepare-db-dir[10924]: Database
MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Nov 14 16:13:37 sds-desk.local mysql-prepare-db-dir[10924]: If this is
not the case, make sure the /var/lib/mysql is empty before running
mysql-prepare-db-dir.
Nov 14 16:13:37 sds-desk.local mysqld[10961]: 2017-11-14 16:13:37
140577406647552 [Note] /usr/libexec/mysqld (mysqld 10.2.9-MariaDB)
starting as process 10961 ...
Nov 14 16:13:37 sds-desk.local mysqld[10961]: 2017-11-14 16:13:37
140577406647552 [Warning] Changed limits: max_open_files: 1024
max_connections: 151 table_cache: 431
Nov 14 16:13:38 sds-desk.local systemd[1]: mariadb.service: Main process
exited, code=exited, status=1/FAILURE
Nov 14 16:13:38 sds-desk.local systemd[1]: Failed to start MariaDB 10.2
database server.
Nov 14 16:13:38 sds-desk.local systemd[1]: mariadb.service: Unit entered
failed state.
Nov 14 16:13:38 sds-desk.local systemd[1]: mariadb.service: Failed with
result 'exit-code'.
Is there anything in the mariadb log file? I also seem to remember that
there is at least one dropped option in 10.2 which might be causing an
error if it is still in your configuration.
Michael Young_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
