Closed brianrivet closed 5 years ago
From line # 7 in your output it seems you are running homestead version 5.2.0. I can imagine that this version is not compatible anymore with the base box. Maybe try provisioning again with the latest version (7.20.0) ?
Thanks! It looks like that may have been the problem.
Hi, I'm having trouble with a reinstall of Homestead. I destroyed my previous box after it went down for some reason, and when I tried to up and re-provision it . says that it is configuring mysql server and purging the old mysql config. It asks if I want to remove all MySQL databases, which appears to autoselect no and continue, but then the install hangs up when saying it is removing the old configs. It doesn't give an error, but it just sits with no prompt or updates. If I hit cntrl-c to exit, it gives me a list of errors. I've tried removing all of the VMs from virtualbox and starting over, but nothing has worked so far.
Versions
A lot of issues can be resolved by simply updating vagrant, provider or homestead.
Host operating system
Mac OS 10.14.2
Homestead.yaml
Vagrant destroy & up output
https://gist.github.com/brianrivet/fb8bde0a1aa2972c3ceb168d7a97f992
Expected behavior
I expected Homestead to complete the installation at which point I can use the VM. I should be able to connect to the server via ssh and connect to databases via ssh in Sequel Pro.
Actual behavior
Homestead appears to hang up during the installation, at the point when it is supposed to be setting up MySQL. I can SSH into homestead from the command line, but I cannot connect to MySQL via Sequel Pro. I have run into an issue in the past where Apparmor was preventing MariaDB from running, but this doesn't appear to be the issue here. I've tried this fix for that issue () and it had no effect. Also, when I try to re-provision, It says MariaDB is installed, but then I get this error:
I checked the location referenced in the error and the file doesn't exist. I also tried starting mysql using "sudo /etc/init.d/mysql start" and it returned that the command was not found. I also tried to run "sudo /usr/bin/mysql start" and itr gave me this error:
I remember running into a similar problem before (although it didn't hang up during install) that is referenced here: https://askubuntu.com/questions/750604/why-does-mariadb-keep-dying-how-do-i-stop-it
I tried the solution described there and it still had no success (It did work in the past when I ran into this problem).
Steps to reproduce
References
I've referenced everything I've looked at/tried above.