Error when updating packet lists or doing an upgrade

  • I am back on 6.0.21-1 and ran those commands there.


    No change :(

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    0 selected / 39 total

    This tells me the client is getting the list of plugins. Hmmm... If you click Show/Hide Columns and enable the Name column, does it show anything?

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.6 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

  • Did you solve this ?

    I m having the same problem ,

    no visible plugins they are there 0 selected / 39 total

    Using 6.0.21-1

    Not solved.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • This tells me the client is getting the list of plugins. Hmmm... If you click Show/Hide Columns and enable the Name column, does it show anything?

    Enabling the Name column doesn't show anything.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • I really have no idea, the JSON files look all good. Are there any errors reported by the browser when you activate the browser dev tools. In FireFox the relevant tab is called 'Console'.

    Firefox Browser Console output when on the Plugins page.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    sudo omv-mkaptid

    This command needs an x at the end.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.6 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

  • This command needs an x at the end.

    Thanks. After running

    echo "[]" | sudo tee /var/lib/openmediavault/apt/upgradeindex.json
    sudo rm /var/lib/openmediavault/apt/pluginsindex.json
    sudo omv-mkaptidx


    Looking at

    Code
    /var/lib/openmediavault/apt/pluginsindex.json 

    Its empty.

    Is there a way to recreate?

    Thanks

    • Official Post

    Is there a way to recreate?

    omv-mkaptidx is supposed to do that. What is the output of: head /usr/sbin/omv-mkaptidx

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.6 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

  • jofen you are still suffering from a unsuccesful upgrade.

    Use this script or


    try

    rm -f /usr/sbin/omv-mkaptidx

    dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx

    omv-mkaptidx

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    • Official Post

    This is the result

    upgrades are such a pain


    Try:


    sudo dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx

    sudo omv-mkaptidx

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.6 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    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!

  • try

    rm -f /usr/sbin/omv-mkaptidx

    dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx

    omv-mkaptidx

    This worked for me. Thank you very much.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • Just for the Record:

    gderf and jofen, you had updated previously from OMV5, correct?


    Strange that the issue only showed with the latest update from 6.0.20 to 6.0.21.


    Or maybe it was already there and you hadn't spotted it?!?


    Nice to see a solution, at least, 👍

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!