• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Failed to start network scripts

Franco

Regular Pleskian
Server operating system version
Almalinux 8.10
Plesk version and microupdate number
18.0.66
Hello,
I am running almalinux 8.10 with Plesk 18.00.66 (the latest, I believe) and I observe the following errors at boot:

network[870]: Bringing up interface eno16780032:
network[1050]: Error: Connection activation failed: No suitable device found for this connect>
network[870]: [FAILED]
systemd[1]: network.service: Control process exited, code=exited status=1
systemd[1]: network.service: Failed with result 'exit-code'.
Failed to start LSB: Bring up/down networking.
It is advised to switch to 'NetworkManager' instead for network management

And this is the result of systemctl status network:

network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated)
Active: failed (Result: exit-code) since Thu 2025-01-16 10:39:21 CET; 4 days ago
Docs: man:systemd-sysv-generator(8)

network[873]: WARN : [network] You are using 'network' service provided by 'network-scripts'
network[873]: WARN : [network] 'network-scripts' will be removed in one of the next major release
network[873]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network-scripts
network[873]: Bringing up loopback interface: [ OK ]
network[873]: Bringing up interface eno16780032:
network[1052]: Error: Connection activation failed: No suitable device found for this connect>
network[873]: [FAILED]
systemd[1]: network.service: Control process exited, code=exited status=1
systemd[1]: network.service: Failed with result 'exit-code'.
systemd[1]: Failed to start LSB: Bring up/down networking.

I saw a suggestion to 'reread' the IP addresses, which I did, and also to disable firewalld. No change to the above status.
Shall I migrate to NetworkManager and, if so, how, please?

Thank you for your attention and advice
 
Thanks. I found out that I am already running NetworkManager and that disabling/stopping network-scripts won't affect my system. It only gives those errors when checking the network.service status. I guess I would need some clean-up along the way, but things look ok for now.
 
Back
Top