Error starting network service
I want to switch from network manager to conventional networking which is always on. But the network service fails to start.
[root@localhost ~]# systemctl stop NetworkManager.service
[root@localhost ~]# systemctl disable NetworkManager.service
Removed /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service.
Removed /etc/systemd/system/multi-user.target.wants/NetworkManager.service.
Removed /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service.
[root@localhost ~]# systemctl enable network.service
network.service is not a native service, redirecting to systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable network
[root@localhost ~]# systemctl start network.service
Job for network.service failed because the control process exited with error code.
See "systemctl status network.service" and "journalctl -xe" for details.
[root@localhost ~]#
This is what I see when running the suggested command:
Apr 18 20:43:46 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has begun starting up.
Apr 18 20:43:46 localhost.localdomain systemd-sysctl[3089]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
Apr 18 20:43:46 localhost.localdomain systemd-sysctl[3089]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
Apr 18 20:43:46 localhost.localdomain systemd-sysctl[3089]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or directory
Apr 18 20:43:46 localhost.localdomain systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
-- Subject: Unit systemd-rfkill.socket has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-rfkill.socket has finished starting up.
--
-- The start-up result is done.
Apr 18 20:43:46 localhost.localdomain kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Apr 18 20:43:46 localhost.localdomain kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Apr 18 20:43:46 localhost.localdomain kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Apr 18 20:43:46 localhost.localdomain kernel: cfg80211: failed to load regulatory.db
Apr 18 20:43:47 localhost.localdomain network[3058]: Bringing up loopback interface: [ OK ]
Apr 18 20:43:47 localhost.localdomain network[3058]: Bringing up interface enp1s0:
Apr 18 20:43:52 localhost.localdomain network[3058]: Determining IP information for enp1s0... failed; no link present. Check cable?
Apr 18 20:43:52 localhost.localdomain network[3058]: [FAILED]
Apr 18 20:43:55 localhost.localdomain kernel: e1000e: enp2s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Apr 18 20:43:58 localhost.localdomain NET[3325]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
Apr 18 20:43:59 localhost.localdomain network[3058]: Bringing up interface enp2s0: [ OK ]
Apr 18 20:43:59 localhost.localdomain systemd-sysctl[3348]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
Apr 18 20:43:59 localhost.localdomain systemd-sysctl[3348]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file ...