-
Notifications
You must be signed in to change notification settings - Fork 25
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
MySQL-Server not reachable #17
Comments
After changing db-configuration from ip to localhost i got the following error-message: |
Ok, looking for the running MySQL-server ends up in the awareness that there is no MySQL-server running. |
I destroyed the machine again yesterday and ran vagrant up again. After that, the MySQL-server works fine but when I halt the machine and start it up again the MySQL-server is again not reachable. Any other users with this issue? |
Have you tried to just restart the MySQL server manually? sudo service mysqld restart I can also highly recommend doing |
With 'vagrant suspend' everything works fine. No I only have the problem that I can't connect to the database with Sequel-SQL client. The access from outside of the machine seems to be blocked. A portscan to 172.22.22.22 or 'name-of-my-project'.local answers that there is no port 3306 is open. |
I'm having both issues, the socket error and also when I try to connect to the database through Sequel. I tried restarting the MySQL server manually (mysqld didn't work, had to be mysql)... |
I've had the same issue as well, I instead did a vagrant destroy and re-built the machine after wasting an hour trying to figure things out. |
I've the same issue. The command 'service mysql status' by ssh => mysql stop/waiting I use too vagrant-phpstorm-tunnel plugin, i loose in the same time, the tunnel between PhPStorm and Vagrant machine. |
Hey,
after running 'vagrant up' and provisioning the machine, the MySQL-Server seems to be not reachable from Laravel.
A portscan to the machines-ip told me, that there is no open port 3306. Anyone else with this problem?
Greetings
The text was updated successfully, but these errors were encountered: