Almalinux UPGRADE fails on reboot

[baronn]

Hello Everyone,

Had/have a few old boxes lying around still running centos7. So took the plunge and decided to upgdare using elavate on one of them to see how smoothly the process went/goes.

Initially it went to stage3 then rebooted after which we couldnt access the box (maybe was still doing updates as per the documentation advice) so we left it alone for a while. Sure enough we got the upgraded to almalinux email

On trying to connect the to box (vps) we couldnt. It was not accepting connections. Data center showed it was 'alive' and running BUT just couldnt access it. Loggin in via PAM allowed us to access and after a while 'faffing' around with the firewal, reviewing logs (none of which showed an issue OR culprit) we stumbled upon restarting the newtwork with:

systemctl restart network

That instantly did the trick! so we thought all was well. Today did the usual yum updates etc and decided to do a graceful reboot just for good measure... and bam box offline again!

Doing the: systemctl restart network instantly brought it back up! so appears there is an underlying issue which we cannot find. Any ideas where we should be looking? what it might be?

When its running, its running smoothly...

 

[andrew.n]

NetworkManager installed?

 

[baronn]

NetworkManager installed?

thats the funny thing. YES but:
systemctl status NetworkManager results in:

failed to start NetworkManager.service: Unit NetworkManager .service not found

BUT the using: systemctl restart network it all starts working instantly! concerened that if the 'box' ever descideds to rebbot itself then it will be offline UNTIL we can run that: systemctl restart network again. Thats not ideal or workable...

 

[quietFinn]

What I did was:
yum remove NetworkManager
and then:
systemctl enable network

 

[HostNoc]

HI

systemctl stop NetworkManager

systemctl disable NetworkManager

service network restart

Regards
SAM

 

[quietFinn]

Better make sure that network is enabled

if you run;
systemctl is-enabled network
you should get:
network.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig network --level=5
enabled

If it's not enabled it does not start after reboot.

 

[baronn]

What I did was:
yum remove NetworkManager

Doesnt actually do anything:
No match for argument: NetworkManager
Dependencies resolved.
Nothing to do.
Complete!

systemctl enable network

@quietFinn Thank you. This did it for me. Works a treat. Not sure why this isnt included (or maybe a bug?) when using eleavte to upgade? so I guess I will have to include this in steps for the other boxes we will be upgrading.

HI

systemctl stop NetworkManager

systemctl disable NetworkManager

service network restart

Regards
SAM

@HostNoc As far as this goes it gives the output:

systemctl stop NetworkManager
Failed to stop NetworkManager.service: Unit NetworkManager.service not loaded.
systemctl disable NetworkManager
Failed to disable unit: Unit file NetworkManager.service does not exist.
service network restart
Restarting network (via systemctl): [ OK ]

BUT it doesnt actually enable anything (weird even though the output says OK?)

Better make sure that network is enabled

if you run;
systemctl is-enabled network
you should get:
network.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig network --level=5
enabled

If it's not enabled it does not start after reboot.

@quietFinn None of that helped APART from: systemctl is-enabled network which helped to identify IF it was enabled OR disabled when trying to get the darn thing to stay on

 

[quietFinn]

Starting (or restarting) network does not enable it, it must be enabled or networking does not start on boot.

I know very little about networking, but this I have learned, with a little help from cPanel support.