LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   /etc/init.d/network restart (failed) (https://www.linuxquestions.org/questions/linux-newbie-8/etc-init-d-network-restart-failed-4175559158/)

windstory 11-17-2015 11:09 PM
/etc/init.d/network restart (failed)
 
My box is Scientific Linux 7.1 x64 and I got network problem.

Quote:
[root@localhost ~]# service network restaqrt
Usage: /etc/init.d/network {start|stop|status|restart|reload|force-reload}
[root@localhost ~]# /etc/init.d/network restart
Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journ alctl -xn' for details.
[FAILED]
Quote:
~] # nmcli c load /etc/sysconfig/network-scripts/ifcfg-eth0
could not load file '/etc/sysconfig/network-scripts/ifcfg-eth0'
Any helpful comment would be appreciated.
Thanks in advance.

berndbausch 11-17-2015 11:29 PM
[QUOTE=windstory;5451262]My box is Scientific Linux 7.1 x64 and I got network problem.

Code:
Restarting network (via systemctl): Job for network.service failed.
See 'systemctl status network.service' and 'journalctl -xn' for details.
Did you do that?

Quote:
Originally Posted by windstory (Post 5451262)
Any helpful comment would be appreciated.
Check ifcfg-eth0.

windstory 11-17-2015 11:46 PM
2 Attachment(s)
About 'systemctl status network.service' and 'journalctl -xn', I did it as shown at the attached photo but I could not understand what this means.
Attachment 20070

And I've checked the ifcfg-eth0, but I could not find anything weird.

Attachment 20071

berndbausch 11-18-2015 12:01 AM
When you can copy text, don't use pictures for posting text.

And if you don't understand an error message, try Google.

I believe the RNETLINK message means that the interface wasn't shut down correctly, thus it couldn't be started. Perhaps the nmcli message has the same cause. But I would have to google that myself to get clarity.

As a first step, I would try systemctl stop network, then check IP addresses, then systemctl start network. But as I said, google.

windstory 11-18-2015 12:53 AM
After 'systemctl stop network' I check ip with 'ifconfig', but there is not ip for inet4.
And I did 'systemctl start network', then shows 'Job for network.service failed. See 'systemctl satus network.service' and 'Journalctl -xn' for details.'.

windstory 11-18-2015 01:12 AM
'ifdown eth0 and ifup eth0' has a problem.

Quote:
[root@localhost ~] ifdown ethO
Could not load file '/etc/sysconfig/network-sc ripts/ifcfg-eth0'
Could not load file '/etc/sysconfig/network-sc ripts/ifcfg-eth0'
ERROR : [/etc/sysconfig/network-sc ripts/ifdown-eth] Device has MAC address 00:00:00:00:00:00 00:15:5D:00:02:02, instead of configured address 00:15:5D:00:02:002. Ignoring,
[root@localhost ~] ifup ethO
Could not load file '/etc/sysconfig/netwo rk-scripts/ifcfg-eth0'
Could not load file '/etc/sysconfig/netwo rk-scripts/ifcfg-eth0'
ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device has different MAC address than expected,ignoring.

berndbausch 11-18-2015 03:05 AM
Quote:
Originally Posted by windstory (Post 5451298)
'ifdown eth0 and ifup eth0' has a problem.
Code:
Device has MAC address 00:00:00:00:00:00 00:15:5D:00:02:02, instead of configured address 00:15:5D:00:02:002. Ignoring,
I think this output is a bit garbled, but it says that the MAC address in your ifcfg-eth0 is different from the actual MAC address of eth0.

You can take the HWADDRESS line out of ifcfg-eth0 or correct it.

windstory 11-18-2015 03:17 AM
Thanks, I corrected it and solved.

jugfudjustin 12-14-2020 03:25 AM
configure Restarting networking
 
old :

/etc/init.d/network-manager restart
Restarting networking (via systemctl): networking.service.

new :

/etc/init.d/networking restart
Restarting networking (via systemctl): networking.service.


All times are GMT -5. The time now is 04:06 PM.