Description of problem: After a yum update of all packages and a reboot, mariadb-server doesn't start. It worked fine before the update with mariadb-server-5.5.33a-1.fc19.x86_64. MariaDB seems to start fine but is immediately shut down due to /usr/libexec/mysqld-wait-ready exiting with status 1. Commenting out ExecStartPost in /usr/lib/systemd/system/mysqld.service works around the problem. This may be a duplicate of bug 1034790. Version-Release number of selected component (if applicable): mariadb-server-5.5.34-1.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. systemctl start mysqld Actual results: mysqld stops immediately after starting. Expected results: mysqld keeps running. Additional info: Output of "systemctl status mysqld": mysqld.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled) Active: failed (Result: exit-code) since Fri 2014-01-03 17:59:51 PST; 9s ago Process: 12271 ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID (code=exited, status=1/FAILURE) Process: 12270 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS) Process: 12246 ExecStartPre=/usr/libexec/mysqld-prepare-db-dir %n (code=exited, status=0/SUCCESS) Jan 03 17:59:48 photo1.fxpal.net mysqld_safe[12270]: 140103 17:59:48 mysqld_safe Logging to '/var/lib/mysql/photo1.fxpal.net.err'. Jan 03 17:59:48 photo1.fxpal.net mysqld_safe[12270]: 140103 17:59:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Jan 03 17:59:50 photo1.fxpal.net systemd[1]: mysqld.service: control process exited, code=exited status=1 Jan 03 17:59:51 photo1.fxpal.net mysqld_safe[12270]: 140103 17:59:51 mysqld_safe mysqld from pid file /var/lib/mysql/photo1.fxpal.net.pid ended Jan 03 17:59:51 photo1.fxpal.net systemd[1]: Failed to start MariaDB database server. Jan 03 17:59:51 photo1.fxpal.net systemd[1]: Unit mysqld.service entered failed state. Log from unsuccessful start: 140103 18:03:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 140103 18:03:07 InnoDB: The InnoDB memory heap is disabled 140103 18:03:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140103 18:03:07 InnoDB: Compressed tables use zlib 1.2.7 140103 18:03:07 InnoDB: Using Linux native AIO 140103 18:03:07 InnoDB: Initializing buffer pool, size = 128.0M 140103 18:03:07 InnoDB: Completed initialization of buffer pool 140103 18:03:07 InnoDB: highest supported file format is Barracuda. 140103 18:03:07 InnoDB: Waiting for the background threads to start 140103 18:03:08 Percona XtraDB (http://www.percona.com) 5.5.34-MariaDB-31.1 started; log sequence number 462795614 140103 18:03:08 [Note] Plugin 'FEEDBACK' is disabled. 140103 18:03:08 [Note] Server socket created on IP: '0.0.0.0'. 140103 18:03:08 [Note] Event Scheduler: Loaded 0 events 140103 18:03:08 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.34-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 140103 18:03:09 [Note] /usr/libexec/mysqld: Normal shutdown 140103 18:03:09 [Note] Event Scheduler: Purging the queue. 0 events 140103 18:03:09 InnoDB: Starting shutdown... 140103 18:03:10 InnoDB: Shutdown completed; log sequence number 462795614 140103 18:03:10 [Note] /usr/libexec/mysqld: Shutdown complete 140103 18:03:10 mysqld_safe mysqld from pid file /var/lib/mysql/photo1.fxpal.net.pid ended Log after commenting out ExecStartPost in /usr/lib/systemd/system/mysqld.service: 140103 18:03:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 140103 18:03:20 InnoDB: The InnoDB memory heap is disabled 140103 18:03:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140103 18:03:20 InnoDB: Compressed tables use zlib 1.2.7 140103 18:03:20 InnoDB: Using Linux native AIO 140103 18:03:20 InnoDB: Initializing buffer pool, size = 128.0M 140103 18:03:20 InnoDB: Completed initialization of buffer pool 140103 18:03:20 InnoDB: highest supported file format is Barracuda. 140103 18:03:20 InnoDB: Waiting for the background threads to start 140103 18:03:21 Percona XtraDB (http://www.percona.com) 5.5.34-MariaDB-31.1 started; log sequence number 462795614 140103 18:03:21 [Note] Plugin 'FEEDBACK' is disabled. 140103 18:03:21 [Note] Server socket created on IP: '0.0.0.0'. 140103 18:03:21 [Note] Event Scheduler: Loaded 0 events 140103 18:03:21 [Note] /usr/libexec/mysqld: ready for connections.
Thanks for reporting. I've reproduced this and it is indeed similar to bug #1034790, but caused by a little bit different cause. I'll submit a fixed update asap.
mariadb-5.5.34-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mariadb-5.5.34-3.fc20
Package mariadb-5.5.34-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mariadb-5.5.34-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0389/mariadb-5.5.34-3.fc20 then log in and leave karma (feedback).
mariadb-5.5.34-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.