mysql 5.7 error after using cloudera recommended my.cnf config

ronnie10 — Wed, 22 Nov 2017 14:31:09 GMT

Hi there,

I have installed Mysql 5.7 as external DB for cloudera setup, however after using the recommeded my.cnf config, the mysql database could not start.

https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_mysql.html

The error shown is after starting mysql:

Redirecting to /bin/systemctl start mysqld.service
Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.

● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Wed 2017-11-22 06:26:28 PST; 19s ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 5401 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 5380 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
Main PID: 5035 (code=exited, status=0/SUCCESS)

The systemctl status mysqld shows following:
Nov 22 06:26:28 localhost.localdomain systemd[1]: mysqld.service: control process exited, code=exited status=1
Nov 22 06:26:28 localhost.localdomain systemd[1]: Failed to start MySQL Server.
Nov 22 06:26:28 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
Nov 22 06:26:28 localhost.localdomain systemd[1]: mysqld.service failed.
Nov 22 06:26:28 localhost.localdomain systemd[1]: mysqld.service holdoff time over, scheduling restart.
Nov 22 06:26:28 localhost.localdomain systemd[1]: start request repeated too quickly for mysqld.service
Nov 22 06:26:28 localhost.localdomain systemd[1]: Failed to start MySQL Server.
Nov 22 06:26:28 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
Nov 22 06:26:28 localhost.localdomain systemd[1]: mysqld.service failed.

journalctl -xe shows following:

-- Unit mysqld.service has begun starting up.
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: 2017-11-22T14:29:17.979624Z
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: 2017-11-22T14:29:17.980614Z
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: 2017-11-22T14:29:17.981890Z
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: 2017-11-22T14:29:17.981910Z
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: 2017-11-22T14:29:17.981943Z
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: 2017-11-22T14:29:17.981993Z
Nov 22 06:29:17 localhost.localdomain systemd[1]: mysqld.service: control proces
Nov 22 06:29:17 localhost.localdomain mysqld[5593]: Initialization of mysqld fai
Nov 22 06:29:17 localhost.localdomain 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.
--
-- The result is failed.
Nov 22 06:29:17 localhost.localdomain systemd[1]: Unit mysqld.service entered fa
Nov 22 06:29:17 localhost.localdomain systemd[1]: mysqld.service failed.
Nov 22 06:29:18 localhost.localdomain systemd[1]: mysqld.service holdoff time ov
Nov 22 06:29:18 localhost.localdomain systemd[1]: Starting MySQL Server...
-- Subject: Unit mysqld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has begun starting up.

Has anyone got the same error?

Thanks.

Re: mysql 5.7 error after using cloudera recommended my.cnf config

bgooley — Wed, 22 Nov 2017 15:28:42 GMT

@ronnie10,

Hi,

The errors you have presented are all at the systemd level and only tell us that mysql didn't start. I'd check the mysql log files for clues as to why the start failed so we can get an idea of what the problem is.

-Ben

Re: mysql 5.7 error after using cloudera recommended my.cnf config

ronnie10 — Thu, 23 Nov 2017 03:16:47 GMT

I have checked the log under /var/log/mysqld.log, it was empty.

Re: mysql 5.7 error after using cloudera recommended my.cnf config

ronnie10 — Thu, 23 Nov 2017 06:51:07 GMT

@bgooley

Hi Ben,

I have done a few trial and error, the initial my.cnf was ok to start the mysql.

Once I change the my.cnf to Cloudera recommended settings, it will crash.

I need to comment out from the cnf file then only it will work, will this affect anything?

#log_bin=/var/lib/mysql/mysql_binary_log

Re: mysql 5.7 error after using cloudera recommended my.cnf config

Tomas79 — Sun, 26 Nov 2017 20:14:12 GMT

Do you have this directory created?
Are the permissions correctly set on this path?

Re: mysql 5.7 error after using cloudera recommended my.cnf config

ronnie10 — Mon, 27 Nov 2017 01:39:25 GMT

Thanks for the reply, after I rebooted the OS, the mysql will not start again.

question mysql 5.7 error after using cloudera recommended my.cnf config in Archives of Support Questions (Read Only)

mysql 5.7 error after using cloudera recommended my.cnf config

Re: mysql 5.7 error after using cloudera recommended my.cnf config

Re: mysql 5.7 error after using cloudera recommended my.cnf config

Re: mysql 5.7 error after using cloudera recommended my.cnf config

Re: mysql 5.7 error after using cloudera recommended my.cnf config

Re: mysql 5.7 error after using cloudera recommended my.cnf config