Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No live threads left #8125

Closed
iDVB opened this issue Dec 15, 2016 · 20 comments

Comments

Projects
None yet
@iDVB
Copy link

commented Dec 15, 2016

Vagrant version

Vagrant 1.9.1

Host operating system

macOS Sierra (10.12.1)

Guest operating system

ALL/ANY

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "hashicorp/precise64"
end

Debug output

Error Msg

Expected behavior

VM should have installed and launched

Actual behavior

Error `join': No live threads left. Deadlock?

Steps to reproduce

  1. vagrant init hashicorp/precise64
  2. vagrant up
@james-pearce-aerian

This comment has been minimized.

Copy link

commented Dec 16, 2016

I'm having a similar issue details below

Vagrant version - Vagrant 1.9.1

Host operating system - OS X El Capitan (10.11.6)

Guest operating system - ALL/ANY

Error - No live threads left. Deadlock?

@chrisroberts

This comment has been minimized.

Copy link
Member

commented Dec 16, 2016

@james-pearce-aerian can you provide a gist of vagrant up --debug output? Thanks!

@jbw976

This comment has been minimized.

Copy link

commented Dec 21, 2016

I am able to reproduce this on Vagrant 1.9.1 for Mac OS X El Capitan 10.11.4, when attempting to vagrant up the env provided in https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/vagrant.

Full debug output can be found here, let me know if I can gather any more information:
https://gist.github.com/jbw976/cfc5b7997cb106724d16db5df65f65c2

@danbenson

This comment has been minimized.

Copy link

commented Dec 23, 2016

Getting the same on Vagrant 1.9.1, MacOS Sierra 10.12.2 on vagrant up.

@sbleon's workaround below got me up and running again. Thanks!

@danbenson

This comment has been minimized.

Copy link

commented Dec 28, 2016

@ddavtian

This comment has been minimized.

Copy link

commented Dec 30, 2016

Same here

@sbleon

This comment has been minimized.

Copy link

commented Jan 6, 2017

I had this problem as well, but I found a workaround. TL;DR: uninstall and reinstall vagrant.

Here's the full sequence of what I did.

  1. Upgraded to macOS Sierra.
  2. vagrant tried to install Virtualbox on vagrant up, even though I already had it and it was working.
  3. I reinstalled vagrant.
  4. I got the "No live threads left" error.
  5. I uninstalled vagrant (using the uninstall script on the installer image).
  6. I reinstall vagrant.
  7. All is well.
@maniarab

This comment has been minimized.

Copy link

commented Jan 6, 2017

I had the same issue with the following version combinations:
OS: OS X El Capitan (10.11.6)
Vagrant: 1.9.1
Virtualbox: 5.0.30
Ruby: 2.3.3p222 (2016-11-21 revision 56859) [x86_64-darwin15]

image

What ended up working for me was the following combination:
OS: OS X El Capitan (10.11.6)
Vagrant: 1.8.5
Virtualbox: 5.0.20
Ruby: 2.3.3p222 (2016-11-21 revision 56859) [x86_64-darwin15]

Not exactly sure why we're having this issue with the latest versions of Vagrant & Virtualbox. I'd love to hear what others think and also if my combination works on their machine.

@bitozoid

This comment has been minimized.

Copy link

commented Jan 12, 2017

Does not work on linux:

  • vagrant 1.9.1
  • virtualbox 5.1.10
  • ruby 2.1.0

Works downgrading vagrant to 1.8.7.

@chrisroberts

This comment has been minimized.

Copy link
Member

commented Jan 12, 2017

I am still working on getting a local repro of this so I can track down the problem. Thank you everyone for the information provided. Anyone else encountering this error, please post your host OS and version, Vagrant version and Ruby version if not running from the official Vagrant installer.

@sbleon What version of Vagrant were you upgrading from when the issue presented?

@mikepsinn

This comment has been minimized.

Copy link

commented Jan 17, 2017

Getting this on
OS: Windows 10
Vagrant: 1.9.1
Virtualbox: 5.1.14

@skelethan

This comment has been minimized.

Copy link

commented Jan 20, 2017

Same issue. Tried uninstall / re-install & no success. Up next, downgrading to 1.8.5 (last working version)

OS: Win 10
Vagrant: 1.9.1
VB: 5.1.2
Guest: CentOS

Debug output
https://gist.github.com/skelethan/fff84a49b2fd7d20f1b6ad603cfa9f96

@giovino

This comment has been minimized.

Copy link

commented Jan 24, 2017

I had same issue as described above.

OS: OS X (10.11.6)
Vagrant 1.9.1
VB: 5.1.14
Guest: hashicorp/precise64
Ruby:

  • /opt/vagrant/embedded/include/ruby-2.2.0/ruby
  • /opt/vagrant/embedded/include/ruby-2.2.0/x86_64-darwin13/ruby

Note: previous to getting this error I did the following:

  • Upgraded: VirtualBox 5.1.13 to 5.1.14
  • Upgraded: Vagrant 1.8.6 to 1.9.1

To the best of my knowledge Vagrant 1.8.6 was working as expected but hadn't used it in a few months.

I was able to resolve the problem by using the uninstall.tool in the Vagrant installer and then reinstalled Vagrant. Issue is now resolved.

@gitttt

This comment has been minimized.

Copy link

commented Feb 6, 2017

Same issue here on Win7:

  • vagrant 1.9.1
  • Virtualbox 5.1.14

Downgraded to 1.8.7 and now it works again.

@Jimadine

This comment has been minimized.

Copy link

commented Mar 6, 2017

The problem continues in vagrant 1.9.2 (Win 7, VirtualBox 5.1.14). Tried the uninstall/reinstall trick but it didn't help.

@xiaods

This comment has been minimized.

Copy link

commented Mar 27, 2017

Tried the uninstall/reinstall trick but it didn't help. The problem continues in vagrant 1.9.3 (Macos, VirtualBox 5.1.14).

@xiaods

This comment has been minimized.

Copy link

commented Mar 27, 2017

$ vagrant up
Validating Plugins...
Validating User Config...
Validating Installer Checksum...
Using DC/OS Installer: installers/dcos/dcos_generate_config-1.8.8.sh
Using DC/OS Config: etc/config-1.8.yaml
Validating Machine Config...
Configuring VirtualBox Host-Only Network...
Bringing machine 'm1' up with 'virtualbox' provider...
Bringing machine 'a1' up with 'virtualbox' provider...
Bringing machine 'p1' up with 'virtualbox' provider...
Bringing machine 'boot' up with 'virtualbox' provider...
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/batch_action.rb:126:in `join': No live threads left. Deadlock? (fatal)
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/batch_action.rb:126:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/batch_action.rb:65:in `each'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/batch_action.rb:65:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:287:in `block (2 levels) in batch'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:282:in `tap'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:282:in `block in batch'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:281:in `synchronize'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:281:in `batch'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/commands/up/command.rb:88:in `execute'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/cli.rb:42:in `execute'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:308:in `cli'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/bin/vagrant:127:in `<main>'
@xiaods

This comment has been minimized.

Copy link

commented Mar 28, 2017

we need clear /opt/vagrant and /usr/local/bin/vagrant, then vagrant works like a charm. please take a note.

@DeploymentBoy

This comment has been minimized.

Copy link

commented Apr 11, 2019

This is a generic error, you may try to execute ngrok as executable first before trying from vagrant share

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.