{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/2430","repository_url":"https://api.github.com/repos/mitchellh/vagrant","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/2430/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/2430/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/2430/events","html_url":"https://github.com/mitchellh/vagrant/issues/2430","id":21710344,"number":2430,"title":"Restarting network (via systemctl):  [FAILED]","user":{"login":"kelbyers","id":1743077,"avatar_url":"https://avatars.githubusercontent.com/u/1743077?v=3","gravatar_id":"","url":"https://api.github.com/users/kelbyers","html_url":"https://github.com/kelbyers","followers_url":"https://api.github.com/users/kelbyers/followers","following_url":"https://api.github.com/users/kelbyers/following{/other_user}","gists_url":"https://api.github.com/users/kelbyers/gists{/gist_id}","starred_url":"https://api.github.com/users/kelbyers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kelbyers/subscriptions","organizations_url":"https://api.github.com/users/kelbyers/orgs","repos_url":"https://api.github.com/users/kelbyers/repos","events_url":"https://api.github.com/users/kelbyers/events{/privacy}","received_events_url":"https://api.github.com/users/kelbyers/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mitchellh/vagrant/labels/bug","name":"bug","color":"e11d21"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2013-10-28T18:29:08Z","updated_at":"2016-08-03T12:47:15Z","closed_at":"2013-12-08T18:27:50Z","body":"After upgrading from Vagrant 1.3.3 to 1.3.5 and upgrading vagrant-vmware-fusion from 2.0.5 to 2.0.8, my Fedora 19 guests get errors up starting:\r\n\r\nKels-MacBook-Pro:800 jxb2016$ vagrant reload vpre\r\n[vpre] Attempting graceful shutdown of VM...\r\nConnection to 192.168.254.193 closed by remote host.\r\n[vpre] Verifying vmnet devices are healthy...\r\n[vpre] Preparing network adapters...\r\n[vpre] Starting the VMware VM...\r\n[vpre] Waiting for the VM to finish booting...\r\n[vpre] The machine is booted and ready!\r\n[vpre] Forwarding ports...\r\n[vpre] -- 22 => 2222\r\n[vpre] Setting hostname...\r\nThe following SSH command responded with a non-zero exit status.\r\nVagrant assumes that this means the command failed!\r\n\r\nservice network restart\r\n\r\nStdout from the command:\r\n\r\nRestarting network (via systemctl):  [FAILED]\r\n\r\n\r\nStderr from the command:\r\n\r\nJob for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.\r\n\r\nKels-MacBook-Pro:800 jxb2016$ vagrant ssh vpre\r\nLast login: Mon Oct 28 12:30:44 2013 from url-fw03-websensedmz.homedepot.com\r\n[vagrant@pre ~]$ sudo systemctl status network.service\r\nnetwork.service - LSB: Bring up/down networking\r\n   Loaded: loaded (/etc/rc.d/init.d/network)\r\n   Active: failed (Result: exit-code) since Mon 2013-10-28 14:13:51 EDT; 7min ago\r\n  Process: 2030 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)\r\n\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com network[2030]: RTNETLINK answers: File exists\r\nOct 28 14:13:51 pre.p2v.vagrantup.com systemd[1]: network.service: control process exited, code=exited status=1\r\nOct 28 14:13:51 pre.p2v.vagrantup.com systemd[1]: Failed to start LSB: Bring up/down networking.\r\nOct 28 14:13:51 pre.p2v.vagrantup.com systemd[1]: Unit network.service entered failed state.\r\n[vagrant@pre ~]$ sudo journalctl -xn\r\n\\-- Logs begin at Mon 2013-08-05 17:58:43 EDT, end at Mon 2013-10-28 14:21:09 EDT. --\r\nOct 28 14:14:12 pre.p2v.vagrantup.com systemd[1]: Starting Stop Read-Ahead Data Collection...\r\n\\-- Subject: Unit systemd-readahead-done.service has begun with start-up\r\n\\-- Defined-By: systemd\r\n\\-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\r\n\\--\r\n\\-- Unit systemd-readahead-done.service has begun starting up.\r\nOct 28 14:14:12 pre.p2v.vagrantup.com systemd-journal[170]: Forwarding to syslog missed 22 messages.\r\n\\-- Subject: One or more messages could not be forwarded to syslog\r\n\\-- Defined-By: systemd\r\n\\-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\r\n\\-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/0027229ca0644181a76c4e92458afa2e\r\n\\--\r\n\\-- One or more messages could not be forwarded to the syslog service\r\n\\-- running side-by-side with journald. This usually indicates that the\r\n\\-- syslog implementation has not been able to keep up with the speed of\r\n\\-- messages queued.\r\nOct 28 14:14:12 pre.p2v.vagrantup.com systemd[1]: Started Stop Read-Ahead Data Collection.\r\n\\-- Subject: Unit systemd-readahead-done.service has finished start-up\r\n\\-- Defined-By: systemd\r\n\\-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\r\n\\--\r\n\\-- Unit systemd-readahead-done.service has finished starting up.\r\n\\--\r\n\\-- The start-up result is done.\r\nOct 28 14:16:38 pre.p2v.vagrantup.com avahi-daemon[734]: Invalid response packet from host 192.168.254.1.\r\nOct 28 14:19:08 pre.p2v.vagrantup.com avahi-daemon[734]: Invalid response packet from host 192.168.254.1.\r\nOct 28 14:20:54 pre.p2v.vagrantup.com sshd[2178]: Accepted publickey for vagrant from 192.168.254.1 port 51431 ssh2\r\nOct 28 14:20:54 pre.p2v.vagrantup.com systemd-logind[731]: New session 2 of user vagrant.\r\n\\-- Subject: A new session 2 has been created for user vagrant\r\n\\-- Defined-By: systemd\r\n\\-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\r\n\\-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat\r\n\\--\r\n\\-- A new session with the ID 2 has been created for the user vagrant.\r\n\\--\r\n\\-- The leading process of the session is 2178.\r\nOct 28 14:20:54 pre.p2v.vagrantup.com sshd[2178]: pam_unix(sshd:session): session opened for user vagrant by (uid=0)\r\nOct 28 14:21:01 pre.p2v.vagrantup.com sudo[2209]: vagrant : TTY=pts/0 ; PWD=/home/vagrant ; USER=root ; COMMAND=/bin/systemctl\r\nOct 28 14:21:09 pre.p2v.vagrantup.com sudo[2211]: vagrant : TTY=pts/0 ; PWD=/home/vagrant ; USER=root ; COMMAND=/bin/journalctl\r\n"},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/237227316","html_url":"https://github.com/mitchellh/vagrant/issues/2430#issuecomment-237227316","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/2430","id":237227316,"user":{"login":"lsim","id":5108355,"avatar_url":"https://avatars.githubusercontent.com/u/5108355?v=3","gravatar_id":"","url":"https://api.github.com/users/lsim","html_url":"https://github.com/lsim","followers_url":"https://api.github.com/users/lsim/followers","following_url":"https://api.github.com/users/lsim/following{/other_user}","gists_url":"https://api.github.com/users/lsim/gists{/gist_id}","starred_url":"https://api.github.com/users/lsim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lsim/subscriptions","organizations_url":"https://api.github.com/users/lsim/orgs","repos_url":"https://api.github.com/users/lsim/repos","events_url":"https://api.github.com/users/lsim/events{/privacy}","received_events_url":"https://api.github.com/users/lsim/received_events","type":"User","site_admin":false},"created_at":"2016-08-03T12:47:15Z","updated_at":"2016-08-03T12:47:15Z","body":"+1 in Vagrant 1.8.5 (centos 7 guest):\r\n\r\n==> default: Setting hostname...\r\nThe following SSH command responded with a non-zero exit status.\r\nVagrant assumes that this means the command failed!\r\n\r\n# Update sysconfig\r\nsed -i 's/\\(HOSTNAME=\\).*/\\1cis-latest/' /etc/sysconfig/network\r\n\r\n# Update DNS\r\nsed -i 's/\\(DHCP_HOSTNAME=\\).*/\\1\"cis-latest\"/' /etc/sysconfig/network-scripts/ifcfg-*\r\n\r\n# Set the hostname - use hostnamectl if available\r\necho 'cis-latest' > /etc/hostname\r\nif command -v hostnamectl; then\r\n  hostnamectl set-hostname --static 'cis-latest'\r\n  hostnamectl set-hostname --transient 'cis-latest'\r\nelse\r\n  hostname -F /etc/hostname\r\nfi\r\n\r\n# Remove comments and blank lines from /etc/hosts\r\nsed -i'' -e 's/#.*$//' -e '/^$/d' /etc/hosts\r\n\r\n# Prepend ourselves to /etc/hosts\r\ngrep -w 'cis-latest' /etc/hosts || {\r\n  sed -i'' '1i 127.0.0.1\\tcis-latest\\tcis-latest' /etc/hosts\r\n}\r\n\r\n# Restart network\r\nservice network restart\r\n\r\n\r\nStdout from the command:\r\n\r\n/bin/hostnamectl\r\nRestarting network (via systemctl):  [FAILED]\r\n\r\n\r\nStderr from the command:\r\n\r\nJob for network.service failed because the control process exited with error code. See \"systemctl status network.service\" and \"journalctl -xe\" for details.\r\n"}}
{"actor":{"display_login":"lsim"}}