Open pearcec opened 12 years ago
It's opscode mysql cookbook problem. I have the same crap in my own recipe
Is it possible to fix? What is the issue do you know? Can we patch it and send out a pull request?
seems I fixed it here https://github.com/everm1nd/mysql
I can confirm this. Ubuntu 10.04, trying to get lamp up and running. Indeed a vagrant provision
does work. After a vagrant up
, even if it fails, mysql is up and running (confirmed by logging in with ssh and doing mysql -u root -p "somepass").
From what I understand, it would be necessary to wait for mysql to be "really" started, like checking service mysql status
till it reports mysql start/running
!
I think so, but still don't find any way how to do it
I just recognized another behaviour: If I kill the virtualbox process (Called VBoxHeadless.exe on my Windows 7 64 bit) and then do vagrant up
, it works as expected without the need to run vagrant provision
! I don't know if this helps though.
I am closing this. We updated to 10.04.4 and some newer version of cookbooks. Not sure which version might of resolved it but it isn't happening for me.
This appears to happen after a reload.
+1
This happens to me, but not every time. It's not waiting for the mysql process to be running before trying to run the grant command. Sometimes it is running, sometimes it isn't, I guess depending on the load of other parts of the system etc.
Hm. Weird. Have never hit this myself... running 10.04 LTS VM on macbook dual core (latest vbox 4.1.x)
I have the same issue on Ubuntu 12.04 64bit. Strange, but i386 works great... Here some ugly, but working solution.
service "mysql" do
action :start
only_if "test -f /etc/init.d/mysql"
end
include_recipe "mysql::server"
I get this isssue on cent os 6.3. The comment above fixes it. Something odd with certain versions of linux
the above fixes does not work on ubuntu 12.04, do i just replace the sever recipe with the fixes in the right section?
When I
vagrant halt
, then runvagrant up
after initial deployment, I get this. The work around is to runvagrant provision
. Seems MySQL isn't running quite yet.