error #4000 when update OMV (after outage)

  • Hello,


    since after a outage we have a problem with our raid5, not appear but all disk are still present.
    >>> Need help too here...



    and we have now a error when we tried to update the OMV 2.2.14


    Here is the error message:


    If someone have a idea to fix this, it'll be great..


    Thank you.
    Regard.

  • If someone have a idea to fix this, it'll be great..

    This is temporary. OMV downloads (not installs) updates daily. Once it done downloading the updates, you should be able to update. Otherwise, reboot and try to update right away.

    omv 5.5.2 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Thank you for your answer.


    But no, stil yesterday I'm trying.
    In the admin interface I click on the "update manager" button, and then click on "check"..but since yesterday I had this problem...


    And if I connect with ssh, and do a "apt-get update", I had this error message :


    Code
    root@OMV-NAS:~# apt-get update
    E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
    E: Unable to lock directory /var/lib/apt/lists/

    If you have a idea... and maybe it is linked with my othe problem (which is bigger..) : can you check here too..?


    Thank you very much.
    Regard.

  • Ok I done this, but it's blocked at 34% (and very slow)


    Apparently, there is a DNS problem, no ?


    Thank you.



    PS: yes I know you hate raid problem, but I answer to you, and if you just have a idea where I can search to solve this it'll be great. Regard.

  • Apparently, there is a DNS problem, no ?

    Yep it is a dns issue. Do you have your dns server set in network setup?



    yes I know you hate raid problem, but I answer to you, and if you just have a idea where I can search to solve this it'll be great

    I saw it. Just give me a bit.

    omv 5.5.2 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Yes I have set up the DNS server in network setup. Which is here 192.168.2.91
    I verified and it is good.


    And if I put the google's DNS 8.8.8.8, I have the problem too...


    Strange isn't it...?

  • Code
    root@OMV-NAS:~# cat /etc/resolv.conf
    search cire.be
    nameserver 192.168.2.77

    the 192.168.2.77 is the old DNS server.


    Now it is 192.168.2.91. But I changed it in the "Ethernet connection" window (screenshot below).


    Regard.




    PS : macom. No, the gateway and DNS are not the same server (in this case). You have a lot of DNS server (google, from your provider, OpenDNS,...)

  • Now it is 192.168.2.91. But I changed it in the "Ethernet connection" window (screenshot below).

    So, is the /etc/resolv.conf before or after changing the ethernet connection in the web interface?

    omv 5.5.2 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Hello,




    Code
    root@OMV-NAS:~# cat /etc/apt/sources.list.d/*.list
    deb http://packages.openmediavault.org/public stoneburner main
    # deb http://downloads.sourceforge.net/project/openmediavault/packages stoneburner main


    If you have a idea...


    Thank you very much.
    Regard.

  • Ok so I empty the /etc/resolv.conf and reboot.


    And after rebooting, it is still empty. But

    Quote

    /etc/resolv.conf is automatically generated upon reboot by resolvconf if its a symbolic link to /run/resolvconf/resolv.conf (the file resolvconf writes to), you don't need to create it or edit it.


    So is there a bug ?

  • Hello hello ?

    I was busy with more important things....


    I don't know why it isn't working. Everything looks correct. Maybe it is bug in OMV 2.x but it is so old, you should upgrade.

    omv 5.5.2 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

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