Any reason not to do this or a better way to do it?
install unattended-upgrades. This will do things the proper way and only reboot when needed.
install unattended-upgrades. This will do things the proper way and only reboot when needed.
Reading the debian documentation I couldn't tell if the OMV packages will be updated. Will they?
Will they?
If you add the omv and omv-extras repos to the repos in /etc/apt/apt.conf.d/50unattended-upgrades in the Unattended-Upgrade::Allowed-Origins section, it will.
If you add the omv and omv-extras repos to the repos in /etc/apt/apt.conf.d/50unattended-upgrades in the Unattended-Upgrade::Allowed-Origins section, it will.
What should the syntax be there? I tried the following (see line 12):
Unattended-Upgrade::Origins-Pattern {
// Codename based matching:
// This will follow the migration of a release through different
// archives (e.g. from testing to stable and later oldstable).
// Software will be the latest available for the named release,
// but the Debian release itself will not be automatically upgraded.
// "origin=Debian,codename=${distro_codename}-updates";
// "origin=Debian,codename=${distro_codename}-proposed-updates";
"origin=Debian,codename=${distro_codename},label=Debian";
"origin=Debian,codename=${distro_codename},label=Debian-Security";
"origin=Debian,codename=${distro_codename}-security,label=Debian-Security";
"origin='openmediavault.org archive',codename=sandworm";
// Archive or Suite based matching:
// Note that this will silently match a different release after
// migration to the specified archive (e.g. testing becomes the
// new stable).
// "o=Debian,a=stable";
// "o=Debian,a=stable-updates";
// "o=Debian,a=proposed-updates";
// "o=Debian Backports,a=${distro_codename}-backports,l=Debian Backports";
};But I only got a notification e-mail; the upgrades weren't applied automatically:
apticron report [Thu, 21 Mar 2024 12:11:05 +0100]
========================================================================
apticron has detected that some packages need upgrading on:
naslg2
[ 10.192.1.254 172.17.0.1 172.18.0.1 172.19.0.1 172.29.0.1 ]
[ 192.168.1.10 ]
The following packages are currently pending an upgrade:
containerd.io 1.6.28-2
docker-buildx-plugin 0.13.1-1~debian.12~bookworm
docker-ce 5:26.0.0-1~debian.12~bookworm
docker-ce-cli 5:26.0.0-1~debian.12~bookworm
docker-compose-plugin 2.25.0-1~debian.12~bookworm
openmediavault 7.0.4-1
openmediavault-compose 7.1
========================================================================
Package Details:
apt-listchanges: Reading changelogs...
apt-listchanges: Changelogs
---------------------------
--- Changes for containerd.io ---
containerd.io (1.6.28-2) release; urgency=medium
* Fix builds for Raspbian armhf producing armv7 binaries
* Build Debian armhf binaries as armv6
* Update Golang runtime to 1.21.8
-- Sebastiaan van Stijn <thajeztah@docker.com> Fri, 15 Mar 2024 14:41:52 +0000
--- Changes for docker-ce (docker-buildx-plugin docker-ce docker-ce-cli docker-compose-plugin) ---
docker-ce (5:26.0.0-1~debian.12~bookworm) bookworm; urgency=low
* Version: 26.0.0
-- Docker <support@docker.com> Wed, 20 Mar 2024 15:18:01 +0000
--- Changes for openmediavault ---
openmediavault (7.0.4-1) stable; urgency=low
* Replace hdparm with smartctl in UDEV helper script.
-- Volker Theile <volker.theile@openmediavault.org> Sat, 16 Mar 2024 12:33:17 +0100
openmediavault (7.0.3-1) stable; urgency=low
* Add functionality required by plugins.
-- Volker Theile <volker.theile@openmediavault.org> Sat, 16 Mar 2024 11:05:17 +0100
--- Changes for openmediavault-compose ---
openmediavault-compose (7.1) stable; urgency=low
* Support backup for paths using environment variables
* Add file to database if the file does not exist when restoring
* Add ability to import one compose file
* Add Advanced menu
* Move Build menu options to Advanced menu
* Add up and down with the --remove-orphans option to Advanced menu
-- OpenMediaVault Plugin Developers <plugins@omv-extras.org> Sat, 16 Mar 2024 12:39:34 -0500
========================================================================
You can perform the upgrade by issuing the command:
apt-get dist-upgrade
as root on naslg2
--
apticronSo I assume the syntax in line 12 is wrong?
Hi,
I see you marked it as solved but it doesn't work yet, right?
Hi,
I see you marked it as solved but it doesn't work yet, right?
Hmm, I suppose it would've been better if I had started a new thread, rather than revive this one...?
Ahhh, just noticed it was not you have it marked as solved.
Let's wait if chente or ryecoaaron shed some light on it 
This thread is old. You can read in this other thread how to do it.
I don't have unattend-upgrades configured but it would probably look something like:
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-backports";
"Docker:${distro_codename}";
"openmediavault-plugin-developers.github.io:sandworm";
"packages.openmediavault.org:sandworm";
"openmediavault.github.io:sandworm";
"download.proxmox.com:${distro_codename}";
};
// Automatically reboot system when needed
Unattended-Upgrade::Automatic-Reboot "true";Thank you. Much appreciated.
I don't have unattend-upgrades configured but it would probably look something like:
CodeAlles anzeigen// Automatically upgrade packages from these (origin:archive) pairs Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}-security"; "${distro_id}:${distro_codename}-updates"; "${distro_id}:${distro_codename}-backports"; "Docker:${distro_codename}"; "openmediavault-plugin-developers.github.io:sandworm"; "packages.openmediavault.org:sandworm"; "openmediavault.github.io:sandworm"; "download.proxmox.com:${distro_codename}"; }; // Automatically reboot system when needed Unattended-Upgrade::Automatic-Reboot "true";
I suppose it's not 100 % this, since I got this email:
Unattended upgrade result: An error occurred
Packages that attempted to upgrade:
<unknown>
Unattended-upgrades log:
Starting unattended upgrades script
Allowed origins are: origin=Debian,codename=bookworm,label=Debian, origin=Debian,codename=bookworm,label=Debian-Security, origin=Debian,codename=bookworm-security,label=Debian-Security, Docker:bookworm, openmediavault-plugin-developers.github.io:sandworm, packages.openmediavault.org:sandworm, openmediavault.github.io:sandworm, download.proxmox.com:bookworm, origin=Debian,codename=bookworm,label=Debian-Security, origin=Debian,codename=bookworm-security,label=Debian-Security
Initial blacklist:
Initial whitelist (not strict):
An error occurred: not enough values to unpack (expected 2, got 1)
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1993, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/unattended-upgrade", line 2134, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 333, in open
self.apply_pinning(self.pinning_from_config())
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/unattended-upgrade", line 279, in pinning_from_config
if not is_allowed_origin(pkg_file, self.allowed_origins):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/unattended-upgrade", line 981, in is_allowed_origin
if match_whitelist_string(allowed, origin):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/unattended-upgrade", line 820, in match_whitelist_string
(what, value) = [s.strip().replace("%2C", ",")
^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)Too bad I can't deduct which line caused the error. I'll comment them all out, but one, and see where that takes us.
Or I go in an entirely different direction, and use the above linked solution (RE: How to automatically apply configuration changes?) for the OMV part of the system.
Would unattended-upgrades still serve a purpose then? For Debian updates?
Would unattended-upgrades still serve a purpose then? For Debian updates?
The linked post actually does better upgrades in my opinion. unattended-upgrades would still be good for automatically rebooting.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
