- r - 以节省内存的方式增长 data.frame
- ruby-on-rails - ruby/ruby on rails 内存泄漏检测
- android - 无法解析导入android.support.v7.app
- UNIX 域套接字与共享内存(映射文件)
我最近在更新Laravel环境或Windows 10的一部分时遇到了一些错误,所以在经过大量的尝试和错误之后,我决定删除所有内容并从头开始。所以现在我有了新的 VirtualBox、Vagrant、Laravel/Homestead 盒子和 Homestead 本身。
但是,我确实遇到了这个错误:
$ vagrant up
Bringing machine 'homestead-7' up with 'virtualbox' provider...
==> homestead-7: Importing base box 'laravel/homestead'...
==> homestead-7: Matching MAC address for NAT networking...
==> homestead-7: Checking if box 'laravel/homestead' is up to date...
==> homestead-7: Setting the name of the VM: homestead-7
==> homestead-7: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 8000 (Errno::EADDRNOTAVAIL)
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `block in is_port_open?'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `block in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:19:in `is_port_open?'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:248:in `port_check'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:121:in `[]'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:121:in `block in handle'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:257:in `block in with_forwarded_ports'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:253:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:253:in `with_forwarded_ports'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:98:in `handle'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:42:in `block in call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:567:in `lock'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:41:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/env_set.rb:19:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/provision.rb:80:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builder.rb:116:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/runner.rb:66:in `block in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/unil/busy.rb:19:in `busy'
下面还有大约 100 行。您知道似乎是什么问题以及如何解决它吗?我正在阅读有关 RoR 的内容,但我没有设法解决它。
最佳答案
这似乎是新的 vagrant 1.9.3 的问题(参见 https://github.com/mitchellh/vagrant/issues/8395)
有些人能够 fix与以下
I managed to make the 1.9.3 version working by rewritten all my Vagrantfile(s) and adding the
host_ip: "127.0.0.1"
parameter for each of the "forwarded_port" network configuration.E.g.:
config.vm.network "forwarded_port", guest: 22, host: 1022, host_ip: "127.0.0.1", id: 'ssh'
对于 Homestead,您可以编辑文件 Homestead/scripts/homestead.rb
# Use Default Port Forwarding Unless Overridden
unless settings.has_key?("default_ports") && settings["default_ports"] == false
default_ports.each do |guest, host|
unless settings["ports"].any? { |mapping| mapping["guest"] == guest }
config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true
end
end
end
# Add Custom Ports From Configuration
if settings.has_key?("ports")
settings["ports"].each do |port|
config.vm.network "forwarded_port", guest: port["guest"], host: port["host"], protocol: port["protocol"], host_ip: "127.0.0.1", auto_correct: true
end
end
关于php - Laravel Vagrant 不工作 - Errno::EADDRNOTAVAIL,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/42955086/
应用程序在本地主机上工作正常。但是当它连接到服务器时出现错误。 我通过端口 22 连接服务器 这是错误 Error: listen EADDRNOTAVAIL Error: listen EADDRN
我真的遇到了这个问题。我在 Windows 机器上(具有管理员权限),我想开始使用 vagrant 设置我的工作环境。 问题是我遇到了错误(如下)并且我找不到任何解决方案......我正在使用最新的虚
我有一个简单的 Node.js 应用程序,无法连接到 SQL 数据库。 Web 服务器是 Azure Web App,运行 node.js 并使用 Tedious对于 SQL。DB 是 Azure S
突然间(上周工作正常)我在尝试使用 Nodemailer 发送电子邮件时开始收到发送邮件时出错:错误:连接 EADDRNOTAVAIL . 该错误确实很模糊,我不太确定 EADDRNOTAVAIL 的
我正在尝试使用以下脚本使用 node.js 下载文件: var http = require('http'); var fs = require('fs'); var file = fs.create
我刚开始使用 NodeJS 开发 Web 应用程序,我的应用程序有一个问题我不知道如何解决。 应用程序(我们使用 expressjs)在我的本地机器上运行平稳,但是当我们将它部署到我们的开发服务器进行
我在 172.16.1.218 上运行了以下 node.js 服务器: var net=require('net'); var server = net.createServer(function (
我在我的应用程序中出现了似乎无法重现的故障。我有一个失败的 TCP 套接字连接,应用程序试图重新连接它。在尝试重新连接的第二次 connect() 调用中,我得到一个错误结果,错误结果为 errno
我正在尝试通过 Appstore 的 IPv6 支持,但遇到了一些问题。 我关注了苹果公会Supporting IPv6 DNS64/NAT64 Networks ,我的代码: const char
(已在 Centos 6.5 和 Centos 7 上测试过) 如果您在 linux 中使用 INADDR_ANY 和 0 端口在 connect() 之前调用 bind() 那么 bind() 的临
我的公司发布了一个用于特殊用途的特殊 TCP 堆栈,我的任务是实现符合 RFC793 的关闭序列。其中一个单元测试有一个服务器在特殊的 TCP 堆栈之上工作,与一个普通的 Linux TCP 客户端通
我的 Node 应用程序正在监听端口 8080。当我添加时 app.listen(port,'50.30.217.289'); 我可以从浏览器访问该应用程序。但是,当我将 IP 地址替换为 EC2 实
我已经在 OpenShift 上开发了一个 nodejs 服务器,现在我正尝试在 Heroku 上为一个新项目制作相同类型的服务器。 这是我的服务器的最小代码: var http = require(
我最近在更新Laravel环境或Windows 10的一部分时遇到了一些错误,所以在经过大量的尝试和错误之后,我决定删除所有内容并从头开始。所以现在我有了新的 VirtualBox、Vagrant、L
我在我的笔记本电脑上安装了相当全新的 OpenSUSE,并尝试测试一个全新的 React 应用程序。 我从 create-react-app 站点运行了以下命令: npx create-rea
我用 node.js 编写了以下代码来访问 Twitter Streaming API。如果我 curl 下面的 URL,它就会起作用。但是,我无法让它与我的代码一起工作。 var https = r
我在 centos 6.3 服务器上使用 rail for teambox,实际上这只是在实际应用之前的试错。 我正在使用 2 个运行在相同 centos 版本和精确副本上的虚拟机,VM2 只运行远离
我在我的服务器中安装了 Nginx 和 Node.js。 当我尝试运行我的 node.js 文件时,我收到一个错误: node.js:201 throw e; // process.ne
我正在运行一个应该托管在本地服务器上的 Node 应用程序。 目前,我只发送一个明文响应。 const http = require('http'); var server = http.create
我正在尝试让一个nodejs应用程序在Azure上运行(它在Heroku上运行得很好)。 在应用程序上运行 npm start 后,出现以下错误: Error: connect EADDRNOTAVA
我是一名优秀的程序员,十分优秀!