Hi guys,
I have just installed Fedora 17 and tried to play with KVM virtualization. Before setting up new vm I set up bridge interface and after that I was unable to restart network service. Always drops an error:
[root@aleks network-scripts]# systemctl restart network.service
Job failed. See system journal and 'systemctl status' for details.
I still have access to the internet but since this scares me a little bit I decided to reinstall OS completely before I put more effort to KVM settings.
On freshly installed Fedora 17 the same issue. Cannot restart network service.
Here's the snippet from journalctl -a
Oct 27 17:01:00 aleks chronyd[788]: Source 91.121.92.90 offline
Oct 27 17:01:00 aleks chronyd[788]: Source 62.146.78.144 offline
Oct 27 17:01:00 aleks chronyd[788]: Source 37.59.115.231 offline
Oct 27 17:01:00 aleks chronyd[788]: Source 85.91.1.180 offline
Oct 27 17:01:01 aleks /USR/SBIN/CROND[3562]: (root) CMD (run-parts /etc/cron.hourly)
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3565]: starting 0anacron
Oct 27 17:01:01 aleks anacron[3572]: Anacron started on 2012-10-27
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3574]: finished 0anacron
Oct 27 17:01:01 aleks anacron[3572]: Will run job `cron.daily' in 7 min.
Oct 27 17:01:01 aleks anacron[3572]: Will run job `cron.weekly' in 27 min.
Oct 27 17:01:01 aleks anacron[3572]: Will run job `cron.monthly' in 47 min.
Oct 27 17:01:01 aleks anacron[3572]: Jobs will be executed sequentially
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3576]: starting mcelog.cron
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3580]: finished mcelog.cron
Oct 27 17:01:01 aleks dhclient[3520]: DHCPACK from 192.168.0.1 (xid=0x3764ffac)
Oct 27 17:01:01 aleks dhclient[3520]: bound to 192.168.0.14 -- renewal in 1529 seconds.
Oct 27 17:01:01 aleks NetworkManager[718]: <info> (p4p1): DHCPv4 state changed preinit -> reboot
Oct 27 17:01:01 aleks NetworkManager[718]: <info> address 192.168.0.14
Oct 27 17:01:01 aleks NetworkManager[718]: <info> prefix 24 (255.255.255.0)
Oct 27 17:01:01 aleks NetworkManager[718]: <info> gateway 192.168.0.1
Oct 27 17:01:01 aleks NetworkManager[718]: <info> nameserver '194.168.4.100'
Oct 27 17:01:01 aleks NetworkManager[718]: <info> nameserver '194.168.8.100'
Oct 27 17:01:01 aleks NetworkManager[718]: <info> Activation (p4p1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct 27 17:01:01 aleks NetworkManager[718]: <info> Activation (p4p1) Stage 5 of 5 (IPv4 Commit) started...
Oct 27 17:01:01 aleks avahi-daemon[700]: Joining mDNS multicast group on interface p4p1.IPv4 with address 192.168.0.14.
Oct 27 17:01:01 aleks avahi-daemon[700]: New relevant interface p4p1.IPv4 for mDNS.
Oct 27 17:01:01 aleks avahi-daemon[700]: Registering new address record for 192.168.0.14 on p4p1.IPv4.
Oct 27 17:01:02 aleks NetworkManager[718]: <info> (p4p1): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct 27 17:01:02 aleks NetworkManager[718]: <info> Policy set 'System br0' (p4p1) as default for IPv4 routing and DNS.
Oct 27 17:01:02 aleks NetworkManager[718]: <info> Activation (p4p1) successful, device activated.
Oct 27 17:01:02 aleks NetworkManager[718]: <info> Activation (p4p1) Stage 5 of 5 (IPv4 Commit) complete.
Oct 27 17:01:02 aleks network[3277]: Bringing up interface p4p1: [ OK ]
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks systemd[1]: network.service: control process exited, code=exited status=1
Oct 27 17:01:02 aleks systemd[1]: Unit network.service entered failed state.
Oct 27 17:01:03 aleks iscsi[3614]: Starting iscsi: iscsiadm: No records found
Oct 27 17:01:03 aleks iscsi[3614]: [ OK ]
Oct 27 17:01:03 aleks dbus-daemon[796]: Starting iscsi (via systemctl): [ OK ]
Oct 27 17:01:03 aleks chronyd[788]: Source 91.121.92.90 online
Oct 27 17:01:03 aleks chronyd[788]: Source 62.146.78.144 online
Oct 27 17:01:03 aleks chronyd[788]: Source 37.59.115.231 online
Oct 27 17:01:03 aleks chronyd[788]: Source 85.91.1.180 online
Any ideas what's wrong. This is literally first thing I did after the OS install.
Cheers,
Aleks
I have just installed Fedora 17 and tried to play with KVM virtualization. Before setting up new vm I set up bridge interface and after that I was unable to restart network service. Always drops an error:
[root@aleks network-scripts]# systemctl restart network.service
Job failed. See system journal and 'systemctl status' for details.
I still have access to the internet but since this scares me a little bit I decided to reinstall OS completely before I put more effort to KVM settings.
On freshly installed Fedora 17 the same issue. Cannot restart network service.
Here's the snippet from journalctl -a
Oct 27 17:01:00 aleks chronyd[788]: Source 91.121.92.90 offline
Oct 27 17:01:00 aleks chronyd[788]: Source 62.146.78.144 offline
Oct 27 17:01:00 aleks chronyd[788]: Source 37.59.115.231 offline
Oct 27 17:01:00 aleks chronyd[788]: Source 85.91.1.180 offline
Oct 27 17:01:01 aleks /USR/SBIN/CROND[3562]: (root) CMD (run-parts /etc/cron.hourly)
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3565]: starting 0anacron
Oct 27 17:01:01 aleks anacron[3572]: Anacron started on 2012-10-27
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3574]: finished 0anacron
Oct 27 17:01:01 aleks anacron[3572]: Will run job `cron.daily' in 7 min.
Oct 27 17:01:01 aleks anacron[3572]: Will run job `cron.weekly' in 27 min.
Oct 27 17:01:01 aleks anacron[3572]: Will run job `cron.monthly' in 47 min.
Oct 27 17:01:01 aleks anacron[3572]: Jobs will be executed sequentially
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3576]: starting mcelog.cron
Oct 27 17:01:01 aleks run-parts(/etc/cron.hourly)[3580]: finished mcelog.cron
Oct 27 17:01:01 aleks dhclient[3520]: DHCPACK from 192.168.0.1 (xid=0x3764ffac)
Oct 27 17:01:01 aleks dhclient[3520]: bound to 192.168.0.14 -- renewal in 1529 seconds.
Oct 27 17:01:01 aleks NetworkManager[718]: <info> (p4p1): DHCPv4 state changed preinit -> reboot
Oct 27 17:01:01 aleks NetworkManager[718]: <info> address 192.168.0.14
Oct 27 17:01:01 aleks NetworkManager[718]: <info> prefix 24 (255.255.255.0)
Oct 27 17:01:01 aleks NetworkManager[718]: <info> gateway 192.168.0.1
Oct 27 17:01:01 aleks NetworkManager[718]: <info> nameserver '194.168.4.100'
Oct 27 17:01:01 aleks NetworkManager[718]: <info> nameserver '194.168.8.100'
Oct 27 17:01:01 aleks NetworkManager[718]: <info> Activation (p4p1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct 27 17:01:01 aleks NetworkManager[718]: <info> Activation (p4p1) Stage 5 of 5 (IPv4 Commit) started...
Oct 27 17:01:01 aleks avahi-daemon[700]: Joining mDNS multicast group on interface p4p1.IPv4 with address 192.168.0.14.
Oct 27 17:01:01 aleks avahi-daemon[700]: New relevant interface p4p1.IPv4 for mDNS.
Oct 27 17:01:01 aleks avahi-daemon[700]: Registering new address record for 192.168.0.14 on p4p1.IPv4.
Oct 27 17:01:02 aleks NetworkManager[718]: <info> (p4p1): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct 27 17:01:02 aleks NetworkManager[718]: <info> Policy set 'System br0' (p4p1) as default for IPv4 routing and DNS.
Oct 27 17:01:02 aleks NetworkManager[718]: <info> Activation (p4p1) successful, device activated.
Oct 27 17:01:02 aleks NetworkManager[718]: <info> Activation (p4p1) Stage 5 of 5 (IPv4 Commit) complete.
Oct 27 17:01:02 aleks network[3277]: Bringing up interface p4p1: [ OK ]
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks network[3277]: RTNETLINK answers: File exists
Oct 27 17:01:02 aleks systemd[1]: network.service: control process exited, code=exited status=1
Oct 27 17:01:02 aleks systemd[1]: Unit network.service entered failed state.
Oct 27 17:01:03 aleks iscsi[3614]: Starting iscsi: iscsiadm: No records found
Oct 27 17:01:03 aleks iscsi[3614]: [ OK ]
Oct 27 17:01:03 aleks dbus-daemon[796]: Starting iscsi (via systemctl): [ OK ]
Oct 27 17:01:03 aleks chronyd[788]: Source 91.121.92.90 online
Oct 27 17:01:03 aleks chronyd[788]: Source 62.146.78.144 online
Oct 27 17:01:03 aleks chronyd[788]: Source 37.59.115.231 online
Oct 27 17:01:03 aleks chronyd[788]: Source 85.91.1.180 online
Any ideas what's wrong. This is literally first thing I did after the OS install.
Cheers,
Aleks