Vvv: how to fix error "default: stdin: is not a tty" when using vagrant up

[ricker07]

This is what i get when i run "vagrant up". i already do everything, line "sudo service mysql restart || true", vagrant hault, vagrant provision, sudo apt-get update, etc. but it doesn't work. please help me, i just want to update my mysql from 5.5 to 5.6 because i'm using laravel framework and the system i'm working on today is required to use mysql version 5.6.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: A newer version of the box 'laravel/homestead' is available! You currently
==> default: have version '0.2.0'. The latest is version '0.2.1'. Run
==> default: vagrant box update to update.
==> default: Setting the name of the VM: Homestead_default_1418261939885_87172
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 80 => 8000 (adapter 1)
default: 3306 => 33060 (adapter 1)
default: 5432 => 54320 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /vagrant => /home/sedp/Homestead
default: /home/vagrant/Projects => /home/sedp/Projects
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCiivZdJRmsEDj0PtfecSxl3g/HOAsmQXh7K4x0LQB5NKONbpO0leFRFJ2lV+iGMasqA45tfF9jGSIxmGsMfmg6VOVkUZ2EWk6tURFfM5FW3DgeL9CLcG4OhTHLyA9AcTHH0BvVml2OWYeXyfM5J8rURbaURZF1qKtjuR2r/JfF1HK0fhgjgnPMfBgkEt77XXMYSfDYxOSY9IhXEr8uNzXRjBWVmB1PNERoOCmodfANjClL8ptbguT+jYgUIFxDbpvm87plT4LzCCo+otoLSgCF+k51mwf0/Y3/IvhuskKdfSEYomRdBVCy19sY5c75oh5f471OFMfAehtFoOYdiRw7 [email protected]
==> default: Running provisioner: shell...
default: Running: inline script
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 1966
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2021
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2076
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2109

[jeremyfelt]

Hi @ricker07 - I'd try a vagrant up without the provisioning just to ensure the box loads properly. Not much of this looks familiar from the VVV provisioning, and if laravel/homestead isn't an Ubuntu box, I could see some conflicts.

[ericandrewlewis]

Pretty sure this is symptomatic of mitchellh/vagrant#1673, which unfortunately is unresolved.

[ricker07]

thank you guys for your help. sorry for late reply. i'm just beginner in
laravel with vagrant. :)

On 8 January 2015 at 12:51, Jeremy Felt [email protected] wrote:

Closed #517 https://github.com/Varying-Vagrant-Vagrants/VVV/issues/517.

—
Reply to this email directly or view it on GitHub
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/517#event-215713290
.

[twisty7867]

There is a simple fix for the issue (assuming you don't really need a TTY); essentially you need to remove the mesg n command from /root/.proflle. You can copy and paste exactly what you need from an explanation I published on my site.

[ricker07]

thanks sir @twisty7867 for the help. :)

On 28 April 2015 at 04:48, twisty7867 [email protected] wrote:

There is a simple fix for the issue (assuming you don't really need a
TTY); essentially you need to remove the mesg n command from
/root/.proflle. You can copy and paste exactly what you need from an
explanation I published on my site
http://foo-o-rama.com/vagrant--stdin-is-not-a-tty--fix.html.

—
Reply to this email directly or view it on GitHub
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/517#issuecomment-96815175
.

[jeremyfelt]

This will be fixed/merged in #633 pending license approval. Thanks all!

[siddhanthm]

I still have the same error. I am using Mac OS though

[kluplau]

+1 on OSX

[mateuslopesbh]

+2 on OSX

[iondulgheru]

+1 in OSX

[mateuslopesbh]

Insert this line in Vagrantfile, was resolved for me.

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

[twisty7867]

@mateuslopesbh that can have some other deleterious effects, according to mitchellh/vagrant#1673 (not necessarily in a VVV context). The code I proposed absolutely fixes this issue, regardless of host OS, for a standard Ubuntu 14.04 install. If anyone continuing to experience this issue could share with me their Vagrantfile and a screen grab of the output during vagrant up, I'll be happy to help troubleshoot.

[ViktorHaag]

Hey @twisty7867, I already have this in my Vagrantfile, and it seems I'm unable to put in your fix in combination with this existing declaration:

config.vm.provision :shell do |shell|
   shell.path = 'setup.sh'
end

I don't know much at all about vagrant or Ruby, and am unsure how to include both your fix and my existing stuff here (which was put there by someone else no longer around)? I tried two blocks (put yours first), and then I get an error that says "fix-no-tty provisioner could not be found"... I tried putting your stuff into this same block, and I get "only of path and inline may be set"... Can you assist?

[twisty7867]

The "could not be found" error is because your version of Vagrant is too old. You need at least 1.7 to support a named provisioner. You could edit the first line of my code to look more like the one you pasted, e.g. just copy and past the first line of above and replace the first line of mine with it, changing |shell| to |s|.

[ViktorHaag]

On OSX, and when I vagrant --version, I get Vagrant 1.7.4 ... this seems to be the latest build available for OSX.

[nkasvosve]

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

did it. Thanks

[stenio123]

@nkasvosve 's solution worked for me, just added that line in the Vagrantfile, inside the loop "Vagrant.configure(2) do |config|. Thank you!

[mewben]

@nkasvosve Thanks.. worked for me...

[walkr]

@twisty7867 Thank you! It worked for me too.

[thierrymarianne]

In a nutshell, inserting the following line into a Vagrantfile breaks the vagrant ssh command (when used in combination with --command option for instance, which I've experienced personally)

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

See https://github.com/mitchellh/vagrant/issues/1673#issuecomment-158742618

There is also the possibility to set config.ssh.pty to true in the Vagrantfile but there seems to be other side-effects:

config.ssh.pty = true

See https://github.com/mitchellh/vagrant/issues/1673#issuecomment-34521728 and http://docs.vagrantup.com/v2/vagrantfile/ssh_settings.html

On the contrary, the next provisioning script provided by @twisty7867 seems to fix the issue without visible regression as far as I can tell from a very restricted usage.

config.vm.provision "fix-no-tty", type: "shell" do |s|
    s.privileged = false
    s.inline = "sudo sed -i '/tty/!s/mesg n/tty -s \\&\\& mesg n/' /root/.profile"
end

See http://foo-o-rama.com/vagrant--stdin-is-not-a-tty--fix.html

[imuller]

@nkasvosve, worked for me. Thanks!

[leetschau]

@thierrymarianne "fix-no-tty" worked for me. Thanks!

[gidantribal]

Still the same problem for me too, this fixes the issue:

    config.vm.provision "fix-no-tty", type: "shell" do |s|
      s.privileged = false
      s.inline = "sudo sed -i '/tty/!s/mesg n/tty -s \\&\\& mesg n/' /root/.profile"
    end

[rahulswimmer]

I ve started exploring Hyperledger and i have encountered a problem while installing vagrant. Following is the error i encountered after i used the command - 'vagrant up':

==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: ++ export DOCKER_STORAGE_BACKEND=
==> default: ++ DOCKER_STORAGE_BACKEND=
==> default: ++ cd /hyperledger/devenv
==> default: ++ ./setup.sh
==> default: fatal: Not a git repository (or any parent up to mount point /hyper
ledger)
==> default: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM no
t set).
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

What should i do?

[christian-weiss]

@thierrymarianne thanks for your "fix-no-tty"-snipped. Works very well. Even on OSX.

[ghost]

@rahulswimmer did you ever find a solution to that problem? I am having the same issue

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.