![]() |
network.service
Hello and thank you for viewing my thread. I don't now what I'm doing.
I have installed CentOS 7.4.1708 onto my VPS, updated to the latest kernel and attempted to install WHM/cPanel. During the installation I received a colorful red message that said cPanel does not support NetworkManager enabled systems. The installation cannot proceed. Please consult your system documentation to remove NetworkManager, replacing it with the network.service I then removed NetworkManager and attempted to Code:
systemctl start network.service After entering systemctl status network.service I got this output Code:
● network.service - LSB: Bring up/down networking If you do not know the solution to this problem but have a good resource for understanding CentOS networking better please feel free to post that too. Thanks |
You could configure a network interface config file (/etc/sysconfig/network-scripts/ifcfg-***) by hand as explained here
https://wiki.centos.org/FAQ/CentOS7#...b1ff9954bec881 This CentOS 6 guide should still be relevant for manual network configuration as well... http://www.serverlab.ca/tutorials/li...work-settings/ |
BTW, make sure that network.service is enabled as well, so that it is active at boot
Code:
systemctl enable network.service https://documentation.cpanel.net/dis...etwork+Manager |
Quote:
Thank you the cPanel documentation did it even though I do not know what it was I was doing. Editing the ifcfg-eth0 and ifcfg-eth0:0 THEN enabling AND starting (What's the difference?) network.services seemed to do fix the problem of: network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2017-10-30 23:30:43 EDT; 20min ago Docs: man:systemd-sysv-generator(8) Process: 7765 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) But now I can no longer SSH to my server. Was I suppose to configure a network interface file before I stopped networkmanager and switched over to network.service? The cPanel directions did not state that. There is one thing I did notice my ifcfg-eth0 and ifcfg-eth0:0 files did not contain a NM_CONTROLLED value that was according to the cPanel instructions suppose to be set to no "NM_CONTROLLED=no". So I added this to both eth0, eth0:0, and ifcfg-lo. So I turned off network manager, edited the configuration files according to that documentation then enabled and started network.service but that left me unable to ssh to my server (currently vnc). Any ideas? Would configure a network interface file do anything? Thanks |
Have you checked to see if there is an SSH server listening on port 22 (or whatever you configured it on)? Are you trying to reach it by a particular IP address, and is it still the same?
Code:
ip address |
Simply starting a .service unit won't create the symlinks to get the unit started at boot.
From the systemctl man page Quote:
|
1 Attachment(s)
Quote:
|
Your config files (ifcfg-eth0 and ifcfg-eth0:0) don't match the network device node name present (ens3)!
|
Quote:
|
The network device node name(s) can be got via ifconfig...
Code:
/sbin/ifconfig -a Code:
ip link Code:
ip address |
If the relevant interface is ens0, then the matching configuration file naming would be ifcfg-ens0
|
So I have to change:
ifcfg-eth0 to ifcfg-lo and ifcfg-eth0:0 to ifcfg-ens3 ??? |
I changed ifcfg-eth0 to ifcfg-ens3 but am still not able to SSH
|
Quote:
Show the output of Code:
ip a |
1 Attachment(s)
This is the output of ip a
|
All times are GMT -5. The time now is 07:28 PM. |