Bad Gateway error after omv-release-upgrade

1. offizieller Beitrag

    Hi there, I did an upgrade via omv-release-upgrade (because there was no update in WebGUI available) and there was some error after the upgrade (some packages could not be loaded, as far as I remember). I assumed there was no upgrade done. But obviously some kind of upgrade was done.

    Unfortunately I cannot login to the WebGUI any more (502 - Bad Gateway). Commands like "omv-initsystem" or "omv-update" result in "Command not found"

    What is my problem with the system. Is there any possibility to repair?

    By the way: all shares are running, I can access data on the fileserver, and also docker containers (there is HomeAssistant running as container on the system) is working fine.

    Can someone help me to identify the problem?

    Thank you very much!

    Hi, thank you for reply!

    First of all the output as requested:

    And to the script: how should I use this?

    Code
    root@openmediavault:~# fix6to7
-bash: fix6to7: Kommando nicht gefunden.
    Zitat von loewes

    And to the script: how should I use this?

    Search the forum for that term.

    Zitat von loewes

    iU openmediavault

    Having a CAPITAL letter on that output is not a good sign.


    Since you ran the fix script, post the same output to see how your system is now:

    dpkg -l | grep openm

    • Neu

    Hi Soma,


    system is working currently (as mentioned above), but I still have the capital letters:

    Can you explain, what iU means?

    Thank you very much!

    • Neu
    Zitat von loewes

    Can you explain, what iU means?

    command line - What do the various dpkg flags like 'ii' 'rc' mean? - Ask Ubuntu


    It shows that it's installed and Unpacked.

    When in a "normal" status, it would show only ii


    When this happens, it usually shows a remark/warning on the output when running the update, saying that you need to run dpkg --configure -a




    I don't know what will happen by running that command.

    If you decide to do it, make sure you have a backup of the OS drive, in case it goes sideways.


    To see what apt shows, just post the output inside a CODE box of:
    sudo omv-upgrade

    • Neu

    both command end up with:


    • Neu

    The output shows dependencies issues which makes the packages staying in the unconfigured state and causes errors on the rest in cascade.


    I'll tag ryecoaaron hoping he can shed a light (and solution) to this.

    • Neu
    • Offizieller Beitrag

    The packages need to finish installing. Run sudo apt-get -f install

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Neu

    thank you, this happens when I run the command:

    • Neu
    • Offizieller Beitrag

    What is the output of: sudo cat /etc/default/nfs-kernel-server

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Neu

    This is the output:

    • Neu
    • Offizieller Beitrag

    On line 12, remove the last --nfs-version. Then try sudo apt-get -f install again.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Danke 1 Gefällt mir 1
    • Neu
    • Offizieller Beitrag

    Run the fix6to7 script.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Neu

    Maybe also post the output again of:

    dpkg -l | grep openm


    To confirm that everything is correct.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden