openmediavault-firewall.service fails after 4to5 upgrade

Should i do additional preparations on OMV4 before starting update script? Specially due to Armbian?

I succeeded, finally. I stuck on a few probs and will give my solutions here, maybe they help to someone's concern (rpi armbian upgrade)

First of all, i didn't went the way in this script https://github.com/dleidert/openmediavault-upgrade/tree/4 but used that tutorial https://www.och-group.de/2020/…ult-4-x-nach-5-x-upgrade/ with some changes.

What i did...

Preparations:

# still on omv4 i uninstalled every service except ssh, even omv-extras and flashmemory

# in armbian-config i deleted everything except loop, not to get in huddle between network manager (armbian) and systemd-networkd

# set webGui network eth0 to use DNS 8.8.8.8 (temporarily)

# deleted mc_cesa in /etc/modules-load.d/@modules.conf (causing an issue in sudo systemctl list-units --failed)

# added that armbian repo to update armbian firmware (im my case from 5.27 to 22.02.2)

echo "deb [arch=arm64] http://apt.armbian.com $(lsb_release -cs) main" > /etc/apt/sources.list.d/armbian.list

apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 9F0E78D5

# sudo apt-get update && apt-get upgrade, of course. And reboot

# sudo apt-get purge openmediavault-cups openmediavault-dnsmasq openmediavault-docker-gui openmediavault-duplicati openmediavault-eyefi openmediavault-ldap openmediavault-letsencrypt openmediavault-mysql openmediavault-nginx openmediavault-openvpn openmediavault-pxe openmediavault-remotedesktop openmediavault-route openmediavault-shellinabox openmediavault-syncthing openmediavault-transmissionbt openmediavault-urbackup-server openmediavault-vdo openmediavault-virtualbox openmediavault-webdav

Updating

# sed -i "s/stretch/buster/g" /etc/apt/sources.list

sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/*

sed -i "s/arrakis/usul/g" /etc/apt/sources.list.d/*

sed -i "/[Dd]ocker/d" /etc/apt/sources.list.d/omvextras.list

sed -i "s/<mtu><\/mtu>/<mtu>0<\/mtu>/g" /etc/openmediavault/config.xml

rm -f /var/cache/openmediavault/archives/Packages

armbian="/etc/apt/sources.list.d/armbian.list"

[ -f "${armbian}" ] && echo "deb http://apt.armbian.com buster main buster-utils" | sudo tee ${armbian}

# sudo apt-get update && apt-get dist-upgrade -y

# reboot (with Rpi better in form of shutdown, power off, power on)

# sudo omv-salt deploy run nginx phpfpm (to get webgui working again)

Faced problems then:

sudo systemctl list-units --failed

● ifup@eth0.service loaded failed failed ifup for eth0

● networking.service loaded failed failed Raise network interfaces

● openmediavault-firewall.service loaded failed failed openmediavault iptables f

Webgui would not accept apply.

In particular the last issue makes the cat bite its own tail. OMV network runs openmediavault-firewall.sh, but i found no other way to change its entries than using webgui (system network). But upgrading itself wanted an "apply" (which fails), and the other option "revert" let me think of reverting the complete upgrading process. Omv-firstaid was no way, too, when trying to save changes it comes with "errno11, ressource temporarily unanvailable". No way out.

Solution here: At last i ignored my fears and "reverted". That's it. Even after rebooting system was still OMV5. And was editable in gui...

Except network firewall (firewall service was still failing). Tried deleting all entries (success) and editing new rules (saving ok), but again "apply"-prob.

Solution here: In docker settings (alltough NOT activated), iptables, i activated "legacy". Surprise, surprise, network firewall applied changes afterwards.

Did all entries in firewall again, saved, applied, rebooted... Everything is fine. "sudo systemctl list-units --failed" shows 0 failed services, updating (cli and gui) works.

On from here, installing oms-extras, plugins etc.....

Some of the steps may be cumbersome or unnecessary, the professionals here can better judge that.

Perhaps two suggestions.

1. it would be helpful if "revert" or "apply" would indicate which changes are concerned.

2. in settings-system-network-firewall there should be a hint about the necessary setting under docker iptables.

by the way, thanx for your job

Zitat von mi-hol

did you post a comment with your issues there too?

No, i didn't

Zitat von mi-hol

As Zoki writes in his signature "If you got help in the forum and want to give something back ..., write up your solution for others." applies to all forums

The post i linked to isn't in a forum. Should I offer to create one for the makers to be able to post a comment?

Zitat von Zoki

They have an E-mail. Give them a pointer to this thread and explain your problems / solutions in a few words.

done