mysql/mariadb failing to start under systemd

If SystemD MariaDB/MySQL is failing to start, make sure your logs directory is set correctly. Sometimes this is caused by failing to correctly make sure the directory is moved.

You’ll see an error log in the journal as follows;

Nov 27 18:24:55 db-a mysqld[28677]: 2017-11-27 18:24:55 140273229838208 [Note] /usr/sbin/mysqld (mysqld 10.2.10-MariaDB-10.2.10+maria~jessie-log) starting as process 28677
Nov 27 18:24:55 db-a systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Nov 27 18:24:55 db-a systemd[1]: Failed to start MariaDB database server.
Nov 27 18:24:55 db-a systemd[1]: Unit mariadb.service entered failed state.

2 thoughts on “mysql/mariadb failing to start under systemd

  1. Waxhead

    I suggest you fix the title which is very misleading.
    How about “mysql/mariadb failing to start UNDER systemd”

    Second please consider spelling systemd the correct way… it is NOT writen SystemD.

  2. Kirrus Post author

    1) fixed
    2) Bleh. Can’t be arsed. Makes me think of System of a Down anyway, which is far better than systemd anyway.

Leave a Reply

Your email address will not be published. Required fields are marked *

cuirie-archiepiscopacy