LoginSignup
1
1

More than 5 years have passed since last update.

vagrant up 時に出る network.service のエラー

Last updated at Posted at 2017-05-10

はじめに

network.serviceのエラーに関して、色々いじった結果解決できたので備忘録として。
ちなみに内容は全くわかってないため、保証はできません。

エラー文

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
  default: Adapter 1: nat
  default: Adapter 2: hostonly
==> default: You are trying to forward to privileged ports (ports <= 1024). Most
==> default: operating systems restrict this to only privileged process (typically
==> default: processes running as an administrative user). This is a warning in case
==> default: the port forwarding doesn't work. If any problems occur, please try a
==> default: port higher than 1024.
==> default: Forwarding ports...
  default: 80 (guest) => 3000 (host) (adapter 1)
  default: 443 (guest) => 443 (host) (adapter 1)
  default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
  default: SSH address: 127.0.0.1:2222
  default: SSH username: vagrant
  default: SSH auth method: private key
  default: Warning: Remote connection disconnect. Retrying...
  default: Warning: Connection reset. Retrying...
  default: Warning: Remote connection disconnect. Retrying...
  default: Warning: Connection reset. Retrying...
  default: Warning: Remote connection disconnect. Retrying...
  default: Warning: Connection reset. Retrying...
  default: Warning: Remote connection disconnect. Retrying...
  default: Warning: Connection reset. Retrying...
  default: Warning: Remote connection disconnect. Retrying...
  default: Warning: Connection reset. Retrying...
  default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
[default] GuestAdditions 5.1.18 running --- OK.
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Down the interface before munging the config file. This might
# fail if the interface is not actually set up yet so ignore
# errors.
/sbin/ifdown 'enp0s8'
# Move new config into place
mv -f '/tmp/vagrant-network-entry-enp0s8-1494406484-0' '/etc/sysconfig/network-scripts/ifcfg-enp0s8'
# attempt to force network manager to reload configurations
nmcli c reload || true

# Restart network
service network restart

Stdout from the command:

Restarting network (via systemctl): [FAILED]

Stderr from the command:

Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.

解決方法

vagrantへssh接続し、/etc/sysconfig/network-scripts/ifcfg-enp0s9のファイルを削除(移動の方がいいかもしれません)する。

$ vagrant ssh
[vagrant@localhost ~]$ sudo rm -rf /etc/sysconfig/network-scripts/ifcfg-enp0s9
[vagrant@localhost ~]$ sudo systemctl start network.service

移動の場合は以下のコマンドかな?

[vagrant@localhost ~]$ sudo mv /etc/sysconfig/network-scripts/ifcfg-enp0s9 ~/ifcfg-enp0s9
[vagrant@localhost ~]$ sudo systemctl start network.service

最後に

責任は持てませんが、誰かのお役に立てることを祈っております。

なお、下記のwarningに関しては解決しておりません(笑)

  default: Warning: Remote connection disconnect. Retrying...
  default: Warning: Connection reset. Retrying...

また、訂正すると思います。

1
1
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
1
1