Vagrant Error on VAGRANT SHARE - "No live threads left. Deadlock?"

Vagrant
1

Hi there.

I seem to have the same problem as this poster from January 2021:

I’m running through the Share an Environment steps and when I get to the point of vagrant share it throws an error No live threads left. Deadlock?.

  • Host is Windows 10
  • ngrok version 3.0.3
  • Vagrant 2.2.19
  • Ubuntu 18.04.3 LTS for the client VM

I tested ngrok http 80 on its own and this would not work under GitBash (it just seems to pause for a very long time) but works under the standard Windows cmd environment.

When I run vagrant share the output is as follows:

==> default: Creating Vagrant Share session... Traceback (most recent call last): 5: from C:/HashiCorp/Vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/bin/vagrant:231:in ’
4: from C:/HashiCorp/Vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/environment.rb:290:in cli' 3: from C:/HashiCorp/Vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/cli.rb:67:in execute’
2: from C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/share.rb:122:in execute' 1: from C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:170:in start_share’
C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:170:in `join’: No live threads left. Deadlock? (fatal)
2 threads, 2 sleeps current:0x000001b0be1aefd0 main thread:0x000001b0b6bbedc0

  • #<Thread:0x000001b0b870c410 sleep_forever>
    rb_thread_t:0x000001b0b6bbedc0 native:0x0000000000000174 int:0
    C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:170:in join' C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:170:in start_share’
    C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/share.rb:122:in execute' C:/HashiCorp/Vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/cli.rb:67:in execute’
    C:/HashiCorp/Vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/lib/vagrant/environment.rb:290:in cli' C:/HashiCorp/Vagrant/embedded/gems/2.2.19/gems/vagrant-2.2.19/bin/vagrant:231:in ’
  • #<Thread:0x000001b0be9c88b0 C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:280 sleep_forever>
    rb_thread_t:0x000001b0be1adc20 native:0x0000000000000360 int:0
    depended by: tb_thread_id:0x000001b0b6bbedc0
    C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:281:in pop' C:/Users/bratt/.vagrant.d/gems/2.7.4/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:281:in block in start_connect_info_watcher’`

I have attempted to uninstall Vagrant and reinstall it; but this has not resolved the problem.

Any suggestions are welcome!

1 Like
2

As of 2023 03 04, I am seeing this same issue. My configuration is similar:

  • Host: Windows 10 Pro 22H2
  • Vagrant: 2.2.34
  • Vagrant Plugin: vagrant-share (2.0.0, global)
  • ngrok: version 3.1.1
  • Vagrant Provider: Virtual Box 7.0.6
  • VBox Guest: Ubuntu 18.04.3 LTS

My next steps are:

  • upgrade the Virtual Box Guest Additions so that release levels match.
  • enable the local HTTPS port.

If either resolves the problem, I’ll report that here.

Any other suggestions for resolution most welcome. I’ve posted this issue on serverfault.com, as well.
DVH

3

As of 2023 03 24; 13:45, I have updated the ServerFault.com entry and report here that the proposed actions had no impact on the error. It remains as described. There has (apparently) been no input from Hashicorp or any other source.

4

As of 23.04.16 - similar observation as above.
I am at ngrok 3.2.2, vagrant 2.3.4 - and port forwarding into VM works without vagrant.

With vagrant share, I get the same error messages as reported above.
.vagrant.d/gems/2.7.6/gems/vagrant-share-2.0.0/lib/vagrant-share/command/ngrok/share.rb:170:in `join’: No live threads left. Deadlock? (fatal)

Maybe a bug in the plugin?