Arch Linux

StrangeGamerHD

Member

Registered: 2017-01-15

Posts: 1

mariadb is not working

What I did:

[root@vmd17339 ~]# systemctl start mysqld
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
[root@vmd17339 ~]# sudo mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
2017-01-15 11:20:01 140456434478592 [Note] /usr/sbin/mysqld (mysqld 10.1.20-MariaDB) starting as process 808 ...
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Using Linux native AIO
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Using SSE crc32 instructions
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-01-15 11:20:01 140456434478592 [Note] InnoDB: Completed initialization of buffer pool
2017-01-15 11:20:01 140456434478592 [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
2017-01-15 11:20:01 140456434478592 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-15 11:20:01 140456434478592 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-15 11:20:01 140456434478592 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-01-15 11:20:01 140456434478592 [ERROR] Aborting

Installation of system tables failed!  Examine the logs in
/var/lib/mysql for more information.

The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:

    shell> /usr/scripts/scripts/mysql_install_db --defaults-file=~/.my.cnf

You can also try to start the mysqld daemon with:

    shell> /usr/sbin/mysqld --skip-grant --general-log &

and use the command line tool /usr/bin/mysql
to connect to the mysql database and look at the grant tables:

    shell> /usr/bin/mysql -u root mysql
    mysql> show tables;

Try 'mysqld --help' if you have problems with paths.  Using
--general-log gives you a log in /var/lib/mysql that may be helpful.

The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-sy … install_db
MariaDB is hosted on launchpad; You can find the latest source and
email lists at http://launchpad.net/maria

Please check all of the above before submitting a bug report
at http://mariadb.org/jira

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: mariadb is not working

Can you post the results of the commands asked for in the second line of the error.

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

cephalicmarble

Member

Registered: 2017-01-25

Posts: 8

Re: mariadb is not working

I get the same error:

Mariadb is regularly borked by 'pacman -Syu', but this time, it even failed to reinitialize...

$ sudo rm -fr /var/mysql/* /var/lib/mysql/* /var/log/mysql/*
$ sudo chown -R mysql:mysql /var/mysql /var/lib/mysql /var/log/mysql
$ sudo bash -c "cd /var/lib ; mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql"
/bin/sh: Symbol `rl_readline_state' has different size in shared object, consider re-linking
Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
2017-01-25 11:33:43 140325861625344 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB) starting as process 23902 ...
2017-01-25 11:33:43 7fa029228e00 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Using Linux native AIO
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Using SSE crc32 instructions
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-25 11:33:43 140325861625344 [Note] InnoDB: Completed initialization of buffer pool
2017-01-25 11:33:43 140325861625344 [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
2017-01-25 11:33:43 140325861625344 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-25 11:33:43 140325861625344 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-25 11:33:43 140325861625344 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-01-25 11:33:43 140325861625344 [ERROR] Aborting

Installation of system tables failed!  Examine the logs in

etc etc

$ pacman -Qi mariadb
Name            : mariadb
Version         : 10.1.21-1

etc etc

Anybody got any good idea what might be going wrong with mysql_install_db / mysqld_safe?

After `journalctl -xe`

-- Unit mariadb.service has begun starting up.
Jan 25 18:08:19 anthrax sh[6216]: /bin/sh: Symbol `rl_readline_state' has different size in shared object, consider re-linking
Jan 25 18:08:19 anthrax sh[6219]: /bin/sh: Symbol `rl_readline_state' has different size in shared object, consider re-linking
Jan 25 18:08:19 anthrax sh[6219]: /bin/sh: Symbol `rl_readline_state' has different size in shared object, consider re-linking
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB) starting as process 6306 ...
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 7f325c5d8e00 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Compressed tables use zlib 1.2.11
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Using Linux native AIO
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Using SSE crc32 instructions
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Initializing buffer pool, size = 16.0M
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] InnoDB: Completed initialization of buffer pool
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [Note] Plugin 'FEEDBACK' is disabled.
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 25 18:08:20 anthrax mysqld[6306]: 2017-01-25 18:08:20 139854274727424 [ERROR] Aborting
Jan 25 18:08:20 anthrax systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 25 18:08:20 anthrax systemd[1]: Failed to start MariaDB database server.

rantanran

Member

From: Germany

Registered: 2014-12-20

Posts: 16

Re: mariadb is not working

I also tried to install mariadb on my system an could not geht the service running.
It was a complete fresh install.

Did you guys get it to work?

stefano

Member

Registered: 2011-04-09

Posts: 258

Re: mariadb is not working

Installation is not working for me either, but the error is different.

After pacman's installation, when I run the initialization command:

sudo mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql

I get the following output with errors on InnoDB:

Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
2017-02-08 15:13:05 140421452647936 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB) starting as process 15323 ...
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Using Linux native AIO
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Using SSE crc32 instructions
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Completed initialization of buffer pool
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-08 15:13:05 140421452647936 [Note] InnoDB: Waiting for purge to start
2017-02-08 15:13:05 140421452647936 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1616757
2017-02-08 15:13:05 140420851930880 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-02-08 15:13:05 7fb66ac4db00 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
2017-02-08 15:13:05 7fb66ac4db00 InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."gtid_slave_pos" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
ERROR: 1136  Column count doesn't match value count at row 1
2017-02-08 15:13:05 140421452647936 [ERROR] Aborting


Installation of system tables failed!  Examine the logs in
/var/lib/mysql for more information.

The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:

    shell> /usr/scripts/scripts/mysql_install_db --defaults-file=~/.my.cnf

You can also try to start the mysqld daemon with:

    shell> /usr/sbin/mysqld --skip-grant --general-log &

and use the command line tool /usr/bin/mysql
to connect to the mysql database and look at the grant tables:

    shell> /usr/bin/mysql -u root mysql
    mysql> show tables;

Try 'mysqld --help' if you have problems with paths.  Using
--general-log gives you a log in /var/lib/mysql that may be helpful.

The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
MariaDB is hosted on launchpad; You can find the latest source and
email lists at http://launchpad.net/maria

Please check all of the above before submitting a bug report
at http://mariadb.org/jira

I looked for logs but could not find any. The mariadb install page (https://mariadb.com/kb/en/mariadb/insta … nstall_db/) says

If mysql_install_db fails, you should examine the logs (*.err files) in the data directory (the one specified with --datadir) for a clue of what went wrong.

However, I could not find any such .err file in the data dir, i.e. /var/lib/mysql

Help is appreciated