Join GitHub today
Expired password #373
Please note that the Homestead issue tracker is reserved for bug reports and
Provider & Provider version
Host operating system
Linux elementary OS 0.3.2 Freya (64-bit) - Built on Ubuntu 14.04
--- ip: "192.168.10.10" memory: 2048 cpus: 1 provider: virtualbox version: "0.3.3" authorize: ~/.ssh/id_rsa.pub keys: - ~/.ssh/id_rsa folders: - map: ~/Code/TrueRev to: /home/vagrant/Code/TrueRev sites: - map: truerev.dev to: /home/vagrant/Code/TrueRev/public databases: - homestead - truerev_testing # blackfire: # - id: foo # token: bar # client-id: foo # client-token: bar # ports: # - send: 50000 # to: 5000 # - send: 7777 # to: 777 # protocol: udp
Vagrant up output
Vagrant should have migrated the files into the database successfully.
The vagrant up command fails with the following
Steps to reproduce
You're using really far out of date versions.
Your Virtualbox version is way out of date. Please upgrade to 5.1.x and also make sure you update Homestead to 3.1.
If you have to use an old version for a project that's understandable, but you should try to upgrade to stay up to date.
A solution to your problem is putting the commands to reset the mysql password in your
Hello @svpernova09 ok no problem thanks for your time.
Just a quick correction in your solution, is not possible to add the mysql command into after.sh. This is because homestead executes previous sql statements that rises the error.
Also I know that this issue is not caused by virtualbox version, this issue is in the MySQL.
Anyway, thanks !
@marabesi when did you first notice this issue? I have a hunch it's based off of when the vm was built https://github.com/laravel/settler that is. If that' the case and you wanted to stick with the
The later boxes don't have this problem because MySQL 5.7.10 relaxed the
The fix of setting the password is only a bandaid as 360 days from provisioning the password will expire again.
While Homestead v3+ allows you to set the version like this, the provisioning scripts run
It would look something like the following:
Note: This will not work for any other version the box because the mysql config directory changed in higher versions of MySQL 5.7 as well. It should no longer be needed honestly, or at least until the MySQL gods wish to inflict this scourge upon us again.
I don't think I mentioned it, but the later versions of settler and subsequently boxes >
Fortunately, it seems this issue is only specific to
I submitted this PR to settler and the work involved was extensive to say the least, just to try to upgrade MySQL beyond v5.7.10. The box I created from this patch is primarily functional but I don't have projects that would put Postgres, HHVM, Redis, or any of the other services through their paces. The easier fix is to just patch Homestead as I couldn't guarantee the changes in ppas or system packages didn't radically destabilize the system.
So if someone took
or something close to that.
Repackaged it as
@svpernova09 seems totally fair. So that would put this in the "needs to be fixed" bucket. Can we reopen?
Where you have Homestead installed open
If there is a line similar to