CRON-APT error

Sorry to say, but I've exactly the same issue like nasty_vibrations. I tried all the steps ryecoaaron proposed, but still the same. Let me know, if I shall run some commands or provide any other info.

Quote from Silenzium

Sorry to say, but I've exactly the same issue like nasty_vibrations. I tried all the steps ryecoaaron proposed, but still the same. Let me know, if I shall run some commands or provide any other info.

How is your system running?

Have you been upgrading from any older versions of OMV or is it a fresh install?

And what error from what command are you experiencing?

More info is needed to filter this.

I'm having my head around this so, was just checking some things:

This is an OMV6 arm64 that was upgraded from OMV5.

I had the automatic updates OFF (by my own choice) on OMV5 and it carried to OMV6.

When CRON-APT runs at ~7AM (with automatic updates OFF), the command that shows is: /usr/bin/apt-get  dist-upgrade -d -y -o APT::Get::Show-Upgraded=true

This only shows that updates are available and I need to go to either GUI or CLI to do the actual update.

Checking the files mentioned:

pi@xxxxxxx:~ $ cat /etc/cron-apt/config
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# Configuration for cron-apt.
# The cron config is located in /etc/cron.d/cron-apt

# When to send email about the cron-apt results.
# Value: error   (send mail on error runs)
#        upgrade (when packages are upgraded)
#        changes (mail when change in output from an action)
#        output  (send mail when output is generated)
#        always  (always send mail)
#                (else never send mail)
MAILON="upgrade"

# The email address to send mail to.
MAILTO="xxxxxx@gmail.com"

# Value: error   (syslog on error runs)
#        upgrade (when packages is upgraded)
#        changes (syslog when change in output from an action)
#        output  (syslog when output is generated)
#        always  (always syslog)
#                (else never syslog)
SYSLOGON="always"

# Value: verbose (log everything)
#        always  (always log)
#        upgrade (when packages is upgraded)
#        changes (log when change in output from an action)
#        output  (log when output is generated)
#        error   (log error runs only)
#                (else log nothing)
# DEBUG="output"

# General apt options that will be passed to all APTCOMMAND calls.
# Use "-o quiet" instead of "-q" for aptitude compatibility.
#  OPTIONS="-o quiet=1"
# You can for example add an additional sources.list file here.
#  OPTIONS="-o quiet=1 -o Dir::Etc::SourceList=/etc/apt/security.sources.list"
# You can also set an alternative sources.list file here.
#  OPTIONS="-o quiet=1 -o Dir::Etc::SourceList=/etc/apt/security.sources.list -o Dir::Etc::SourceParts=\"/dev/null\""
# If you want to allow unauthenticated and untrusted packages add the
# following to your options directive.
#  OPTIONS="-o quiet=1 -o APT::Get::AllowUnauthenticated=true -o aptitude::Cmdline::ignore-trust-violations=yes"
# To limit the bandwidth used use the following line. This example limit the
# bandwidth usage to 25 kB/s.
#  OPTIONS="-o Acquire::http::Dl-Limit=25"
OPTIONS=""

pi@xxxxxxx:~ $ cat /etc/cron-apt/action.d/0-update
update -o quiet=2

pi@xxxxxx:~ $ cat /etc/cron-apt/action.d/3-download
autoclean -y
dist-upgrade -d -y -o APT::Get::Show-Upgraded=true

nasty_vibrations && Silenzium

Care to try the following commands to see if it clears that error:

Check the status of this environment (if it shows nothing, it should be on default that is TRUE):

omv-env get OMV_APT_USE_OS_SECURITY

This command will set Auto-Updates to FALSE:

omv-env set OMV_APT_USE_OS_SECURITY false

This command will set Auto-Updates to TRUE:

omv-env set OMV_APT_USE_OS_SECURITY true

And to finish the action:

omv-salt deploy run cronapt

Then check again the files above to see if there's any difference between them and try to run again the update command.
And rest assure that all the above is good to be done and non-destructive.

Quote from nasty_vibrations

I can't see any difference in them.

The update command still results in the known error.

Ok, it was worth a shot.

Maybe ryecoaaron can spot something else on this matter.

Quote from nasty_vibrations

Soma : Do you know why /etc/cron-apt/action.d/3-download doesn't exist?

I'm affraid not.
I thought that the salt command would (re)create it.

Let's wait for some, hopefully, solution.