RTNETLINK answers: File exists - Unable to bring bond0 up
Hi
After changing IP address on the server i restarted network service and it doesnt come up .
~]# systemctl start network
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[ ~]# jouralctl -xe
bash: jouralctl: command not found...
[ ~]# journalctl -xe
Jul 08 12:09:15 network[18745]: Bringing up interface bond0
Jul 08 12:09:15 tnetwork[18745]: [FAILED]
Jul 08 12:09:15 network[18745]: RTNETLINK answers: File exi
Jul 08 12:09:15 network[18745]: RTNETLINK answers: File exi
Jul 08 12:09:15 network[18745]: RTNETLINK answers: File exi
Jul 08 12:09:15 t systemd[1]: network.service: control proces
Jul 08 12:09:15 te systemd[1]: Failed to start LSB: Bring up/d
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit network.service has failed.
-- The result is failed.
Jul 08 12:09:15 systemd[1]: Unit network.service entered fa
Jul 08 12:09:15 systemd[1]: network.service failed.
Jul 08 12:09:15 polkitd[3077]: Unregistered Authentication
lines 1456-1478/1478 (END)
Responses
You could have a configuration file entry wrong. If you didn't put the bond interface down before changing the config, then the live system doesn't match the config file so this sort of thing is expected. In that situation I just find it easier to reboot, but you could put all the relevant interfaces down, unload bonding, and try again.
It also wouldn't be correct to start the network service if you're using NetworkManager to manage the devices. You would need to put the interface down, edit the file, make NM aware of new changes with nmcli con reload, then put the interface up again. If using NM, it's probably just easier to use the nmtui config interface.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
