MariaDB won't run, neither will mysql_install_db

Sparticuz · 2016-09-28 18:01:07

I can't get MariaDB to start. It was working fine as of a week ago, not sure why it stopped working. I was looking for a log file, but couldn't find one in /var/log. I tried chowning /var/lib/mysql, that didn't work. I tried mysql_install_db, but that just hung, left it overnight and it didn't get anywhere. I finally (did a backup of /var/lib/mysql) and removed the entire package. Made sure /etc/mysql/my.cnf was gone and deleted /var/lib/mysql. So I thought I was starting fresh. Reinstalled MariaDB, but I'm having the same problems, I can't even get mysql_install_db to run.

Purgator · 2016-09-29 08:05:39

What command do you use to run it ? What's the terminal output ?

mrunion · 2016-09-29 14:50:12

Tried "chowning" to what? Why did you try this? What is systemd's status show you when running the mysql/maria service? What do yout system logs and or dmesg say?

Last edited by mrunion (2016-09-29 14:50:36)

Sparticuz · 2016-09-30 12:46:40

mrunion: I followed the directions in the wiki under: https://wiki.archlinux.org/index.php/My … nnot_start for the chown

I was running the systemd service and it fails with

----@---- 08:40:28 ~ $ sudo systemctl status mysqld
● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Wed 2016-09-28 14:06:06 EDT; 1 day 18h ago
  Process: 503 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=kil
  Process: 490 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/mariadb.service

Sep 28 14:04:35 ---- systemd[1]: Starting MariaDB database server...
Sep 28 14:06:06 ---- systemd[1]: mariadb.service: Start-pre operation timed out. Terminating.
Sep 28 14:06:06 ---- systemd[1]: Failed to start MariaDB database server.
Sep 28 14:06:06 ---- systemd[1]: mariadb.service: Unit entered failed state.
Sep 28 14:06:06 ---- systemd[1]: mariadb.service: Failed with result 'timeout'.

I also tried to run it straight via terminal using both sudo mysqld, and sudo mysqld_safe --datadir=/var/lib/mysql. I get no output from either command. Again, I get no system logs in /var/log, and I see nothing relevant in dmesg.

Last edited by Sparticuz (2016-09-30 12:47:16)

Sparticuz · 2016-09-30 13:00:51

mysql_install_db --user=mysql --ldata=/var/lib/mysql/ also just sits there forever

RiJo · 2016-11-10 19:45:23

I just ran into this same issue. It may not be related but you can hopefully use the same strategy to preceed. My root partition was almost full and this was how I found it out: I killed the mysqld process running in the background (using `kill -9 <pid>`). I then started mysqld as the mysql user and got this:

$ sudo -u mysql mysqld --verbose
2016-11-10 20:30:02 139922928782848 [Note] mysqld (mysqld 10.1.19-MariaDB) starting as process 2411 ...
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Using Linux native AIO
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Using SSE crc32 instructions
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Completed initialization of buffer pool
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-10 20:30:03 139922928782848 [Note] InnoDB: Waiting for purge to start
2016-11-10 20:30:03 139922928782848 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 6433777
2016-11-10 20:30:03 139922928782848 [Note] Plugin 'FEEDBACK' is disabled.
2016-11-10 20:30:03 139922335852288 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-11-10 20:30:03 139922928782848 [Warning] mysqld: Disk is full writing './mysql-bin.~rec~' (Errcode: 28 "No space left on device"). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
2016-11-10 20:30:03 139922928782848 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs

Arch Linux

#1 2016-09-28 18:01:07

MariaDB won't run, neither will mysql_install_db

#2 2016-09-29 08:05:39

Re: MariaDB won't run, neither will mysql_install_db

#3 2016-09-29 14:50:12

Re: MariaDB won't run, neither will mysql_install_db

#4 2016-09-30 12:46:40

Re: MariaDB won't run, neither will mysql_install_db

#5 2016-09-30 13:00:51

Re: MariaDB won't run, neither will mysql_install_db

#6 2016-11-10 19:45:23

Re: MariaDB won't run, neither will mysql_install_db

Board footer