network.service start faild

[goldensafe002]

]# systemctl restart network
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.


# systemctl status network.service
● 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 Sun 2024-04-07 09:23:25 CST; 40s ago
Docs: man:systemd-sysv-generator(8)
Process: 224644 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Apr 07 09:23:25 hg-p-ebsdb01 network[224644]: RTNETLINK answers: File exists
Apr 07 09:23:25 hg-p-ebsdb01 network[224644]: RTNETLINK answers: File exists
Apr 07 09:23:25 hg-p-ebsdb01 network[224644]: RTNETLINK answers: File exists
Apr 07 09:23:25 hg-p-ebsdb01 network[224644]: RTNETLINK answers: File exists
Apr 07 09:23:25 hg-p-ebsdb01 network[224644]: RTNETLINK answers: File exists
Apr 07 09:23:25 hg-p-ebsdb01 network[224644]: RTNETLINK answers: File exists
Apr 07 09:23:25 hg-p-ebsdb01 systemd[1]: network.service: control process exited, code=exited status=1
Apr 07 09:23:25 hg-p-ebsdb01 systemd[1]: Failed to start LSB: Bring up/down networking.
Apr 07 09:23:25 hg-p-ebsdb01 systemd[1]: Unit network.service entered failed state.
Apr 07 09:23:25 hg-p-ebsdb01 systemd[1]: network.service failed.


cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.9 (Maipo)

[TrevorH]

Use `journalctl -u network` to see messages older than the ones that you see using status.

[jlehtone]

The network.service is not the default. I'd check:

Code: Select all

chkconfig --list
systemctl status NetworkManager.service

... in case that was forgotten.