Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or directory
Apr 02 15:54:16 machine_name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
Apr 02 15:54:16 machine_name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
Apr 02 15:54:16 machine_name systemd[1]: network.service: Control process exited, code=exited status=1
Apr 02 15:54:16 machine_name systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
Apr 02 15:54:16 machine_name audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/sy
Apr 02 15:54:16 machine_name systemd[1]: network.service: Unit entered failed state.
systemctl status network.service returns the following
"job for network.service failed because the control process exited with error code."