wordpress - Vagrant up fails with stdin, start, ssh, stderr & stdout errors -
i cannot life of me...after reinstalling things vvv/vbox(4.3.10) & running vagrant --provision figure out why beauty(vvv) wont run. i'm unable access of wordpress sites such http://local.wordpress.dev/.
specs: windows 8.1 cygwin
final lines after running cmd -> vagrant --provision
==> default: http://gruntjs.com/getting-started ==> default: downloading phpmyadmin 4.1.14... ==> default: restart nginx... ==> default: * restarting nginx nginx ==> default: ...done. ==> default: cleaning virtual machine's /etc/hosts file... ==> default: adding domains virtual machine's /etc/hosts file... ==> default: * added vvv.dev /srv/www/vvv-hosts ==> default: * added local.wordpress.dev /srv/www/vvv-hosts ==> default: * added local.wordpress-trunk.dev /srv/www/vvv-hosts ==> default: * added src.wordpress-develop.dev /srv/www/vvv-hosts ==> default: * added build.wordpress-develop.dev /srv/www/vvv-hosts ==> default: ----------------------------- ==> default: provisioning complete in 1636 seconds ==> default: external network connection established, packages date. ==> default: further setup instructions, visit http://vvv.dev ==> default: running provisioner: shell... default: running: inline script ==> default: stdin: not tty ==> default: start: job running: mysql following ssh command responded non-zero exit status. vagrant assumes means command failed! chmod +x /tmp/vagrant-shell && /tmp/vagrant-shell stdout command: stderr command: stdin: not tty start: job running: mysql
where going wrong?
add following line vagrantfile
config.ssh.shell = "bash -c 'bash_env=/etc/profile exec bash'"
this starts bash non-login shell, tells source /etc/profile, hypothesised reason use login shell default. works me stock precise64 vagrant box.
Comments
Post a Comment