Hi all,
Well I tried to setup a new server today with DirectAdmin PHP 7.2 and MySQL 5.7 (based on CentOS 7.x).
For some reason it's installing MySQL 5.7, but it refuses to start.
So maybe I did something wrong; did a new install, but this time with MySQL 5.6 and installed perfectly and everything working (also CentOS 7.x).
Then I tried to upgrade MySQL to 5.7 as advertised here: https://www.prado.lt/directadmin-an...min-and-custombuild-2-0-now-support-mysql-5-7
Followed everything correctly (except for the backups, because it's a fresh install anyways). But same result, after the upgrade MySQL won't start. No matter what.
I also tried deleting /etc/my.cnf and tried restarting. Exactly the same result.
The "systemctl status mysqld.service" gives me this:
The output of "journalctl -xe" is (partially):
And the output, if useful, for "service mysqld status" is the following:
I have no clue what's wrong here. The exact same thing happens with a clean install with MySQL 5.7 and doing an upgrade of a clean install with MySQL 5.6 to MySQL 5.7.
If I use MySQL 5.6 for a clean install everything works...
Any advice or ideas? I am pretty clueless here.
Thanks in advance.
Regards
Well I tried to setup a new server today with DirectAdmin PHP 7.2 and MySQL 5.7 (based on CentOS 7.x).
For some reason it's installing MySQL 5.7, but it refuses to start.
So maybe I did something wrong; did a new install, but this time with MySQL 5.6 and installed perfectly and everything working (also CentOS 7.x).
Then I tried to upgrade MySQL to 5.7 as advertised here: https://www.prado.lt/directadmin-an...min-and-custombuild-2-0-now-support-mysql-5-7
Followed everything correctly (except for the backups, because it's a fresh install anyways). But same result, after the upgrade MySQL won't start. No matter what.
I also tried deleting /etc/my.cnf and tried restarting. Exactly the same result.
Starting mysqld (via systemctl): Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
[FAILED]
The "systemctl status mysqld.service" gives me this:
* mysqld.service - MySQL Server
Loaded: loaded (/etc/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2018-06-14 22:22:02 CEST; 30s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 7122 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=203/EXEC)
Main PID: 419 (code=exited, status=0/SUCCESS)
Jun 14 22:22:02 host systemd[1]: Unit mysqld.service entered failed state.
Jun 14 22:22:02 host systemd[1]: mysqld.service failed.
Jun 14 22:22:02 host systemd[1]: mysqld.service holdoff time over, scheduling restart.
Jun 14 22:22:02 host systemd[1]: start request repeated too quickly for mysqld.service
Jun 14 22:22:02 host systemd[1]: Failed to start MySQL Server.
Jun 14 22:22:02 host systemd[1]: Unit mysqld.service entered failed state.
Jun 14 22:22:02 host systemd[1]: mysqld.service failed.
Jun 14 22:22:06 host systemd[1]: start request repeated too quickly for mysqld.service
Jun 14 22:22:06 host systemd[1]: Failed to start MySQL Server.
Jun 14 22:22:06 host systemd[1]: mysqld.service failed.
The output of "journalctl -xe" is (partially):
-- Unit mysqld.service has begun starting up.
Jun 14 22:23:02 host systemd[7226]: Failed at step EXEC spawning /usr/bin/mysqld_pre_systemd: No such file or directory
-- Subject: Process /usr/bin/mysqld_pre_systemd could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/mysqld_pre_systemd could not be executed and failed.
--
-- The error number returned by this process is 2.
Jun 14 22:23:02 host systemd[1]: mysqld.service: control process exited, code=exited status=203
Jun 14 22:23:02 host systemd[1]: Failed to start MySQL Server.
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has failed.
And the output, if useful, for "service mysqld status" is the following:
PHP:
Jun 14 22:17:02 host systemd: Starting MySQL Server...
Jun 14 22:17:02 host systemd: Failed at step EXEC spawning /usr/bin/mysqld_pre_systemd: No such file or directory
Jun 14 22:17:02 host systemd: mysqld.service: control process exited, code=exited status=203
Jun 14 22:17:02 host systemd: Failed to start MySQL Server.
Jun 14 22:17:02 host systemd: Unit mysqld.service entered failed state.
Jun 14 22:17:02 host systemd: mysqld.service failed.
Jun 14 22:17:02 host systemd: mysqld.service holdoff time over, scheduling restart.
Jun 14 22:17:02 host systemd: Starting MySQL Server...
Jun 14 22:17:02 host systemd: Failed at step EXEC spawning /usr/bin/mysqld_pre_systemd: No such file or directory
Jun 14 22:17:02 host systemd: mysqld.service: control process exited, code=exited status=203
Jun 14 22:17:02 host systemd: Failed to start MySQL Server.
Jun 14 22:17:02 host systemd: Unit mysqld.service entered failed state.
Jun 14 22:17:02 host systemd: mysqld.service failed.
Jun 14 22:17:03 host systemd: mysqld.service holdoff time over, scheduling restart.
Jun 14 22:17:03 host systemd: start request repeated too quickly for mysqld.service
Jun 14 22:17:03 host systemd: Failed to start MySQL Server.
Jun 14 22:17:03 host systemd: Unit mysqld.service entered failed state.
Jun 14 22:17:03 host systemd: mysqld.service failed.
Jun 14 22:17:06 host systemd: start request repeated too quickly for mysqld.service
Jun 14 22:17:06 host systemd: Failed to start MySQL Server.
Jun 14 22:17:06 host systemd: mysqld.service failed.
Jun 14 22:17:11 host systemd: Removed slice User Slice of root.
Jun 14 22:17:11 host systemd: Stopping User Slice of root.
I have no clue what's wrong here. The exact same thing happens with a clean install with MySQL 5.7 and doing an upgrade of a clean install with MySQL 5.6 to MySQL 5.7.
If I use MySQL 5.6 for a clean install everything works...
Any advice or ideas? I am pretty clueless here.
Thanks in advance.
Regards