• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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