seems vagrant trigger is trying to do something in the box and thats failing
If you want to delete the box, you can use the virtualbox gui, delete it then vagrant destroy should just update the state. alvaro FRITZ!Box <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, Nov 3, 2017 at 5:36 PM, Clinton Gallagher < [email protected]> wrote: > // None of the Vagrant scripts will run: `vagrant up`, `vagrant halt`, > `vagrant suspend`, and `vagrant destroy` > // nothing runs they all get stopped with the following output error > message > > $ vagrant destroy > ==> default: Running triggers before destroy... > ==> default: Executing command "vagrant ssh -c vagrant_destroy"... > ==> default: stdin is not a tty > ==> default: Command execution finished. > The local command "vagrant ssh -c 'vagrant_destroy'" returned a failed exit > code or an exception. The error output is shown below: > > stdin is not a tty > > // I wrote the # comments when I found the following config.vm.provision > statement in the Vagrant file: > > # CSG 2017-11-1 > # This was here before finding and reading the same at > # http://foo-o-rama.com/vagrant--stdin-is-not-a-tty--fix.html > # but this alleged fix to the "stdin is not a tty" message does not > resolve 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 > > // Does that config.vm.provision statement go somewhere special in the > Vagrant file? > // How else can this be disabled on the ubuntu/trusty64 box? > > // All up to date > $ vagrant plugin list > vagrant-hostupdater (1.0.2) > vagrant-share (1.1.9, system) > vagrant-triggers (0.5.3) > > // I have VM log files but they are lengthy and impossible for me to > interpret > > > On Thursday, November 2, 2017 at 9:09:27 PM UTC-5, Clinton Gallagher wrote: >> >> x64 Windows 10 Pro >> VirtualBox v5.1.30 >> Vagrant v2.0.0 >> >> Vagrant is FUBAR >> Apparently I made the mistake of updating ubuntu/trusty64 that is pushing >> Vagrant around like a bully. >> >> Now Vagrant will not halt or delete or much of anything else as there is >> some conflict with stdin is not a tty >> I've scowered the www and there are scant solutions. One of which is >> already written into the Vagrant file which I have no idea how it got there >> but it does not prevent stdin is not a tty either. >> >> I know its not a Vagrant error but there should be a reliable way to >> resolve this matter and IMO it should come from Hashicorp as they and they >> alone know Vagrant inside and out and how Vagrant interacts with boxes such >> as ubuntu/trusty64. >> >> That said if Hashicorp continues to ignore this matter then what? >> >> >> -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/7128ca00-aa87-4b61-9925-6497ab7196ea%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/7128ca00-aa87-4b61-9925-6497ab7196ea%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewxq_hh1MCx%3DGgQvm9MY2oo9ZV1CQcdf4yuP%2BDAsDEmow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
