Posts by baldman

  • upgrade from 5.6.xxx to 6

    I haven't made a yml for it yet. I was trying to fix nextcloud first and then make a yml for backup.
    I manged to get a command line update going but it didn't work either. I can't get into nextcloud at all.
    I haven't completed any updates at all, but docker says my nextcloud data version is higher than the container image.
    my docker container is running image nextcloud:latest

    If I change the docker image to nextcloud:30-apache I get the following:

    Code
    Conf remoteip disabled.
To activate the new configuration, you need to run: service apache2 reload
Can't start Nextcloud because the version of the data (31.0.0.18) is higher than the docker image version (30.0.6.2) and downgrading is not supported. Are you sure you have pulled the newest image version?

  • upgrade from 5.6.xxx to 6

    I've manged to backup and build composer files for each container. But my Nextcloud is still broken. The web browser says the following, but there's no command line updater in the docker container.


    Please use the command line updater because updating via browser is disabled in your config.php.

  • upgrade from 5.6.xxx to 6

    All my docker data is on a separate disk. I've just never had much recovering docker in the past. I've only ever used portioner.
    Are you saying I just need to install OMV7 and OMV-Extras. Then just load the old docker storage path in docker (OMV-Extras, Docker), and it should just work?

    I'm not sure about YMLs. I'll do some research :/

  • upgrade from 5.6.xxx to 6

    Yeah, it's looking that way. I just don't want to lose all my docker containers. I've already lost Nextcloud. Thats' a mission in itself to rebuild. Nothing ever ends up being easy...lol. I think I need to learn more about backing up containers before proceeding.

    Thanks for all your help :)

  • upgrade from 5.6.xxx to 6

    ls -al /etc/pam.d

    apt --fix-broken install --dry-run

    dpkg -l | grep openme

    Code
    ii  openmediavault                      5.6.26-1                            all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring              1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg         5.6.6                               all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-openvpn              5.1                                 all          OpenVPN plugin for OpenMediaVault.
ii  openmediavault-sftp                 5.0.7                               all          sftp server
ii  openmediavault-symlinks             5.0                                 all          OpenMediaVault symlinks plugin



  • upgrade from 5.6.xxx to 6

    Sorry, I realised from the first page in this thread that I actually did run omv-release-upgrade


    The output from wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix5to6upgrade | sudo bash was too long, and it won't let me post it. But it seemed to work fine. I think it fixed the repo too. When I run apt-get update it doesn't error. But when I run apt-get upgrade it say's to fix some broken things. After fixing them it goes to a blue screen with the following (code below), then it closes.


    apt-get upgrade

    Code
    Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these. 
The following packages have unmet dependencies: 
libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5) but 1.4.0-9+deb11u1 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).



    I fix it with the above, then the blue screen displays this:

    Code
    you are using pam_tally or pam_tally2 in your configuration
The pam_tally and pam_tally2 modules have been removed from PAM. You are using one of these modules in your PAM configuration in /etc/pam.d. You must remove the
uses of these modules before PAM can be upgraded; including these modules in your PAM configuration after the upgrade will stop users from being able to log
into the system.
Consider the pam_faillock module as a replacement for pam_tally.

  • upgrade from 5.6.xxx to 6

    To be honest, I don't really know what I did. It wouldn't update, so I tried to fix it with some the things listed in this thread. However, I didn't rewrite the file like you did in a previous post with the other user. I changed between the boot kernels a couple of times, but that's it.


    Current ACTIVE kernel: Debian GNU/Linux, with Linux 5.10.0-0.deb10.16-amd64
    Optional kernel: Debian GNU/Linux, with Linux 5.10.0-0.bpo.15-amd64

  • upgrade from 5.6.xxx to 6

    Yeah, sorry for hijacking the thread. My issue was similar when searching the forums. I am trying to upgrade, but all updates are failing and can't continue because of this repo issue. The upgrade also won't start. I'm sure I'm on version 5. (Vrs. 5.2.26-1 (Usul) )

    Code
    dpkg -l | grep openmed
ii  openmediavault                      5.6.26-1                            all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring              1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg         5.6.6                               all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-openvpn              5.1                                 all          OpenVPN plugin for OpenMediaVault.
ii  openmediavault-sftp                 5.0.7                               all          sftp server
ii  openmediavault-symlinks             5.0                                 all          OpenMediaVault symlinks plugin
root@FILESERVER:~#
    Code
    cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
    Code
    uname -a
