“system-cloudinit@-var-tmp-hostname.yml.service 的作业失败,因为超出了配置的资源限制”

Posted

技术标签:

【中文标题】“system-cloudinit@-var-tmp-hostname.yml.service 的作业失败,因为超出了配置的资源限制”【英文标题】:"Job for system-cloudinit@-var-tmp-hostname.yml.service failed because a configured resource limit was exceeded" 【发布时间】:2015-08-29 14:44:54 【问题描述】:

我开始使用 Rancher 和 Vagrant 来创建我的本地开发环境。我已经完成的步骤:

    我已经安装了 VirtualBox。

    我用

    下载并安装了适用于 linux 的 Vagrant 包
    sudo rpm -i vagrant_1.7.2_x86_64.rpm  
    

流浪版本:

vagran --version  
Vagrant 1.7.2  

我从 GitHub 克隆了 Rancher 存储库:

git clone git@github.com:rancherio/rancher.git  

其中有 Vagrant 文件。执行后:

sudo vagrant up  

这是我得到错误的步骤,我得到了这个:

==> rancher: Box 'coreos-alpha' could not be found. Attempting to find and install...
rancher: Box Provider: virtualbox
rancher: Box Version: >= 308.0.1
==> rancher: Loading metadata for box 'http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json'
rancher: URL: http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json
==> rancher: Adding box 'coreos-alpha' (v709.0.0) for provider: virtualbox
rancher: Downloading: http://alpha.release.core-os.net/amd64-usr/709.0.0/coreos_production_vagrant.box
rancher: Calculating and comparing box checksum...
==> rancher: Successfully added box 'coreos-alpha' (v709.0.0) for 'virtualbox'!
==> rancher: Importing base box 'coreos-alpha'...
==> rancher: Matching MAC address for NAT networking...
==> rancher: Checking if box 'coreos-alpha' is up to date...
==> rancher: Setting the name of the VM:rancher_rancher_1434213461241_51852
==> rancher: Clearing any previously set network interfaces...
==> rancher: Preparing network interfaces based on configuration...
rancher: Adapter 1: nat
rancher: Adapter 2: hostonly
==> rancher: Forwarding ports...
rancher: 8080 => 8080 (adapter 1)
rancher: 22 => 2222 (adapter 1)
==> rancher: Running 'pre-boot' VM customizations...
==> rancher: Booting VM...
==> rancher: Waiting for machine to boot. This may take a few minutes...
rancher: SSH address: 127.0.0.1:2222
rancher: SSH username: core
rancher: SSH auth method: private key
rancher: Warning: Connection timeout. Retrying...
rancher: 
rancher: Vagrant insecure key detected. Vagrant will automatically replace
rancher: this with a newly generated keypair for better security.
rancher: 
rancher: Inserting generated public key within guest...
rancher: Removing insecure key from the guest if its present...
rancher: Key inserted! Disconnecting and reconnecting using new SSH key...
==> rancher: Machine booted and ready!
==> rancher: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!  

systemctl start system-cloudinit@-var-tmp-hostname.yml.service  

Stdout from the command:  



Stderr from the command:

Job for system-cloudinit@-var-tmp-hostname.yml.service failed because a configured resource limit was exceeded. See "systemctl status system-cloudinit@-var-tmp-hostname.yml.service" and "journalctl -xe" for details.  

然后当我访问 localhost:8080 时,没有安装 Rancher UI。

【问题讨论】:

你能不能登录到你的docker实例并在失败后执行systemctl status system-cloudinit@-var-tmp-hostname.yml.service 我得到了这个:system-cloudinit@-var-tmp-hostname.yml.service 加载:未找到(原因:没有这样的文件或目录)活动:不活动(死) 【参考方案1】:

我也遇到了同样的问题, 然后我配置“config.rb”,将更新通道更改为稳定,如下所示,

$update_channel='stable'

然后再次销毁并升级 vagrant coreos,

$ vagrant destroy
$ vagrant up

终于,vagrant运行成功了~

【讨论】:

【参考方案2】:

看到这个GitHub issue,它是由 CoreOS 709.0.0 中的 systemd 更新引起的。

就像提到的小镇一样,您可以使用 beta 通道切换回旧版本的 CoreOS。或者你可以等待这个this pull request 被合并到 vagrant-coreos 中,这样你就可以固定一个特定的版本来使用。

【讨论】:

以上是关于“system-cloudinit@-var-tmp-hostname.yml.service 的作业失败,因为超出了配置的资源限制”的主要内容,如果未能解决你的问题,请参考以下文章