System version // NethServer release 7.5.1804 (final)
- Software center configuration > Locked > Download updates > Install updates automatically
- On return, it shows only the SOGO module as available
- Software Updates > DOWNLOAD AND INSTALL
- “Resolving RPM dependencies The install/update may have failed due to metadata caching issues. Please clean the cache by clicking the button below and retry the install/update operation. CLEAR YUM CACHE”
- CLEAR YUM CACHE
On return = Software updates are available
Updates > DOWNLOAD AND INSTALL
again “Resolving RPM dependencies The install/update may have failed due to metadata caching issues. Please clean the cache by clicking the button below and retry the install/update operation. CLEAR YUM CACHE”
yum clean all --enablerepo=*; yum update
config show sysconfig
- On return to GUI
- Software center - system upgrade
- “A system upgrade to NethServer 7.6.1810 is available. The system upgrade procedure switches the to “unlocked” software updates origin and updates all installed packages”
- Software center > Available
- Still, only SOGO is available
- OS Version:
- System version is still at 7.5.1804 (final)
- pkgaction: [YumRPMCheckError] [u’ERROR with transaction check vs depsolve:’, ‘jq is needed by nethserver-subscription-3.3.2-1.ns7.noarch’, ‘perl(Proc::ProcessTable) is needed by nethserver-backup-config-2.2.1-1.ns7.noarch’, ‘perl-Proc-ProcessTable is needed by nethserver-backup-config-2.2.1-1.ns7.noarch’]
rpm -qa | grep jq
rpm -qa | grep ProcessTable
fpauspNeth Server Ambassador // I ask myself if the locked-feature is technically mature…
Giacomo Sanchietti Dev Team // I’m not sure neither…
** Giacomo Sanchietti Dev Team // This requires a lot of work and a good infrastructure, this is why we create the subscription plan…
** Does that mean that your infrastructure is not good or that you do not want to do a lot of work?
** “…getting access to monitoring portal and stable update repositories.”
** Does that mean that other repositories are not stable?
If a system has the Software origin policy set to Locked and it has automatic updates enabled, it should never update…
- if not set to: “Install updates automatically”, the version will update automatically to NethServer 7.6.1810
- On previous installations, I always disabled “automatic updates” then after an update, the system is at version 7.6.
- I never saw automatic updates on production server except with Micro$oft and even then, I always suspected a newbie administrator.
- December 2018
- My Locked 7.5's have or are updating to 7.6
- fasttech Quality Team
- once 7.6 is out, 7.5 is dead: we are using the concept of “rolling release”, so old releases should be always updated to latest one. Also, old releases will not get any update (including security fixes from upstream)
- “old releases should be always updated to latest one” I never heard of such a thing. It is always better to wait for a little while to see if the new release is safe to update to.
- “Also, old releases will not get any update (including security fixes from upstream)”. What kind of quality is that? Some distributions include security fixes for up to 10 years after initial release.
- December 2018
- New Centos 7.6 update
- Davide Principi NethServer Ambassador
- Due to a bug in the yum-cron/NsReleaseLock feature those who enabled the automated updates found a bad surprise today: their systems were updated to CentOS 7.6 by the daily cron job.
- “…so old releases should be always updated to latest one.” As I wrote before: “It is always better to wait for a little while to see if the new release is safe to update to.”
I always prefered security/stability to latest goodies.
lang en_US.UTF-8 --addsupport=fr_CA.UTF-8
- Login to the GUI, fr_CA: nowhere to be seen…
- First NIC:
network --bootproto=static --device=enp0s3 --gateway=192.168.1.1 --ip=192.168.1.11 --nameserver=192.168.1.1 --netmask=255.255.255.0 --ipv6=auto --activate
- Login to the GUI > Network > First NIC doesn’t have gateway set…
- Second NIC:
In installation, put it OFF.
network --bootproto=dhcp --device=enp0s8 --nameserver=184.108.40.206 --ipv6=auto
- Login to the GUI > Network > Second NIC is given a DHCP address
echo “Disable kdump…”
systemctl disable kdump
- In installation, I looked at it and it was CHECKED by default
It’s been a month that I am looking at NethServer, still I am not convinced that it is stable and ready for a production environment…
I would really like to be proved wrong,