-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
./bin/wasabi.sh start - Can't connect to MySQL on '172.18.0.3' #236
Comments
I never ran into an issue like that, but it could be related to the mysql server configuration as described here: http://stackoverflow.com/questions/1420839/cant-connect-to-mysql-server-error-111. @jwtodd do you know if/how we could resolve such an issue with docker? |
@AndreaSuckro sry just now seeing this :( hmmm no i haven't seen this error before. i tried to echo the command-as-executed when an error occurs so that one can copy-paste the command directly to work through the error condition. |
Probably your server instance is running out of memory. I was having the same problem when I was trying to run Wasabi on a 1GB instance. Checking the docker logs for the mysql:5.6 container got me into this docker-library/mysql issue. Increasing your instance memory to 2GB should solve this issue. |
Hi, I am getting the same error. Not able to start cassandra as well |
I got the same issue. I upgraded my server from 1GB (to 4GB in my case) as suggested by @brunoarakaki It fixed the problem |
what are the steps to do this? |
Hello,
I have trouble installing Wasabi on Ubuntu 16.04 x64, using sudo user
wasabi
.The bootstrap, reboot and build commands all ran without a single problem. When
./bin/wasabi.sh build
completed it said something like "completed successfully with 0 errors". However I can't get Wasabi to start. Upon trying to run./bin/wasabi.sh start
I get the following errorIs that something already known?
The text was updated successfully, but these errors were encountered: