Hello, I’m trying to get startet with Vargrant and followed the official Getting Started tutorial. Everything works fine to the point Share an Environment.
I’m using Vagrant 2.2.14 on Ubuntu 20.04.1 LTS with VirtualBox 6.1.10. ngrok is installed as version 2.3.35, as well as the vagrant-share plugin.
When I try to run vagrant share, I get the error No live threads left. Deadlock?.
Here is the complete output:
bj@uxbuntu:~/vagrant_getting_started$ vagrant share
==> default: Detecting network information for machine...
default: Local machine address: 127.0.0.1
default:
default: Note: With the local address (127.0.0.1), Vagrant Share can only
default: share any ports you have forwarded. Assign an IP or address to your
default: machine to expose all TCP ports. Consult the documentation
default: for your provider ('virtualbox') for more information.
default:
default: Local HTTP port: 4567
default: Local HTTPS port: disabled
default: Port: 2222
default: Port: 4567
==> default: Creating Vagrant Share session...
Traceback (most recent call last):
5: from /opt/vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/bin/vagrant:205:in `<main>'
4: from /opt/vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/environment.rb:290:in `cli'
3: from /opt/vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/cli.rb:67:in `execute'
2: from /home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:2267:in `execute'
1: from /home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1738:in `start_share'
/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1738:in `join': No live threads left. Deadlock? (fatal)
2 threads, 2 sleeps current:0x0000000003b81860 main thread:0x000000000201df20
* #<Thread:0x000000000204b2b0 sleep_forever>
rb_thread_t:0x000000000201df20 native:0x00007fbce46c7740 int:0
/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1738:in `join'
/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1738:in `start_share'
/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:2267:in `execute'
/opt/vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/cli.rb:67:in `execute'
/opt/vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/lib/vagrant/environment.rb:290:in `cli'
/opt/vagrant/embedded/gems/2.2.14/gems/vagrant-2.2.14/bin/vagrant:205:in `<main>'
* #<Thread:0x0000000003bfc720@/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1843 sleep_forever>
rb_thread_t:0x0000000003c190d0 native:0x00007fbcdd8cb700 int:0
depended by: tb_thread_id:0x000000000201df20
/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1844:in `pop'
/home/bj/.vagrant.d/gems/2.6.6/gems/vagrant-share-1.1.11/lib/vagrant-share/activate.rb:1844:in `block in start_connect_info_watcher'
I couldn’t find any solution on how to solve this problem when using vargrant share. Canon someone help me?