yes with the command i gave you before you can remove that line. On Fri, Nov 3, 2017 at 10:18 PM, Clinton Gallagher < clinton.s.gallag...@gmail.com> wrote:
> I deleted the box from the VM GUI and then ran vagrant destroy that did > nothing. > I used a vagrant up command which rebuilt the box with a new instance of a > box.. > When I used vagrant up my WordPress website will load from the browser on > the Windows desktop. I'm even able to login which is very insightful as the > db connection to the old db remained. > > Apparently Vagrant made a backup it used to make a new instance of a VM > box that allows WordPress to reconnect to the db. I can also see the db > with PhpMyAdmin > > The stdin is not a tty is still present though. > > When I run vagrant global-status I see a new ID for the box so I run > vagrant halt 597e485 and the VM is still running so the excercise seems to > have been futile. > > $ vagrant halt 597e485 > ==> default: Running triggers before halt... > ==> default: Executing command "vagrant ssh -c vagrant_halt"... > ==> default: stdin is not a tty > ==> default: Command execution finished. > The local command "vagrant ssh -c 'vagrant_halt'" returned a failed exit > code or an exception. The error output is shown below: > > stdin is not a tty > > Is there not a way to go directly into Ubuntu and hack it so it doesn't > want to believe stdin is controlled by a tty? > > > 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 vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/736fbd43-79f3-43ad-bf09-b7e6f5d6f4a5%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/736fbd43-79f3-43ad-bf09-b7e6f5d6f4a5%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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ex9JxvVeMSPAO4T0jndSgX8hBzKnQb7p%3DWkrDK0syugDA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