Linux FILESERVER 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux

  • upgrade from 5.6.xxx to 6

    I updated the file. I ran apt-get update and got the same result:

    Code
    E: The repository 'http://security.debian.org/debian-security bullseye-updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


    I got no result from this. It's just blank.

    Code
    grep -r "bullseye/updates" /etc/apt/*  

    sudo omv-aptclean

    Code
    E: The repository 'http://security.debian.org/debian-security bullseye-updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

    sudo omv-aptclean repos


    Code
    E: The repository 'http://security.debian.org/debian-security bullseye-updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.



  • upgrade from 5.6.xxx to 6

    Sorry, I hop this what you mean :)

    Results from: grep -r "bullseye/updates" /etc/apt/*

    Code
    grep -r "bullseye/updates" /etc/apt/*
/etc/apt/sources.list.d/openmediavault-os-security.list:deb http://security.debian.org/debian-security bullseye/updates main contrib non-free
/etc/apt/sources.list.d/openmediavault-os-security.list:deb-src http://security.debian.org/debian-security bullseye/updates main contrib non-free


    Results from: sudo omv-aptclean

    Code
    E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
    Code
    Results from: sudo omv-aptclean repos

E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

  • upgrade from 5.6.xxx to 6

    Sorry for the misunderstanding. What outputs would you like?


    Code
    Sudo apt-get update still gives me the same result.
    Code
    E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

  • upgrade from 5.6.xxx to 6

    apt-get upgrade gives me this:

    You might want to run 'apt --fix-broken install' to correct these.

    The following packages have unmet dependencies:

    libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5) but 1.4.0-9+deb11u1 is installed

    E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).


    Do as suggested above gives me the following blue screen:

    you are using pam_tally or pam_tally2 in your configuration │

    │ │

    │ The pam_tally and pam_tally2 modules have been removed from PAM. You are │

    │ using one of these modules in your PAM configuration in /etc/pam.d. You │

    │ must remove the uses of these modules before PAM can be upgraded; │

    │ including these modules in your PAM configuration after the upgrade will │

    │ stop users from being able to log into the system. │

    │ │

    │ Consider the pam_faillock module as a replacement for pam_tally. │

    │

  • upgrade from 5.6.xxx to 6

    Still the same.


    sudo apt-get update gives me:

    E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

  • upgrade from 5.6.xxx to 6

    Hey,

    I'm having roughly the same issue. Really hoping to avoid rebuilding.


    E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

    root@FILESERVER:~# E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

    Thanks in advance

  • Move docker storage location

    I've tried multiple times now with the same results. I also tried copying the files to the new location after I modify the docker path address. I thought (maybe) the changes might not be replicated to the new directory. I don't know what else to try. Will I just have to rebuild all the containers manually?

  • Move docker storage location

    Hey, so I tried following your instructions again. I confirmed the new directory is being used etc. I'm on OMV5 and all my drives are labeled with UUID. I use the symlinks plugin for some things but not docker as I've had issues using symlinks in docker before. I always make sure to use UUID in my potainer/containers. However, again, after reinstalling docker with the new path, I had to re-install portainer as it wasn't working anymore. All other containers have exited except for the newly installed portainer.

    I'm a pretty basic user when it comes to docker, so I need to educate myself on what stacks are :S ... In saying that, I have zero stacks in Portainer. I use portainer for everything docker, and there's never been any stacks listed in portainer.



  • Docker containers show as exited after changing storage location

    KM0201, that's exactly what I did following instructions in another thread here: Move docker storage location - Docker - openmediavault

    Anyhow, I will try again and see if I have better luck.

    Just to be clear though. I have two folders to move. There is the docker base folder, and the storage folder where the images are being created.
    I'm not sure why I have two folders. It was so long ago when I started using docker :/

  • Docker containers show as exited after changing storage location

    I created them under containers in Portainer. I pulled the images and set them up etc. I have 0 stacks in Portainer. I've never had any stacks in Portainer :/


    I put the storage location back and everything is working again. But when I change to the new storage directory, they all exit, but Portainer still works with the new directory :/

  • Docker containers show as exited after changing storage location

    Hey there, Sorry for the double post. I thought it'd be better to create a dedicated thread for my issue.

    I moved my docker base folder to another drive, but it didn't work correctly.

    I have two docker folders. The main docker storage folder and one for my containers external data, eg plex data.


    The external apps data folder works fine and I haven't moved it. But after I moved the docker folder and reinstalled docker etc, I had to reinstall Portainer to gain access. When I log in all my other containers show as exited and won't start. There's also no "Edit Container" button where I can fix things.


    I'm assuming there's more directory settings that need updating for the individual containers, but I'm not sure where to look.


    Any help would be amazing.

    Thanks B :)