Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

MySQL Daemon failed on the start of docker version of HDP 2.6.4

avatar
Explorer

I am just starting with a Hortonworks tools and using Docker version of HDP 2.6.4 Sandbox on the Ubuntu 16.04.2 LTS server.

Fore some reason MySQL fails immediately after running of the start-sandbox-hdp-standalone_2-6-4.sh with the message

MySQL Daemon failed to start.

62652-2018-03-05-01-20-45.png

What might be the reason?

1 ACCEPTED SOLUTION

avatar
Contributor

@Timur Kobilov, I could deploy HDP 2.6.4 on Ubuntu 16.04 LTS and MySQL started without any issues.

Could you please try running the command "service mysqld start" from inside the sandbox and see what error you get ?

Can you please check the permission/ownership of directory "/var/lib/mysql" ?

Also if you could paste the log contents from "/var/log/mysqld.log" in sandbox, that would be helpful.

View solution in original post

12 REPLIES 12

avatar
Master Mentor

@Timur Kobilov

I see that there are some minor difference between the "start_sandbox-hdp.sh" script in previous and current version. Can you please try using the

Difference in old "start_sandbox-hdp.sh":
https://github.com/hortonworks/data-tutorials/commit/f88da0da324e252996cf3201fc9b038e9564a665#diff-4...


Can you please try using the following Script "start_sandbox-hdp.sh" instead and see if it works:
https://raw.githubusercontent.com/hortonworks/data-tutorials/f88da0da324e252996cf3201fc9b038e9564a66...

.

avatar
Explorer

@Jay Kumar SenSharma

Thank you for your message.

Unfortunately the same result. I'm steel getting the same MySQL daemon error.

I have also tried this with HDP 2.6.1 docker image version.

avatar
Contributor

@Timur Kobilov, I could deploy HDP 2.6.4 on Ubuntu 16.04 LTS and MySQL started without any issues.

Could you please try running the command "service mysqld start" from inside the sandbox and see what error you get ?

Can you please check the permission/ownership of directory "/var/lib/mysql" ?

Also if you could paste the log contents from "/var/log/mysqld.log" in sandbox, that would be helpful.

avatar
Explorer

Accepted this answer. More about that below

avatar
Explorer

@vpaul


'service mysqld start' failed with the same message:

MySQL Daemon failed to start.
Starting mysqld:  			[FAILED]

'/var/lib/mysql' permissions:

drwxr-xr-x 1 mysql mysql 4096 Feb  1 10:54 /var/lib/MySQL

There are no content lines in the '/var/log/mysqld.log':

[root@sandbox-hdp log]# cat /var/log/mysqld.log
[root@sandbox-hdp log]#

avatar
Contributor

@Timur Kobilov

Since the logs are empty, you could run the command as follows to generate a more verbose output.

sh -x /etc/init.d/mysqld start

avatar
Contributor

The timestamp on the mysql folder is Feb 1 which is confusing.

Could you please redeploy HDP 2.6.4 with the script downloaded from here ?

The md5sum of the downloaded script should be b14f4538147851c51b26d9da37ab931c. Please verify the same after download.

avatar
Explorer

@vpaul

So... I afraid I'm missing something...

I got 'start-sandbox-hdp-standalone_2-6-4.sh.zip', unzipped it and deployed HPD 2.6.4 as discribed here

The md5sum of the 'start-sandbox-hdp-standalone_2-6-4.sh.zip' was 2c2cee0aafc71405b373f89eb9a988d7 as on the picture below (not b14f4538147851c51b26d9da37ab931c):

62699-2018-03-07-15-53-31.png

Starting this script leads to the same 'MySQL Daemon failed to start' message as before. Timestamp of the '/var/lib/mysql' is Feb 1:

62700-2018-03-07-16-05-14.png

I also tried 'sh -x /etc/init.d/mysqld start'. The output is here

avatar
Contributor

@Timur Kobilov

It looks like the script you have is not the proper one.

Could you please download from the link here.

Click on "DOWNLOAD FOR DOCKER LINUX/MAC" . It is not a zipped file but just a shell script named "start-sandbox-hdp-standalone_2-6-4.sh" and having an md5sum of "b14f4538147851c51b26d9da37ab931c"

The details can be found here in the release notes.

Please try deploying using the same and let us know if you have issues.