Failed to restart network.service: Unit not found.
Failed to restart network.service: Unit not found.
This CentOS 7.5.1804 server has a loopback and ethernet network cards. Upon rebooting the server for maintenance of an unrelated application (OpManager), the network service will not initialize. When attempting to restart network service I get the error:
Failed to restart network.service: Unit not found. Here is the current ifconfig output: I did not change any network scripts configuration. The ethernet network interface is "ens33"
There is no GUI this server is CLI only.
At one point I was able to manually start the interface making it show up under ifconfig command output, but it is not showing up now. Rebooting does not resolve this issue. Why the network service is crashing after a simple reboot is beyond me... Any ideas?
Failed to restart network.service: Unit not found. Here is the current ifconfig output: I did not change any network scripts configuration. The ethernet network interface is "ens33"
There is no GUI this server is CLI only.
At one point I was able to manually start the interface making it show up under ifconfig command output, but it is not showing up now. Rebooting does not resolve this issue. Why the network service is crashing after a simple reboot is beyond me... Any ideas?
- Attachments
-
- ifconfig-output-1.PNG (7.76 KiB) Viewed 34457 times
Re: Failed to restart network.service: Unit not found.
Code: Select all
# rpm -qf /etc/init.d/network
initscripts-9.49.46-1.el7.x86_64
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Failed to restart network.service: Unit not found.
It is and install fails:
Re: Failed to restart network.service: Unit not found.
You need to set up your network interface to be able to connect to the internet to be able to use yum.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Failed to restart network.service: Unit not found.
How do I do that?
Alternatively can I install the software from the install ISO?
Alternatively can I install the software from the install ISO?
Re: Failed to restart network.service: Unit not found.
You can use the iso image if you loopback mount it (or write it to a DVD and have a DVD drive) on one of the mountpoints listed in /etc/yum.repos.d/CentOS-Media.repo (or add your own directory to the list in that file). Then use yum --disablerepo=\* --enablerepo=c7-media reinstall initscripts
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Failed to restart network.service: Unit not found.
Followed these steps:
https://www.itzgeek.com/how-tos/linux/c ... g-dvd.html
By mounting the local repo this way the system would allow me to install initscripts. Reinstall command failed.
Now the ethernet interface came up and I can ping the server.
Thank you for all the help!
https://www.itzgeek.com/how-tos/linux/c ... g-dvd.html
By mounting the local repo this way the system would allow me to install initscripts. Reinstall command failed.
Now the ethernet interface came up and I can ping the server.
Thank you for all the help!
Re: Failed to restart network.service: Unit not found.
There are two parts:
* Configuration used by services is stored in files. It must be in proper syntax that the service reads.
There were GUI/TUI tools, where you set/select options and the tool writes files in correct syntax.
* Logical network configuration. No tool can tell whether the logic is valid. However, ...
It is very common to define the logic of the entire subnet in one server and set all client machines to
load their configuration from that server at boot. That is DHCP.