Network access broken every update/reboot

no_connection

Patron
Joined
Dec 15, 2013
Messages
480
scale_brokennetwork.PNG

Going into network interfaces and remove config from any interface or vlan(preferably unused) resets it to working order with IP/conf still in place.
I assume this is not a feature but a bug, and since it's a NAS a pretty serious one.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,702
if you do ifconfig bnx2 up does that make it work?

If so, a tunable could work to do it automatically at startup.
 

no_connection

Patron
Joined
Dec 15, 2013
Messages
480
Using that command did not work(error out), and if I do up for the interface it completes but do not fix the problem. I did not dig further but I think the interfaces are already up and shuold work fine (have to verify later).
 

no_connection

Patron
Joined
Dec 15, 2013
Messages
480
Manually bringing them up after boot did not work but putting it in pre-init script/job works. Thanks!
It does look like some script don't want to wait until interfaces are up and running and breaks, but running ifconfig enp3s0f0 up it in a script before ensures it happen before that so it works. I would call this a bug in a NAS appliance/server, the user should not need to jump through hoops to get basic functionality working. I would suggest some integrity script running to ensure network functionality.

Fun fact if you enter configure network interfaces in shell and then quit with q it interrupts network for UI a short while even tho you didn't do anything.
 

KrisBee

Wizard
Joined
Mar 20, 2017
Messages
1,288
@no_connection In the case shown in your first post, what happens if you enter the shell and use systemctl restart ix-netif.service ? Is your network config restored?
 

no_connection

Patron
Joined
Dec 15, 2013
Messages
480
@KrisBee I just tested and yes it looks like it works to bring it up.
Should I add back the startup script or keep it as is and see if it gets fixed with future updates? I have iLO so it's a thing I can do for testing.
 

KrisBee

Wizard
Joined
Mar 20, 2017
Messages
1,288
Your choice, but I added that systemctl restart command as a post-install command via the UI when trying to make some progress with the recent ALPHA release. SCALE has a long way to go.

I'm not an IT specialist, but SCALE is not using debian's std ifupdown in conjuction with /etc/network/interfaces configuration. Nor do they seem to be using ifupdown2 with vlan aware bridges nor openvswitch, so network config is a bridge per vlan. Neither are Linux bonds present in the network config.
 

kbumsik

Cadet
Joined
Aug 29, 2020
Messages
1
I had exactly same problem. As @KrisBee mentioned I fixed the problem by adding systemctl restart ix-netif.service post-init command in Data Protection -> Init/Shutdown Scripts.
It's a little bit weird that it falls under "Data Protection" section though.
 
Top