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.
What might be the reason?
@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
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...
@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.
Accepted this answer. More about that below
'service mysqld start' failed with the same message:
MySQL Daemon failed to start.
Starting mysqld: [FAILED]
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
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
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.
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):
Starting this script leads to the same 'MySQL Daemon failed to start' message as before. Timestamp of the '/var/lib/mysql' is Feb 1:
I also tried 'sh -x /etc/init.d/mysqld start'. The output is here
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.
Shall-file I got here after unzipping has exactly the same md5sum you say:
And it resilts with an error I mentioned before:
My docker version is '17.12.1-ce' and OS is Ubuntu 16.04.4 LTS. Is it ok?
It looks the host where the container is deployed has an active MySQL installation and the MySQL daemon is running.
I tried installing and starting MySQL on my Ubuntu host and could see MySQL in the container failing to start.
Could you please try stopping MySQL daemon in your host machine and then deploy the sandbox ?
I have similar configuration as yours.
Ubuntu 16.04 LTS Release:16.04
Docker version 17.12.0-ce, build c97c6d6
Yes! It works. As you said the problem was with a mysql daemon running on the host machine.