6.9.14-1 receiving CRON-APT repository error

peglegtv · 26. April 2024

I'm running 6.9.14-1 and I've been getting theses emails since April 14th, I finally had time to take a look into it today.

Code

CRON-APT RUN [/etc/cron-apt/config]: Sun Apr 14 07:35:14 CDT 2024
CRON-APT SLEEP: 325, Sun Apr 14 07:40:39 CDT 2024
CRON-APT ACTION: 0-update
CRON-APT LINE: /usr/bin/apt-get  update -o quiet=2
E: The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file.

all references to buster-backports seem to pertain to omv 5 and upgrading to omv 6

/etc/apt/sources.list - no mention of buster-backports

Code

# 



deb http://ftp.us.debian.org/debian/ bullseye main non-free contrib
deb-src http://ftp.us.debian.org/debian/ bullseye main non-free contrib


# bullseye-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free

Alles anzeigen

how ever I did find buster-backports.list in /etc/apt/sources.list.d

Code

deb http://deb.debian.org/debian buster-backports main

what can I do to solve this error? Thank you

chente · 26. April 2024

Zitat von peglegtv

deb http://deb.debian.org/debian buster-backports main

You will have to search the files and subfolders of the /apt folder

In some of them there is that line, when you find it simply delete it.

Soma · 26. April 2024

Just disable the backports on the GUI.

Unless you have a real need for it (some plugins need it, kvm or proxmox/zfs, IIRC), there's no point in having it enabled.

And since you are on a EOL version, if you upgrade, then you can enable it again.

chente · 26. April 2024

Zitat von Soma

And since you are on a EOL version

The OP is on OMV6.

Soma · 26. April 2024

Zitat von chente

The OP is on OMV6.

Didn't want to say EOL.

I wanted to say "almost EOL"

chente · 26. April 2024

Zitat von Soma

"almost EOL"

There is still a way to go to get there.

Soma · 26. April 2024

Debian | endoflife.date

Soma · 26. April 2024

Zitat von chente

There is still a way to go to get there.

3 months pass in a jiffy...

chente · 26. April 2024

Zitat von Soma

Just disable the backports on the GUI.

I'm not sure if that will work, it will depend on how the plugin applies the changes. It is possible that if the system is OMV6 that button does not detect an OMV5 repository to delete it. That's why I told the OP to do it manually, just to be sure.

Soma · 26. April 2024

Zitat von peglegtv

buster

Zitat von chente

I'm not sure if that will work, it will depend on how the plugin applies the changes. It is possible that if the system is OMV6 that button does not detect an OMV5 repository to delete it. That's why I told the OP to do it manually, just to be sure.

AHHHH

Only now I see the issue.

My bad.

peglegtv · 26. April 2024

Thank you for the fast replies,

do I need to delete the file or just the text in the file:

Code

/etc/apt/sources.list.d/buster-backports.list (only one line - deb http://deb.debian.org/debian buster-backports main)

I can't read the files listed below, do I need to delete them as well

Code

/etc/apt/trusted.gpg.d/
                       debian-archive-buster-automatic.gpg
                       debian-archive-buster-security-automatic.gpg
                       debian-archive-buster-stable.gpg

sorry I just want to make sure I'm deleting the right things

thanks again

chente · 26. April 2024

You can delete any line that mentions "buster". After that run:

sudo omv-aptclean repos

sudo omv-upgrade

peglegtv · 26. April 2024

thank you,

being that Bullseye has an EOL of 3 months, is there anything I need to do to avoid this again in three months other then updating OMV 6?

chente · 26. April 2024

Zitat von peglegtv

being that Bullseye has an EOL of 3 months, is there anything I need to do to avoid this again in three months other then updating OMV 6?

Upgrading to OMV7 from OMV6 is working well overall. Some errors have been seen on the forum but they are usually easily repaired. In any case, don't forget to make a backup before updating to OMV7 just in case.

chente · 26. April 2024

Zitat von Soma

3 months pass in a jiffy...

You're right.

I have two systems that I maintain remotely that I have not yet upgraded to OMV7. Most of the problems I have seen on the forum have been precisely connection loss or network problems and if I need to connect a monitor and keyboard I will not be able to do so.

But I'll have to start thinking about upgrading those two systems.

peglegtv · 26. April 2024

Zitat von chente

You can delete any line that mentions "buster". After that run:
sudo omv-aptclean repos
sudo omv-upgrade

sudo omv-upgrade, updated to 6.9.15-1, however the newer docker version (version 26 I believe) broke 3 containers and caused my other containers to act strange sometimes their interfaces wouldn't load or took an extended amount of time to load, so for now I'm going to stick with 6.9.14-1 until I have more time to solve the issues at hand, I get the feeling that I'll have to start from scratch. Thank you for your help

chente · 26. April 2024

If you use Portainer, this may be the reason. Some docker updates broke things in Portainer, you can search the forum, there are some threads about this.

If you think something is broken in your system you can use omv-regen to get a clean installation while preserving your settings. [How to] Migrate/Restore OMV Settings to Another System with omv-regen

I would wait a couple of days in case any developer responds to this thread and wants to investigate this problem antes de regenerar con omv-regen. Solving a problem helps prevent other users from having the same problem.

Jetzt mitmachen!