Updates are not fetched on three different OMV installs

  • Hi there,


    Here is a combo topic about upgrade issues I am having on three different OMV installs.


    1- on Raspberry Pi supplemented by RTC, running off a USB hard drive
    Had issues with adding Samsung Ml-2510 printer. I finally managed to make it run (though it's unclear how exactly), but it still has issues (1) (2).


    2- On Banana Pi running off SD card. Flash Memory plugin is installed and active (3).
    Displayed error is:
    Failed to execute command 'export LANG=C; apt-get update 2>&1': Ign file: Release.gpg Ign file: Release Ign file: Translation-en Hit http://apt.syncthing.net syncthing Release.gpg Hit http://www.greyhole.net stable Release.gpg Hit http://security.debian.org wheezy/updates Release.gpg Hit http://security.debian.org wheezy/updates Release Hit http://www.deb-multimedia.org wheezy Release.gpg Hit http://dl.bananian.org wheezy Release.gpg Hit http://ppa.launchpad.net precise Release.gpg Hit http://www.greyhole.net stable Release Hit http://debian.yeasoft.net wheezy Release.gpg Hit http://apt.tvheadend.org wheezy Release.gpg Hit http://dh2k.omv-extras.org plex-wheezy-mirror Release.gpg Hit http://ftp.pl.debian.org wheezy Release.gpg Hit http://ppa.launchpad.net precise Release Hit http://www.deb-multimedia.org wheezy Release Hit http://dl.bananian.org wheezy Release Hit http://security.debian.org wheezy/updates/main Sources Hit http://apt.tvheadend.org wheezy Release Hit http://debian.yeasoft.net wheezy Release Hit http://packages.openmediavault.org stoneburner Release.gpg Ign http://dh2k.omv-extras.org stoneburner-miller Release.gpg Hit http://packages.omv-extras.org stoneburner Release.gpg Hit http://ftp.pl.debian.org wheezy-updates Release.gpg Hit http://www.greyhole.net stable/main armhf Packages Hit http://security.debian.org wheezy/updates/contrib Sources Hit http://ppa.launchpad.net precise/main armhf Packages Ign http://dh2k.omv-extras.org stoneburner-vpn Release.gpg Hit http://security.debian.org wheezy/updates/non-free Sources Hit http://apt.syncthing.net syncthing Release Hit http://packages.omv-extras.org stoneburner-plex Release.gpg Hit http://ftp.pl.debian.org wheezy-backports Release.gpg Hit http://www.deb-multimedia.org wheezy/main Sources Hit http://ppa.launchpad.net precise/main Translation-en Hit http://dl.bananian.org 


    I have seen errors starting with Export LANG=C often in other virtual Linuxes I am playing with, but still don't know what it means. On other Linux-based distros, it doesn't prevent updates from going through, though. Why does it in OMV?


    3- In Virtual Box
    At first it gave the error listed below, but now, without any configuration changes, it finally found updates and applied them successfuly.
    What does the intermittent error means, and how to prevent it?


    Displayed error in dialog box is:
    Failed to execute command 'export LANG=C; apt-get update 2>&1': Ign file: Release.gpg Ign file: Release Ign file: Translation-en Hit http://www.greyhole.net stable Release.gpg Hit http://ftp.us.debian.org wheezy Release.gpg Hit http://ftp.us.debian.org wheezy-updates Release.gpg Hit http://www.greyhole.net stable Release Hit http://ftp.us.debian.org wheezy Release Hit http://ftp.us.debian.org wheezy-updates Release Hit http://ppa.launchpad.net precise Release.gpg Hit http://www.greyhole.net stable/main amd64 Packages Hit http://ftp.us.debian.org wheezy/main Sources Hit http://ftp.us.debian.org wheezy/main amd64 Packages Hit http://ppa.launchpad.net precise Release Hit http://ftp.us.debian.org wheezy/main Translation-en Hit http://ftp.us.debian.org wheezy-updates/main Sources Hit http://ppa.launchpad.net precise/main amd64 Packages Hit http://ftp.us.debian.org wheezy-updates/contrib Sources Hit http://ftp.us.debian.org wheezy-updates/non-free Sources Hit http://ppa.launchpad.net precise/main Translation-en Hit http://ftp.us.debian.org wheezy-updates/main amd64 Packages/DiffIndex Ign http://www.greyhole.net stable/main Translation-en Hit http://ftp.us.debian.org wheezy-updates/contrib amd64 Packages Hit http://ftp.us.debian.org wheezy-updates/non-free amd64 Packages Hit http://ftp.us.debian.org wheezy-updates/contrib Translation-en Hit http://ftp.us.debian.org wheezy-updates/main Translation-en Hit http://ftp.us.debian.org wheezy-updates/non-free Translation-en Hit http://security.debian.org wheezy/updates Release.gpg Hit http://dh2k.omv-extras.org virtualbox-wheezy-mirror Release.gpg Hit http://packages.omv-extras.org stoneburner Release.gpg Hit http://security.debian.org wheezy/updates Release Hit http://security.debian.org wheezy/updates/main Sources Hit http://dh2k.omv-extras.org plex-wheezy-mirror Release.gpg Hit http://packages.omv-extras.org stoneburner-vb Release.gpg Hit http://security.debian.org wheezy/updates/contrib Sources Hit http://security.debian.org wheezy/updates/non-free Sources Hit http://packages.omv-extras.org stoneburner-plex Release.gpg Ign http://dh2k.omv-extras.org stoneburner-miller Release.gpg Hit http://security.debian.org wheezy/updates/main amd64 Packages Hit http://security.debian.org wheezy/updates/contrib amd64 Packages Hit http://security.debian.org wheezy/updates/non-free amd64 Packages Hit http://packages.omv-extras.org stoneburner-greyhole Release.gpg Ign http://dh2k.omv-extras.org stoneburner-vpn Release.gpg Hit http://security.debian.org wheezy/up


    Overall, the error messages are not terribly helpful, and the dialog boxes are often too large to spot the relevant part.

    • Offizieller Beitrag

    I don't see any bad repos but that is the typical reason an apt-get update would fail. Can you post the output from apt-get update run from putty as root? Not all of the message is in your output.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • I'm not quite sure if I have the same problem and I don't want to hijack your thread but I can't update my OMV either. I have to say that my OMV was offline for about 4 months due to a missing internet connection but today I'm back again in the www. An update from GUI gives no error but in CLI using

    Code
    apt-get update

    returns


    Does anybody know what to do?


    Thank you!
    fahrer17

    OMV6.x

    AMD Ryzen 5 5600G

    ASRock B550M Pro4

    Crucial DIMM 16GB

    Western Digital WD Blue SN570

    Seagate IronWolf 8TB/WD Red 8TB

    AeroCool CS-102

  • Are you sure? I don't have any packages.omv-extras.org/debian/dists/kralizec/Release - that's how my sources.list looks like:


    OMV6.x

    AMD Ryzen 5 5600G

    ASRock B550M Pro4

    Crucial DIMM 16GB

    Western Digital WD Blue SN570

    Seagate IronWolf 8TB/WD Red 8TB

    AeroCool CS-102

  • OK, a short Google search brought the solution hopefully (at least an update is running atm):


    Code
    sudo apt-get clean
    sudo mv /var/lib/apt/lists /var/lib/apt/lists.old
    sudo mkdir -p /var/lib/apt/lists/partial
    sudo apt-get update


    Taken from http://www.rootz.de/stichwort/…wurde-nicht-aktualisiert/


    http://www.rootz.de/stichwort/…wurde-nicht-aktualisiert/
    ......aaaaand everything is fine now! :thumbup:

    OMV6.x

    AMD Ryzen 5 5600G

    ASRock B550M Pro4

    Crucial DIMM 16GB

    Western Digital WD Blue SN570

    Seagate IronWolf 8TB/WD Red 8TB

    AeroCool CS-102

  • Sorry
    nano /etc/apt/sources.list.d/openmediavault.list


    Zu spät :D
    Hmmm, ob das die gleiche Lösung war...


    Edit:
    packages.omv-extras.org/debian/dists/kralizec/Release looks like this on my system:


    OMV6.x

    AMD Ryzen 5 5600G

    ASRock B550M Pro4

    Crucial DIMM 16GB

    Western Digital WD Blue SN570

    Seagate IronWolf 8TB/WD Red 8TB

    AeroCool CS-102

    Einmal editiert, zuletzt von fahrer17 ()

    • Offizieller Beitrag

    The apt clean button in omv-extras or omv-aptclean fixes this problem most of the time.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Thanks all for your replies,


    for omv-update, I get:
    Raspberry Pi:
    no error in the command line.


    Banana Pi:



    VirtualBox:
    No error from the command line,
    apt-get update yields no error.
    yet it fails from the web interface.


    Then I tried what fahrer17 posted, and got this error:


    Haven't tried in in the other OMV installations as they are more difficult to restore to a semi-working state if it goes awry.

    • Offizieller Beitrag

    Read the messages. They tell you what the problem is. Banana Pi has a bad tvheadend repo (probably because it does not support armhf). Remove it.


    Virtualbox - the omv repo must have been down or something. Not much you can do to fix that other than wait.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • For the same omv-command, I now get:


    On Banana Pi:


    After disabling all repos from OMV-extras.org:


    Same tvheadend error. I commented it out in /etc/apt/sources.list, and ran omv-update again.


    Then it worked.


    But what functionality does tvheadend provides in OMV, anyway?


    On VirtualBox:


    The BTSync third-party repository seems to have invalid certificates.



    How
    would I put the missing certificate in? I find it confusing because
    even during normal upgrade process, authentication is ignored. Isn't it
    risky not to authenticate packages?


    As a side-question: when OMV kicks off an idle user, displaying the
    red-on-black bar at the top, one script stays active on the page and
    eats up CPU power, locking the Firefox tab with it. Wouldn't it be more
    gentle on the CPU to simply display a static version of this bar, or
    simply reload the login page?

    • Offizieller Beitrag

    You (or a script) must have added tvheadend to the sources.list because omv-extras does not add anything to that file. It is used for recording tv shows.


    bintray is not the btsync repo. That is the new hosting repo for omv-extras and a few 2.x repos. I don't get the cert issue. Not sure why you are.


    Packages are authenticated when they are signed. OMV does ignore it if they are aren't signed though. I'm guess this was done for people to write plugins without signing them. It might be risky if you didn't trust the repo. Although anyone can get a signing key. So, how does being signed make it safe? It only prevents the man-in-the-middle attack.


    I set my timeout to 0. So, I don't have this issue. File a request at bugtracker to change it

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

Jetzt mitmachen!

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