Mariadb/mysqld won't start after today's update

benzene · July 2, 2015, 11:49pm

Trying to execute mysqld I get this:


-- Unit mysql.service has begun starting up.
Jul 02 23:35:42 unix mysql-systemd-helper[19697]: Waiting for MySQL to start
Jul 02 23:35:42 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:42 139840518174592 [Note] Using unique option prefix 'group' is error-prone and can break in the future. Please use the full name 'group_concat
Jul 02 23:35:42 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:42 139840518174592 [Warning] option 'group_concat_max_len': unsigned value 0 adjusted to 4
Jul 02 23:35:42 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:42 139840518174592 [Note] /usr/sbin/mysqld (mysqld 10.1.5-MariaDB) starting as process 19716 ...
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: The InnoDB memory heap is disabled
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Memory barrier is not used
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Compressed tables use zlib 1.2.8
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Using Linux native AIO
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Not using CPU crc32 instructions
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Completed initialization of buffer pool
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Highest supported file format is Barracuda.
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: 128 rollback segment(s) are active.
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Waiting for purge to start
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.23-72.1 started; log sequence number 1617389
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139839827576576 [Note] InnoDB: not started
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] Plugin 'FEEDBACK' is disabled.
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: /usr/sbin/mysqld: Too many arguments (first extra is 'NAMES').
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [ERROR] Aborting
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139839810791168 [Note] InnoDB: FTS optimize thread exiting.
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Starting shutdown...
Jul 02 23:35:45 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:45 139840518174592 [Note] InnoDB: Shutdown completed; log sequence number 1617399
Jul 02 23:35:45 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:45 139840518174592 [Note] /usr/sbin/mysqld: Shutdown complete
Jul 02 23:35:45 unix systemd[1]: mysql.service: main process exited, code=exited, status=1/FAILURE
Jul 02 23:36:44 unix mysql-systemd-helper[19697]: MySQL is still dead
Jul 02 23:36:44 unix systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 02 23:36:44 unix systemd[1]: Failed to start MySQL server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has failed.
-- 
-- The result is failed.
Jul 02 23:36:44 unix systemd[1]: Unit mysql.service entered failed state.
Jul 02 23:36:44 unix systemd[1]: mysql.service failed.
Jul 02 23:36:44 unix unknown[1]: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mysql comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 02 23:36:44 unix polkitd[909]: Unregistered Authentication Agent for unix-process:19667:1448920 (system bus name :1.173, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (dis

And running systemctl status mysql.service I get this:

● mysql.service - MySQL server
   Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-07-02 23:36:44 CEST; 5min ago
  Process: 19697 ExecStartPost=/usr/lib/mysql/mysql-systemd-helper wait default (code=exited, status=1/FAILURE)
  Process: 19695 ExecStart=/usr/lib/mysql/mysql-systemd-helper start default (code=exited, status=1/FAILURE)
  Process: 19683 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade default (code=exited, status=0/SUCCESS)
  Process: 19672 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install default (code=exited, status=0/SUCCESS)
 Main PID: 19695 (code=exited, status=1/FAILURE)

Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139839810791168 [Note] InnoDB: FTS optimize thread exiting.
Jul 02 23:35:43 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:43 139840518174592 [Note] InnoDB: Starting shutdown...
Jul 02 23:35:45 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:45 139840518174592 [Note] InnoDB: Shutdown completed; log sequence number 1617399
Jul 02 23:35:45 unix mysql-systemd-helper[19695]: 2015-07-02 23:35:45 139840518174592 [Note] /usr/sbin/mysqld: Shutdown complete
Jul 02 23:35:45 unix systemd[1]: mysql.service: main process exited, code=exited, status=1/FAILURE
Jul 02 23:36:44 unix mysql-systemd-helper[19697]: MySQL is still dead
Jul 02 23:36:44 unix systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 02 23:36:44 unix systemd[1]: Failed to start MySQL server.
Jul 02 23:36:44 unix systemd[1]: Unit mysql.service entered failed state.
Jul 02 23:36:44 unix systemd[1]: mysql.service failed.

I’ve can’t see what is wrong in these logs. I’ve tried to completely remove Mariadb and my datadir, and then reinstall MDB but I get the same failure: InnoDB: not started

Ideas?

Miuku · July 3, 2015, 12:04am

Please post the output of;

zypper info mariadb

Your XtraDB is too new to be from the normal Tumbleweed installation.

Also post the output of:

zypper lr -d

Edit:
The MariaDB in the server:database repo is currently fubar because it updates to 10.1.x which is beta release and the systemd helper script is broken, it will never start. It seems you’re running 10.1 beta which is very, very bad. You should downgrade to 10.0.17 or 10.0.20.

benzene · July 3, 2015, 12:25am

Miuku:

Please post the output of;
zypper info mariadb
Your XtraDB is too new to be from the normal Tumbleweed installation.

Also post the output of:
zypper lr -d
Edit:
The MariaDB in the server:database repo is currently fubar because it updates to 10.1.x which is beta release and the systemd helper script is broken, it will never start. It seems you’re running 10.1 beta which is very, very bad. You should downgrade to 10.0.17 or 10.0.20.

Ahh, I see. I did indeed originally install from server:database for some reason that now escapes me. Will downgrade to TW and see what it says.

Miuku · July 3, 2015, 12:31am

You can install 10.0.20 from the server:database with **zypper in --oldpackage --from server_database mariadb=10.0.20-3.1
**
If you added with the default repo name. Otherwise adjust from.

benzene · July 3, 2015, 1:03am

The Software Management YaST module did not like to downgrade, it crashed. So I did it on in CLI. Now on 10.0.17.

If I now try to start it I get this:

 systemctl status mysql.service -l
● mysql.service - MySQL server
   Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2015-07-03 00:47:31 CEST; 6min ago
  Process: 3964 ExecStart=/usr/lib/mysql/rcmysql start (code=exited, status=1/FAILURE)

Jul 03 00:46:58 unix rcmysql[3964]: Phase 5/6: Running 'mysql_fix_privilege_tables'...
Jul 03 00:46:58 unix rcmysql[3964]: Phase 6/6: Running 'FLUSH PRIVILEGES'...
Jul 03 00:46:58 unix rcmysql[3964]: OK
Jul 03 00:47:31 unix rcmysql[3964]: Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds
Jul 03 00:47:31 unix rcmysql[3964]: chmod: cannot access ‘/var/run/mysql/mysqld.pid’: No such file or directory
Jul 03 00:47:31 unix rcmysql[3964]: Something went wrong
Jul 03 00:47:31 unix systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 03 00:47:31 unix systemd[1]: Failed to start MySQL server.
Jul 03 00:47:31 unix systemd[1]: Unit mysql.service entered failed state.
Jul 03 00:47:31 unix systemd[1]: mysql.service failed.

The /var/run/mysql/ dir does exist and is owned by mysql:mysql…

benzene · July 3, 2015, 1:02pm

Okay, I fixed it. The problem was now that there were my.cnf files in places where they should not be. I presume some were installed by the installer and existing ones renamed by the installer to *.rpminstall. Deleting the files that existed in the user dirs and the datadir, so that only the /etc/my.cnf was used fixed the situation.

Silicon_Penguin67 · July 10, 2015, 3:56am

I was having a similar problem as benzene. After the recent update, mariadb stopped working. Seems it quit during the update. Followed the advice and was able to downgrade to mariadb-10.0.20-2.9.1

I just wanted to say thanks all!

ArjenRodenhuis · July 14, 2015, 10:42pm

I’m not running Tumbleweed, but 13.2 and was having the same error here, on 2 computers, but now it’s running again.
The error was in the package “libmysqlclient_r18”, version 10.0.20-2.9.1.

The file “/usr/lib64/libmysqlclient_r.so”, which is linked to “/usr/lib64/libmysqlclient_r.so.18.0.0”, was 0 bytes and couldn’t be found by “mysql-workbench”.

After recreating the link manually, I can start mysqld again.

wolfi323 · July 14, 2015, 10:45pm

No, actually /usr/lib64/libmysqlclient_r.so points to a non-existing file:

ls -l /usr/lib64/libmysqlclient*
lrwxrwxrwx 1 root root      26  9. Jul 19:53 /usr/lib64/libmysqlclient_r.so -> libmysqlclient18.so.18.0.0
lrwxrwxrwx 1 root root      20  9. Jul 19:53 /usr/lib64/libmysqlclient.so -> libmysqlclient.so.18
lrwxrwxrwx 1 root root      24  9. Jul 19:52 /usr/lib64/libmysqlclient.so.18 -> libmysqlclient.so.18.0.0
-rwxr-xr-x 1 root root 3483608  1. Jul 01:12 /usr/lib64/libmysqlclient.so.18.0.0

The problem is known though, and a new update to fix this has already been submitted and should be released in the next days…

mysql-workbench works fine here despite this though. Only LibreOffice Base crashes when trying to connect to mariadb.

But this is totally unrelated to the previously mentioned problems in this thread…

wolfi323 · July 15, 2015, 8:28am

Actually, the followup update to fix this has been released already meanwhile…