Changelog for sapconf-5.0.5-150000.7.24.1.noarch.rpm :

* Fri Oct 21 2022 abrielAATTsuse.com- version update from 5.0.4 to 5.0.5- adapt check of an active saptune service during the initial package installation to work in a chroot environment and fix the missing enablement of sapconf. (bsc#1190736, bsc#1190787)
* Mon Apr 25 2022 abrielAATTsuse.com- version update from 5.0.3 to 5.0.4- change block device handling to handle multipath devices correctly. Only the DM multipath devices (mpath) will be used for the settings, but not its paths. (bsc#1188743)- fixed wrong comparison used for setting force_latency (bsc#1185702)- SAP Note 1771258 v6 updates nofile values to 1048576 (bsc#1192841)
* Fri Aug 13 2021 abrielAATTsuse.com- version update from 5.0.2 to 5.0.3- adapt the activity detection of saptune to the upcoming saptune version 3 (bsc#1189496)
* Thu Mar 18 2021 abrielAATTsuse.com- version update from 5.0.0 to 5.0.2- added sapconf_check and supportconfig plugin for sapconf- change log message for \'MIN_PERF_PCT\' parameter to reduce the spot light (bsc#1179524)- add additional check to detect an active saptune service (started but disabled and without any notes applied). Improve the logging message. (bsc#1182314)- enable and start sapconf.service during package update, if tuned is running with sapconf as profile (bsc#1176061)- preserve the state of the sapconf.service during the package update. Only disable the sapconf service, if saptune is active. In any other cases don\'t touch the state of the sapconf service. If tuned has problems and the command \'tune-adm off\' does not work properly in the preinstall script of the package, try to stop the tuned service to avoid weird error messages in the log of tuned during and after the package update (bsc#1182906)
* Wed May 06 2020 abrielAATTsuse.com- version update from 4.2.3 to 5.0.0- check the values of the vm.dirty_
* settings to be in a valid range before activating or restoring these system values. (bsc#1168067)- add a logrotate drop-in file for sapconf to control the size of the /var/log/sapconf.log logfile (bsc#1166925)- use a drop-in file in /etc/security/limits.d instead of modifying /etc/security/limits.conf directly. So during sapconf service start the ulimits for the max number of open files configured with sapconf will be written to /etc/security/limits.d/sapconf-nofile.conf. During sapconf service stop this file will be removed. During package update from version 4 to version 5 of sapconf the nofile related entries added by version 4 of sapconf will be removed from /etc/security/limits.conf. (bsc#1168840)- support multi-queued scheduler for block devices (jsc#SLE-11140, jsc#SLE-11142, jsc#SLE-11143)- remove usage of tuned from sapconf That means: Now there is only ONE configuration file for sapconf /etc/sysconfig/sapconf All trailing comment sections, which were only used for documentation purpose are now removed. All parameters of the tuned profile defined in tuned.conf governor, energy_perf_bias, min_perf_pct, force_latency and elevator are moved to /etc/sysconfig/sapconf Customer specific tuned profile changes in /etc/tuned/ are transferred to /etc/sysconfig/sapconf. The customer specific tuned profile files from /etc/tuned/sapconf are moved to /var/lib/sapconf/saved_configs. Additional parameter settings in these tuned configuration files are NOT covered by sapconf. Additional changes during package update: if sapconf with tuned support was not used during package update stop and disable the sapconf service if sapconf with tuned support was used during package update stop and disable tuned service if saptune is active during package update stop and disable sapconf service To prevent sapconf related tuned error messages anytime after the package installation we need to switch off tuned in the preinstall of the package to remove the \'active\' sapconf profile before the package installation removes the no longer shipped sapconf profile files. The system tuning will be restarted after the configuration transfer in the post phase of the package installation. (jsc#SLE-10985, jsc#SLE-10987, jsc#SLE-10988)
* Thu Mar 19 2020 abrielAATTsuse.com- version update from 4.2.2 to 4.2.3- file /etc/systemd/logind.conf.d/sap.conf will be removed during the package update. It is not needed any longer as the limits for TasksMax and UserTasksMax are removed from systemd/logind (bsc#1148163, jsc#SLE-10123)- if sapconf detects an improper tuned profile during start it will write an information to the log file and the start of the sapconf service will fail to guide the administrator to the problem. (bsc#1139176)- use absolute path to script.sh in tuned.conf file (bsc#1124453)- use \';\' as new delimiter for a sed command in postinstall script, because the used \'%\' is used and expanded by rpm macros. (bsc#1150868, bsc#1150870)
* Wed Jan 30 2019 abrielAATTsuse.com- source /etc/sysconfig/sapconf entries correctly, even if the /etc filesystem is read-only (bsc#1122741)- log skipping of existing /etc/systemd/logind.conf.d/sap.conf file during package installation (bsc#1111243)
* Mon Aug 27 2018 abrielAATTsuse.com- Do not change the system settings for kernel.sem. So remove the variables SEM
* from sapconf. (bsc#1099101)
* Fri Jun 15 2018 abrielAATTsuse.com- correct the SAP Note references in the man pages and in the sysconfig file of the sapconf package (bsc#1096498)
* Fri May 18 2018 abrielAATTsuse.com- never ever stop or disable uuidd.socket in sapconf. It is mandatory for every SAP application running. (bsc#1093843)- remove hardcoded default value for VSZ_TMPFS_PERCENT. This allows an admin to exclude VSZ_TMPFS settings from the sysconfig file, so current system value will remain untouched. This value only got used in the previous version, if the variable VSZ_TMPFS_PERCENT was removed from the sapconf configuration file /etc/sysconfig/sapconf. If the value of the variable was only changed (increase or decrease) in the sapconf configuration file everything works fine. (bsc#1093844)
* Fri Apr 13 2018 abrielAATTsuse.com- remove the no longer needed sysconfig file \'/etc/sysconfig/sapnote-1680803\' in any update case. (bsc#1089549)
* Thu Apr 12 2018 abrielAATTsuse.com- sapconf will set ALL values specified in the file /etc/sysconfig/sapconf irrespective of the current system value. The values will be not just increase, but also decrease, if the value in the sysconfig file is lower than the current system value. All actions are logged to /var/log/sapconf.log (fate#325548)- change variable names in sysconfig file for the avoidance of doubt (bsc#1070495)- remove unnecessary TMPFS_SIZE_MIN from sysconfig file (bsc#1070496)
* Fri Apr 06 2018 abrielAATTsuse.com- remove the pagecache references from the sysconfig file during the package update from SLE12 to SLE15 (bsc#1071539)
* Mon Mar 26 2018 abrielAATTsuse.com- consolidate the 4 former sapconf profiles sap-hana, sap-netweaver, sap-ase and sap-bobj to one basic sapconf profile \'sapconf\' as requested by SAP. If one of the former profiles is the currently active tuned profile, the active tuned profile will be reset to the \'sapconf\' profile during the update installation of the package. Additionally the no longer needed sysconfig file \'/etc/sysconfig/sapnote-1680803\' will be removed during the package update. (fate#324489, bsc#1070504)
* Tue Mar 13 2018 abrielAATTsuse.com- add directive ExecStop to the systemd unit file sapconf.service and start sapconf.service after initial package installation (fate#325363)
* Mon Mar 12 2018 abrielAATTsuse.com- add system unit file sapconf.service to start tuned, uuidd.socket and sysstat during system boot and to restart tuned during package update installation so that the changes will take effect immediately (fate#325363)- remove left over pagecache limit references (bsc#1071539)
* Thu Feb 22 2018 abrielAATTsuse.com- Remove sapconf legacy interface /usr/lib/systemd/system/sapconf.service /usr/sbin/SAPconf /usr/sbin/rcsapconf /usr/sbin/sapconf The man pages are adapted to reflect the changed handling. (bsc#1070505, fate#324490)
* Tue Dec 19 2017 abrielAATTsuse.com- Check, if pagecache limit is available at the system. If yes, set pagecache limit according the settings in /etc/sysconfig/sapconf. If not, log a message to the log file. (bsc#1071539, fate#323778)
* Tue Dec 05 2017 abrielAATTsuse.com- Refactoring sapconf parameter settings together with SAP Linux Lab. (fate#324491)- ATTENTION: One main feature of this sapconf package update to version 4.1.12 is a consolidation of all sapconf configuration settings into the central /etc/sysconfig/sapconf configuration file (except those settings related to ASE or BOBJ and those settings which can only be set via tuned.conf) This will result in a lot of configuration file changes concerning /etc/sysconfig/sapconf, /etc/sysconfig/sapnote-1557506, /usr/lib/tuned/sap-netweaver/tuned.conf and /usr/lib/tuned/sap-hana/tuned.conf. That means that your system configuration get changed after a restart of tuned or during a system reboot. Please read carefully the following information about configuration file handling before restarting tuned or rebooting the system. (bsc#1070508)- use the same tuning values for HANA and Netweaver workloads. That means the use of the same tuned.conf and script.sh file for both profiles (sap-hana and sap-netweaver) This should lead to a better base for mixed HANA and ABAB workloads on one system. (bsc#1070508)- the pagecache configuration is now integrated in the general sapconf sysconfig file and the old sysconfig file sapnote-1557506 is obsolete. As before pagecache handling is disabled by default. ATTENTION: configuration file handling during package installation. During an initial package installation the new sysconfig file, which includes the pagecache values from the former file sapnote-1557506, is copied to /etc/sysconfig/sapconf and the changes will take effect immediately after restarting tuned. During a package update previously copied /etc/sysconfig files will exist. If both files in /etc/sysconfig are unchanged - that means, there are no custom changes present - the new sysconfig file is copied to /etc/sysconfig, the old obsolete /etc/sysconfig/sapnote-1557506 is removed and the changes will take effect immediately after restarting tuned. If the file /etc/sysconfig/sapconf is unchanged - that means, there are no custom changes present - but the file /etc/sysconfig/sapnote-1557506 contains custom modifications, the new sysconfig file is copied to /etc/sysconfig, the changed values from /etc/sysconfig/sapnote-1557506 are copied to /etc/sysconfig/sapconf and /etc/sysconfig/sapnote-1557506 is moved to /etc/sysconfig/sapnote-1557506.rmpsave. The changes will take effect immediately after restarting tuned. If the file /etc/sysconfig/sapconf contains custom modifications, the new sysconfig file is copied to /etc/sysconfig as sapconf.rpmnew. Custom modifications from /etc/sysconfig/sapnote-1557506 - if available - are not merged in this new file. Please merge the needed custom modifications manually from both files into /etc/sysconfig/sapconf.rpmnew, move this file to /etc/sysconfig/sapconf and remove /etc/sysconfig/sapnote-1557506 before you restart tuned to get the changes take effect. (bsc#1070496, bsc#1070508)- The following parameters are additional specified (instead of static tuning inside the tuning script or defined in other configuration files like tuned.conf or sapnote-1557506) or changed in the central configuration file /etc/sysconfig/sapconf. vm.max_map_count, vm.dirty_bytes, vm.dirty_background_bytes, kernel.shmmni, net.ipv4.tcp_slow_start_after_idle, ksm, transparent_hugepages, numa_balancing added and value changed vm.pagecache_limit_ignore_dirty, vm.pagecache_limit_mb added and commented out kernel.shmall, kernel.shmmax, kernel.sem changed But be in mind: higher system value will ever remain unchanged. sapconf will respect higher values set by the system or by the administrator using sysctl configuration files. Values set with sysctl command will respect too, but do not survive a system reboot. Every tuning action is logged to /var/log/sapconf.log ATTENTION: configuration file handling during package installation. During an initial package installation the new sysconfig file is copied to /etc/sysconfig and the changes will take effect immediately after restarting tuned. During a package update a previously copied /etc/sysconfig file will exist. If this file in /etc/sysconfig is unchanged - that means, there are no custom changes present - the new sysconfig file is copied to /etc/sysconfig and the changes will take effect immediately after restarting tuned. If this file in /etc/sysconfig includes custom modifications, the new sysconfig file is copied to /etc/sysconfig as sapconf.rpmnew. Please merge the needed custom modifications into /etc/sysconfig/sapconf.rpmnew and move this file to /etc/sysconfig/sapconf before you restart tuned to get the changes take effect (bsc#1070494, bsc#1070495, bsc#1070496, bsc#1070508)- The following parameters were specified in tuned.conf of profile sap-hana and/or sap-netweaver before. But they are removed from tuned.conf because they are redundant, no SAP Note is mentioned it, replaced by another parameter, moved to another configuration file or commented out, because they are only valid for a special architecture or special tasks (like the [cpu] part was only valid for Intel architecture and only performance related) vm.swappiness, kernel.sched_min_granularity_ns, kernel.sched_wakeup_granularity_ns, readahead removed [cpu] section with governor, energy_perf_bias, min_perf_pct commented out vm.dirty_ratio, vm.dirty_background_ratio removed from tuned.conf replaced by vm.dirty_bytes, vm.dirty_background_bytes defined in sysconfig/sapconf kernel.sem, net.ipv4.tcp_slow_start_after_idle, transparent_hugepages moved to sysconfig/sapconf ATTENTION: these changes will take effect immediately after restarting tuned. Except the administrator is using an own copy of the tuned.conf file in /etc/tuned/ (where may be sap-hana or sap-netweaver) to set own or changed values. The tuned.conf files in /etc/tuned/ remain untouched during package installation. To get the new behaviour SAP is recommended, remove the profile copy from /etc/tuned or copy the new tuned.conf file from /usr/lib/tuned/ to /etc/tuned/ or compare the files in /etc/tuned/ with the files in /usr/lib/tuned/ manually and adjust the content, if needed. (bsc#1070494, bsc#1070495, bsc#1070496, bsc#1070503) (bsc#1048550, bsc#1064720)- Setting of UserTasksMax, a parameter of the systemd login manager, will be done in the post script during the package installation. The value is set to \'infinity\'. Note: A reboot is needed after the first setup to get the change take effect. A message will indicate if a reboot is necessary. As before there is no automatic rollback. (bsc#1070386)- enable and start sysstat service during post script of the package installation (see SAP Note 1310037) (bsc#1070390)- add package requirements including a short description to the man page of sapconf and to the central configuration file /etc/sysconfig/sapconf (bsc#1070390)- Update the sapconf man page and associated man pages to reflect all the changes of sapconf package version 4.1.12 (bsc#1070506)- respect active tuned profile during reboot of the system even if it is not a \'sap\' profile. sapconf only activates sap-netweaver profile by default, if NO tuned profile is actually set. (bsc#1026862)- reinsert \'elevator=noop\' to tuned.conf of profile sap-hana and sap-netweaver. (bsc#1031073, bsc#1032516, bsc#1070494)
* Mon Sep 18 2017 abrielAATTsuse.com- fix variable name for pagecache handling (bsc#1057986)
* Thu Aug 10 2017 abrielAATTsuse.com- restrict UserTasksMax setting to os releases > 12.1
* Fri Aug 04 2017 abrielAATTsuse.com- add SLE12-SP1 specific change for UserTasksMax (bsc#1039309 and comment #35 of bsc#1031355)
* Thu Aug 03 2017 abrielAATTsuse.com- add a message to %post to remind the admin to restart the tuned service, if he want the configuration changes to take effect immediately (bsc#1048550)
* Thu Aug 03 2017 abrielAATTsuse.com- increase MAX_MAP_COUNT_REQ to 2147483647, see SAP Note 900929 (bsc#1048550)
* Thu Jul 27 2017 hguoAATTsuse.com- Update package description.- Make \"tuned\" a mandatory runtime dependency to address bsc#1043844.- In all tuning profiles, do not overwrite a parameter if present value is higher than optimal value. (bsc#1048550)
* Wed Jun 21 2017 abrielAATTsuse.com- Amend logind\'s behaviour (bsc#1031355, bsc#1039309, bsc#1043844)
* Mon Jun 12 2017 abrielAATTsuse.com- Add a dependency against the package sapinit-systemd-compat to prevent SAP systems to be stopped every time the SAP Host Agent is restarted (SLE12-SP1 only) (bsc#1043841)
* Thu Apr 27 2017 abrielAATTsuse.com- add new profiles for SAP ASE (Sybase) and SAP BOBJ according to fate#320359.
* Thu Apr 06 2017 hguoAATTsuse.com- Upgrade to upstream version 4.1.7 that addresses exactly one issue: Lee Martin and colleagues noticed that SAP HANA performs better with \"force_latency=70\" in its tuning profile, so the setting is now introduced to the profile. (bsc#1032516)
* Mon Mar 27 2017 hguoAATTsuse.com- Upgrade to upstream version 4.1.6 that addresses exactly one issue: sapconf\'s sap-hana tuning profile incorrectly uses \"noop\" IO scheduler on disk block devices, which is not explicitly recommended by either SUSE or SAP. Performance regression showed up during benchmark runs. Hence, the IO scheduler setting is removed from tuning profile, and left to be decided by end-user. (bsc#1031073)
* Mon Mar 06 2017 hguoAATTsuse.com- Use arbitrary precision calculator rather than bash\'s built-in integer calculator to calculate parameter values, this gets rid of all integer overflow issues observed in production. (bsc#1027411)- Apply tuning technique of Netweaver in HANA profile too. (bsc#1016795) Upgrade to upstream version 4.1.5.
* Fri Feb 17 2017 hguoAATTsuse.com- \"force_latency=1\" is removed from HANA\'s configuration, so that CPUs are no longer kept busy when idling. (bsc#1025824)- Introduce complementary README.d and LICENSE files from upstream git repository.
* Tue Nov 29 2016 hguoAATTsuse.com- Do not touch THP configuration in Netweaver profile, avoid inheriting configuration from high throughput profile. (bsc#994306)
* Wed Jul 27 2016 hguoAATTsuse.com- Put version number in source archive name.- Fix a race condition during start (bsc#977575).
* Mon Jul 04 2016 hguoAATTsuse.com- Start uuidd.socket as soon as the package is installed. Further fix bsc#983454.
* Tue Jun 07 2016 hguoAATTsuse.com- Control uuidd as a step of the tuning process. Fix bsc#983454.
* Mon May 02 2016 hguoAATTsuse.com- Introduce mandatory dependency on package tuned. Implement fate#320783.
* Thu Mar 31 2016 hguoAATTsuse.com- Redo the directory structure in the source archive file.- Introduce /etc/sysconfig/sapnote-1557506 to:
* Disable pagecache_limit by default.
* Let user decide if and how to tune pagecache_limit. Fix bsc#966930 and bsc#971625.
* Tue Feb 23 2016 hguoAATTsuse.com- Mention tuned parameters in manual pages: fix bsc#966720
* Fri Jan 15 2016 hguoAATTsuse.com- Fix a misplaced optimisation routine that should have been applied to SAP HANA but in fact applied to SAP NetWeaver. (bsc#962059)
* Mon Sep 28 2015 hguoAATTsuse.com- Implement fate#319480 - [ECO] Include tuned architecture in sapconf
* Replace the entire sapconf package content with tune daemon SAP profiles,
* The executables remain compatible with the original sapconf implementation.
* Following files are removed from package source: LGPL README SAPconf SAPconf-reconfig SAPconf.8 config.b64 functions sapconf sapconf.8 sapconf.service
* Following file is added into package source: sapconf.tgz