Skip to content
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

Open
MrSnoozles opened this issue May 3, 2017 · 6 comments
Open

./bin/wasabi.sh start - Can't connect to MySQL on '172.18.0.3' #236

MrSnoozles opened this issue May 3, 2017 · 6 comments

Comments

@MrSnoozles
Copy link

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 error

...
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Connected to cluster: Test Cluster
Data center: datacenter1; Host: wasabi-cassandra/172.18.0.2
Current version of keyspace wasabi_experiments: 034
Keyspace wasabi_experiments is up to date, no migration necessary
wasabi: [DONE] creating keyspace and migration schemas
Warning: Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on '172.18.0.3' (111)
error: unable to run command: % docker run --net=wasabi_nw -it --rm mysql:5.6 mysql -h172.18.0.3 -P3306 -uroot -pmypass -e "    create database if not exists wasabi;
    grant all privileges on wasabi.* to 'readwrite'@'localhost' identified by 'readwrite';
    grant all on *.* to 'readwrite'@'%' identified by 'readwrite';
    flush privileges;"

Is that something already known?

@AndreaSuckro
Copy link
Member

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?

@jwtodd
Copy link
Member

jwtodd commented Jun 14, 2017

@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.

@brunoarakaki
Copy link

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.

@fangorn88
Copy link

Hi, I am getting the same error. Not able to start cassandra as well

@Francescu
Copy link

I got the same issue. I upgraded my server from 1GB (to 4GB in my case) as suggested by @brunoarakaki

It fixed the problem

@Dragon-Of-Dojima
Copy link

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.

what are the steps to do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants