Posts by charyouz

Well, that was stupid of me.

Did not run the fix6to7 upgrade script, since I didn't want to run anything when I had the original error.

Running it now fixed the issue.

Thank you very much for the fast help!

First updated from OMV5 -> OMV6, no issues. Ran the fix5to6 script and went through some settings on the web GUI to see that everything seemed to work fine.

Then decided to update to OMV7:

omv-upgrade -> no issues.

omv-release-upgrade gave this issue:

Unpacking wireless-tools (30~pre9-14) over (30~pre9-13.1) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-FVkzV3/46-firmware-ath9k-htc_1.4.0-108-gd856466+dfsg1-1.3+deb12u1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looked that the linux is now bookworm and I can still access the shares and ssh as well as all the docker containers, but when I try to access the omv webGUI, I get 502 bad gateway when I try to login.

running dpkg --configure -a didn't help

Any ideas on what to do?

Edit:

searched the forums a bit more and found a similar older issue where this helped:

sudo dpkg -P firmware-ath9k-htc

Helped for me too, now there are no errors, can run omv-upgrade without issues, but the 502 Bad gateway persists.

from another thread, found that this fixed that issue:

omv-salt stage run deploy

Error now changed to 500 when I try to log in. (running that command gave no errors)

Edit2:

nginx error logs show this:

[crit] 1066#1066: *9 connect() to unix:/run/php/php7.4-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.246, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock:", host: "192.168.1.91", referrer: "http://192.168.1.91/"