Posts by James_Sheeler

  • Failed upgrades

    For the past couple weeks I have seen this error when upgrading packages. Not sure what to do about this.


    '''

    ependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of openmediavault-kernel:

    openmediavault-kernel depends on openmediavault (>= 7); however:

    Package openmediavault is not configured yet.


    dpkg: error processing package openmediavault-kernel (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of openmediavault-scripts:

    openmediavault-scripts depends on openmediavault (>= 7.1); however:

    Package openmediavault is not configured yet.


    dpkg: error processing package openmediavault-scripts (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of openmediavault-nut:

    openmediavault-nut depends on openmediavault (>= 7.7.2); however:

    Package openmediavault is not configured yet.


    dpkg: error processing package openmediavault-nut (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of openmediavault-compose:

    openmediavault-compose depends on openmediavault (>= 7); however:

    Package openmediavault is not configured yet.


    dpkg: error processing package openmediavault-compose (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of php8.2-phpdbg:

    php8.2-phpdbg depends on php8.2-cli; however:

    Package php8.2-cli is not configured yet.


    dpkg: error processing package php8.2-phpdbg (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of php8.2-fpm:

    php8.2-fpm depends on php8.2-cli; however:

    Package php8.2-cli is not configured yet.


    dpkg: error processing package php8.2-fpm (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of openmediavault-omvextrasorg:

    openmediavault-omvextrasorg depends on openmediavault (>= 7); however:

    Package openmediavault is not configured yet.


    dpkg: error processing package openmediavault-omvextrasorg (--configure):

    dependency problems - leaving unconfigured

    dpkg: dependency problems prevent configuration of php8.2-cgi:

    php8.2-cgi depends on php8.2-cli; however:

    Package php8.2-cli is not configured yet.


    dpkg: error processing package php8.2-cgi (--configure):

    dependency problems - leaving unconfigured

    Errors were encountered while processing:

    nginx-common

    vim-tiny

    xz-utils

    php8.2-cli

    nginx

    openmediavault

    openmediavault-kernel

    openmediavault-scripts

    openmediavault-nut

    openmediavault-compose

    php8.2-phpdbg

    php8.2-fpm

    openmediavault-omvextrasorg

    php8.2-cgi

    W: Problem unlinking the file /var/log/apt/eipp.log.xz - FileFd::Open (5: Input/output error)

    W: Could not open file /var/log/apt/eipp.log.xz - open (17: File exists)

    W: Could not open file '/var/log/apt/eipp.log.xz' - EIPP::OrderInstall (17: File exists)

    W: Could not open file '/var/log/apt/term.log' - OpenLog (5: Input/output error)

    E: Sub-process /usr/bin/dpkg returned an error code (1)

    root@openmediavault:~#

    '''

  • docker not working since omv-upgrade

    Quote from ryecoaaron

    Here is the solution to disable apparmor on the system and it worked on my test system (not harmful since apparmor package is not installed):

    Code
    sudo mkdir -p /etc/default/grub.d
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' | sudo tee /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo reboot

    Taken from: https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor

    Thank you, this worked for me as well.

  • Can't run docker containers after upgrade to v6. AppArmor missing"

    Ok


    Here is docker info and it shows it in there.


    And the output of


    Code
    root@openmediavault:~# apt-get purge apparmor apparmor-utils auditd
    Code
    Reading package lists... Done
    Code
    Building dependency tree... Done
    Code
    Reading state information... Done
    Code
    Package 'apparmor' is not installed, so not removed
    Code
    Package 'apparmor-utils' is not installed, so not removed
    Code
    Package 'auditd' is not installed, so not removed
    Code
    The following package was automatically installed and is no longer required:
    Code
      linux-image-5.19.0-0.deb11.2-amd64
    Code
    Use 'apt autoremove' to remove it.
    Code
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  • Can't run docker containers after upgrade to v6. AppArmor missing"

    this is what I see when I go to remove it, is it safe to proceed?


  • Can't run docker containers after upgrade to v6. AppArmor missing"

    I am seeing the same issues as well this morning.




    Code
    root@openmediavault:~# dpkg -l | grep -E "docker|apparmor"
ii  docker-ce                          5:23.0.0-1~debian.11~bullseye amd64        Docker: the open-source application container engine
ii  docker-ce-cli                      5:23.0.0-1~debian.11~bullseye amd64        Docker CLI: the open-source application container engine
ii  docker-compose-plugin              2.15.1-1~debian.11~bullseye   amd64        Docker Compose (V2) plugin for the Docker CLI.
ii  libapparmor1:amd64                 2.13.6-10                     amd64        changehat AppArmor libraryroot@openmediavault:~#

  • Error with backup plugin

    Also get this message sometimes when using SMART to check drives


    /etc/cron.weekly/openmediavault-update-smart-drivedb:
    mesg: ttyname failed: Inappropriate ioctl for device





    Sent from my Pixel 3 XL using Tapatalk

  • Error with backup plugin

    I'm using fsarchiver and getting this error message




    mesg: ttyname failed: Inappropriate ioctl for device
    E: Could not get lock /var/cache/apt/archives/lock - open (11: Resource temporarily unavailable)
    E: Unable to lock directory /var/cache/apt/archives/
    E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
    E: Unable to lock directory /var/lib/apt/lists/



    What does this mean?


    Sent from my Pixel 3 XL using Tapatalk

  • Having trouble routing Docker containers through vpn container after last Docker update

    I had this issue as well try adding them to the container through the networks tab in the docker gui, I read its an issue with docker but adding them through this gui should work.


    Select the network you want to use for VPN click connect then add the docker images as well as the IPs you want them to use.


    If you dont know what IP to select login to terminal and use docker network inspect (networkname) to find out whats available.


    hope this helps