Open jessereynolds opened 10 years ago
Turns out I think I was having DNS issues of some sort when the above occurred.
I've the same issues when running multiple Vagrant processes at the same time for aws provider. E.g.
~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `getaddrinfo'~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `getaddrinfo': getaddrinfo: nodename nor servname provided, or not known (SocketError) (Excon::Errors::SocketError)
: ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `getaddrinfo'getaddrinfo: nodename nor servname provided, or not known (SocketError) (Excon::Errors::SocketError from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `connect'
)
: getaddrinfo: nodename nor servname provided, or not known (SocketError) from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:146:in `connect'
(Excon::Errors::SocketError from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `connect'
)
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:28:in `initialize'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:8:in `initialize'
.rb:146:in `connect'
~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `getaddrinfo' from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `connect'
~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `getaddrinfo': from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `new'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:28:in `initialize'
getaddrinfo: nodename nor servname provided, or not known (SocketError) ( from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:146:in `connect'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:8:in `initialize'
Excon::Errors::SocketError from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `socket'
)
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:28:in `initialize'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `new'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:8:in `initialize'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `socket'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `new'
: from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:106:in `request_call'
...
getaddrinfo: nodename nor servname provided, or not known (SocketError) from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
(Excon::Errors::SocketError)
from ~/.vagrant.d/gems/gems/vagrant-auto_network-1.0.2/lib/auto_network/action/request.rb:24:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:100:in `connect'
from ~/.vagrant.d/gems/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:146:in `connect'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
from ~/.vagrant.d/gems/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/socket.rb:28:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/ssl_socket.rb:8:in `initialize'
from ~/.vagrant.d/gems/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:404:in `socket'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder.rb:116:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:106:in `request_call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/mock.rb:47:in `request_call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `block in run'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/instrumentor.rb:25:in `request_call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:19:in `busy'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:15:in `request_call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:15:in `request_call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:15:in `request_call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:25 from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:224:in `action_raw'
0:in `request'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:199:in `block in action'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:561:in `lock'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185:in `call'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/idempotent.rb:26:in `error_call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185:in `action'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
from ~/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/provider.rb:32:in `state'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:501:in `state'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:273:in `rescue in request'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:144:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/vagrantfile.rb:79:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/vagrantfile.rb:79:in `machine'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:221:in `request'
from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:663:in `machine'
from ~/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/idempotent.rb:26:in `error_call'
from ~/.vagrant.d/gems/gems/vagrant-auto_network-1.0.2/lib/auto_network/action/filter_networks.rb:38:in `block in machines_for_env'
This is happening almost every time when I run 2-10 vagrant processes in the background.
Vagrant 1.8.1 with vagrant-aws (0.7.0).
Maybe one Vagrant shouldn't block the socket for another process? It's like I'm trying to run more than 25 instances at the same time (in parallel, separate Vagrant processes), but it's not possible more than that (btw. I've got limit of 200).
Update: I think this probably could mean I've reached the limit of 25 standard volumes, but it's weird method of saying that.
This was working a week or two ago. I'm not sure if this is an issue with vagrant-aws or something else...