VVV: Mysql not started on boot
According to the tutorial, provisioning should take care of everything so you should be good to go after the initial vagrant up. However, in the current master mysqld does not come up automatically.
I’m currently unaware of whether there are some issues with mysqld+upstart in Precise, but sticking an update-rc.d mysql defaults somewhere around provision.sh:328 should fix this.
(In case it is a conscious design decision I don’t see it documented anywhere;))
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 39 (16 by maintainers)
Commits related to this issue
- Use Unix line endings on conf files This is specifically directed to #287, in which these line endings may be causing issues when starting the MySQL service after a restart of the VM. — committed to Varying-Vagrant-Vagrants/VVV by jeremyfelt 10 years ago
- Only mount shared DB drive if already mounting This shifts the default behavior for VVV to non-persisting databases. If an existing VM is already storing database data on the guest machine, drives wi... — committed to Varying-Vagrant-Vagrants/VVV by jeremyfelt 10 years ago
- Use Unix line endings on conf files This is specifically directed to #287, in which these line endings may be causing issues when starting the MySQL service after a restart of the VM. — committed to jb510/VVV by jeremyfelt 10 years ago
- Only mount shared DB drive if already mounting This shifts the default behavior for VVV to non-persisting databases. If an existing VM is already storing database data on the guest machine, drives wi... — committed to jb510/VVV by jeremyfelt 10 years ago
+1, have had the same problem more than a couple of times. Have to SSH in and start MySQL manually