Issues upgrading to 4.1.14-1

  • When doing omv-update in command line or GUI update I get the following error


    “”” dpkg: unrecoverable fatal error, aborting:
    unable to open files list file for package ‘libicu57:amd64’: no such device or address


    E: Sub-process /usr/bin/dpkg return an error code (2). “””


    When I do ‘apt-get install libicu57’ it says “libicu57 is already the newest very...”


    I click (y) to install anyways and it says:


    “Errors were encountered while processing:
    python-samba
    samba
    samba-common-bin
    openmediavault
    openmediavault-backup
    openmediavault-omvextraorg
    openmediavault-usbbackup
    E: Sub-process /usr/bin/dpkg returned and error code (1)”


    Here are some screenshots:






    Sent from my iPhone using Tapatalk

  • I got errors upgrading as well:


    Reading package lists...
    Building dependency tree...
    Reading state information...
    The following packages will be upgraded:
    openmediavault
    Preconfiguring packages ...
    1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 0 B/1689 kB of archives.
    After this operation, 5120 B of additional disk space will be used.
    (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 45112 files and directories currently installed.)
    Preparing to unpack .../openmediavault_4.1.14-1_all.deb ...
    Unpacking openmediavault (4.1.14-1) over (4.1.13-1) ...
    Setting up openmediavault (4.1.14-1) ...
    Installing new version of config file /etc/cron.weekly/openmediavault-update-smart-drivedb ...
    Updating configuration database ...
    Updating configuration ...
    Processing triggers for rsyslog (8.24.0-1) ...
    Processing triggers for openmediavault (4.1.14-1) ...
    Restarting engine daemon ...
    Cannot create socket to [localhost]:2812 -- Connection refused
    Updating locale files ...
    Updating file permissions ...
    Purging internal cache ...
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fbfcf3398c8>
    Traceback (most recent call last):
    File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fbfcf3398c8>
    Traceback (most recent call last):
    File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable
    Done ...
    ?(

    • Offizieller Beitrag

    I got errors upgrading as well:

    I don't see any errors in that output that affect anything (especially the weakref error). The create socket error is caused by restarting the engine. This won't affect anything either.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | 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!