Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 925 Vote(s) - 3.49 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vagrant up fails with stdin, start, ssh, stderr & stdout errors

#1
I cannot for the life of me...after reinstalling all things VVV/VBox(4.3.10) & running vagrant up --provision figure out why this beauty(VVV) wont run. I'm unable to access any of the wordpress sites such as

[To see links please register here]

.

Specs:
Windows 8.1
Cygwin

Final lines after running the cmd ->
vagrant up --provision

==> default:

[To see links please register here]

==> default: Downloading phpMyAdmin 4.1.14...
==> default: Restart Nginx...
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: Cleaning the virtual machine's /etc/hosts file...
==> default: Adding domains to the virtual machine's /etc/hosts file...
==> default: * Added vvv.dev from /srv/www/vvv-hosts
==> default: * Added local.wordpress.dev from /srv/www/vvv-hosts
==> default: * Added local.wordpress-trunk.dev from /srv/www/vvv-hosts
==> default: * Added src.wordpress-develop.dev from /srv/www/vvv-hosts
==> default: * Added build.wordpress-develop.dev from /srv/www/vvv-hosts
==> default: -----------------------------
==> default: Provisioning complete in 1636 seconds
==> default: External network connection established, packages up to date.
==> default: For further setup instructions, visit

[To see links please register here]

==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: start: Job is already running: mysql
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chmod +x /tmp/vagrant-shell && /tmp/vagrant-shell

Stdout from the command:



Stderr from the command:

stdin: is not a tty
start: Job is already running: mysql


Where am I going wrong?
Reply

#2
Not anything you are doing. Apparently this is a known issue.

I fixed it by running `vagrant ssh`

and then

sudo service mysql restart || true

You can find a record of the issue [here][1]


[1]:

[To see links please register here]

Reply

#3
Add the following line in your Vagrantfile

config.ssh.shell = "bash -c 'BASH_ENV=/etc/profile exec bash'"

This starts bash as a non-login shell, but also tells it to source /etc/profile, which I hypothesised to be the only reason to use a login shell by default. Works for me with the stock precise64 Vagrant box.
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through