Hi,
please could someone provide a HowTo do all Upgrades and Reboots at a specific time automaticly?
Thanks folks
Chriz
Hi,
please could someone provide a HowTo do all Upgrades and Reboots at a specific time automaticly?
Thanks folks
Chriz
There is a command line tool available. I remember the name being univention-update
or univention-upgrade
Check the tool and itâs parameters. Once you have figured out what parameters you will need you can set up a cron job in /etc/crontab
or /etc/cron.d
.
/KNEBB
As an alternative, a policy can be configured: http://docs.software-univention.de/manual-4.2.html#computers::softwaremanagement::maintenancepolicy
to be honest, i tried the policy method and have no idea what its doing when. could someone explan?
Can you be more specific? What did you configure, or what would you like to configure, and what did not work as expected?
Maybe this german blog article is helpful: https://www.univention.de/2018/03/kurz-erklaert-wie-lassen-sich-ucs-systeme-automatisch-aktualisieren/
There is also an english version https://www.univention.com/2018/03/brief-introduction-how-can-ucs-systems-be-updated-automatically/
great howto, thank you
i did it but it does not do the updates, the machine is assigned to the policy
while reboot does not do any updates, univention-upgrade shows pending ones
01.03.18 11:58:56.325 DEBUG_INIT
**** Starting univention-updater with parameter=[â/usr/share/univention-updater/univention-updaterâ, ânetâ, ââsilentâ, ââcheckâ]
â>DBG:update_available(mode=net, cdrom_mount_point=/media/cdrom, iso=None)
Checking network repository
System is up to dateStarting univention-upgrade. Current UCS version is 4.2-3 errata305
Checking for package updates: found
Please rerun command without --check argument to install.
root@ucs-Leister:~# univention-upgrade
Starting univention-upgrade. Current UCS version is 4.2-3 errata305
Checking for local repository: none
Checking for package updates: foundThe following packages will be upgraded:
libkcutil0,libkcmapi0,libkcarchivercore0,libkcfreebusy0,libkcicalmapi0,libkcinetmapi0,libkcssl0,libkcsync0,kopano-server-packages,kopano-dagent,kopano-spooler,python-mapi,kopano-gateway,libkcsoap0,libkcserver0,kopano-utils,kopano-server,kopano-ical,kopano-monitor,kopano-common,php5-mapi,kopano-contacts,kopano-lang,kopano-client,libmapi1,libkcarchiver0,python-kopano,kopano-presence,kopano-search,kopano-backup,kopano-migration-pst,kopano-webapp,kopano-webapp-plugin-folderwidgets,kopano-webapp-plugin-titlecounter,kopano-webapp-plugin-webappmanual,univention-bind,univention-directory-listener,univention-errata-level,univention-saml,univention-saml-schema,univention-directory-notifierDo you want to continue [Y|n]?
Yes the settings are correct (i think you can use the setting âallâ instead of listing each month
but that policy is for app updates not for system updates - have a look under âReferenzierende Objekteâ !
It may look like :
so with this policy there would be no package updates on UCS System files
rg
Christian
is this policy also upgrading releases?
Hey,
Do you mean such as from 4.2-3 to the just-released 4.3-0? It shouldnât. The policy creates a Cron job that calls /usr/share/univention-updater/univention-actualise
. That one doesnât add new apt sources, nor does it run something like univentio-upgradeâŠ
. Instead, it executes the command set via the UCR variable update/commands/distupgrade
which is basically apt-get dist-ugprade
with certain settings facilitating unattended upgrades. Even if itâs called dist-upgrade
, it really doesnât as the apt sources arenât modified.
Kind regards,
mosu
so after the first test, ucs 4.3 is breaking kopano installations
i have to prevent upgrade to 4.3!!!
is this the correct policy and setting not to do upgrade to new releases?
Hey,
it is. To make this very clear:
Enabling the option (check box) called âActivate release updates (Errata updates are activated by default)â and leaving âUpdate to this UCS versionâ empty will update systems from e.g. 4.2-3 to 4.3-0.
Kind regards,
mosu
Hello,
still the same Problem. The UCS is on Version 4.4.4 but wonât update to version 4.4.6.
Has anyone a functional update policy?
The assigned policies are app-release-updates and app-update-schedule. Both connected to the UCS.