--- canonical: https://safekit.evidian.com/products/high-availability-software-for-application-clustering/safekit-release-notes-8-2/ SafeKit 8.2 Release Notes — Part 2 of 7 — Major Changes 8.2 vs 7.5: Web Console, Web Service & Logs (sections 2.1.1–2.1.3) --- # 2. Major changes ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Major_changes_between) 2.1 Major changes between SafeKit 8.2 and SafeKit 7.5 ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Major_Changes_between_15) 2.2 Major changes between SafeKit 7.5.2 and SafeKit 7.5.1 ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Major_Changes_between_13) 2.3 Major changes between SafeKit 7.5.1 and SafeKit 7.4.0 ![*](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20266%20201'%3E%3C/svg%3E)![*](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image001.png)       [Section](#_Major_Changes_between_14) 2.4 Major changes between SafeKit 7.4.0 and SafeKit 7.3.0   This section gives the list of new features introduced in SafeKit since release 7.4. Go to [section](#_Restrictions_and_Known) 3 and carefully read known problems about SafeKit releases and to [section](#_Migration_Instructions) 4 for migration instructions. ## 2.1      Major changes between SafeKit 8.2 and SafeKit 7.5 Version 8.2.1 is a consolidation of version 8.2.0. Upgrading from 8.2.0 to 8.2.1 is minor upgrade and follow the standard procedure. Version 8.2.2 is an improvement of version 8.2.1. Upgrading from 8.2.1 to 8.2.2 is minor upgrade and follow the standard procedure. Version 8.2.3 is an improvement of version 8.2.2. Upgrading from 8.2.2 to 8.2.3 is minor upgrade and follow the standard procedure. Version 8.2.4 is an improvement of version 8.2.3. Upgrading from 8.2.3 to 8.2.4 is minor upgrade and follow the standard procedure. During this upgrade, you may encounter the issue described in [SK-0100](https://customercare.evidian.com/space/PDA/1470005313/Knowledge+Base+-+SafeKit+7.5++&+8.2#SK-0100---Windows-&-Linux). It only occurs in the unusual case where a farm module has been configured without encryption for module communications. Version 8.2.5 is an improvement of version 8.2.4. Upgrading from 8.2.4 to 8.2.5 is minor upgrade and follow the standard procedure. ### 2.1.1          New ergonomic web console SafeKit web console has evolved to offer a more ergonomic and pleasant user experience. It is loaded by connecting a web browser to (where host is the name or IP address of one of the SafeKit servers) and offers a navigation side bar with 2 selections: ·         ![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2016%2013'%3E%3C/svg%3E)![](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image005.png) Configuration to configure the cluster and the modules. Configuration is only authorized to users that have Admin role. By default, the admin user has the Admin role. The configuration wizard has evolved to: o    easily switch to advanced configuration o    configure module checkers with form (since SafeKit 8.2.1) ·         ![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2018%2013'%3E%3C/svg%3E)![](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image006.png) Monitoring to monitor and control the configured modules. Monitoring is authorized to users that have Admin, Control and Monitor roles. With Monitor role, actions on modules (start, stop…)  are prohibited. The module log is now displayed in real time, and its analysis has been improved. For details, see section “The SafeKit web console” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). Since SafeKit 8.2.1: ·         browser notifications are emitted on module state change if the user has allowed them, and the URL is https or http://localhost ·         the language is automatically selected according to the browser’s language preference. At the time this document is written, only English and French are supported. Since SafeKit 8.2.2: ·         addition of button ![Une image contenant noir, obscurité Description générée automatiquement](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2022%2013'%3E%3C/svg%3E)![Une image contenant noir, obscurité Description générée automatiquement](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image007.png) to open/close details for the module on this node (logs, resources…). ·         addition of button on ![Une image contenant noir, obscurité Description générée automatiquement](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%2015%2013'%3E%3C/svg%3E)![Une image contenant noir, obscurité Description générée automatiquement](https://safekit.evidian.com/wp-content/uploads/downloads_safekit/version-82/safekit82releasenotes_fichiers/image008.png) to open/close the module states timeline on all nodes where it is installed. This provides a global view of the module's state on the cluster. Be aware that the clocks of the two nodes must be synchronized for the mapping of state changes to be meaningful. Since SafeKit 8.2.3: ·         addition of action field for configuring tcp and ping checker ·         transformation into a PWA (Progressive Web) App for mobile use. Supported only with https or ·         addition of a list of connection nodes to allow connection to another node with a single click. The list is built from the servers defined in the cluster. Ability to export and import this list in JSON format. Since SafeKit 8.2.4: ·         addition of the ability to dynamically enable or disable the module startup at boot for maintenance purposes   Note that legacy URLs to access the web console are no longer supported: ·         [deploy.html, control.html, monitor.html, manage.html](http://host:9010/control_and_monitor.html) for the main tabs Instead, with SafeKit 8.2.4, the monitoring and control is provided by /console/en/monitoring and the configuration by /console/en/configuration  ·         monitor\_and\_control.html and monitor\_only.html for limited restricted access to the console Instead, SafeKit 8.2.4 provides a special URL with the keyword limited that disables the navigation to the Configuration: [/console/en/limited](http://localhost:9010/console/en/limited). However, as this restriction is lifted simply by removing limited keyword from the URL, it is recommended to restrict access by specifying a group for each role (Admin, Control, Monitor) and then assigning each user to a given group. For details, see section “Manage users and groups” for “User authentication setup” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). ### 2.1.2          SafeKit web service enhancement Since the new console relies on a new SafeKit API, the console delivered with SafeKit 8 can only administer SafeKit 8 servers, which cannot be administered with an older console. The Apache configuration of the SafeKit web server has been modified and enhanced to: ·         implement the new API and remove the legacy one ·         simplify user customization into SAFE/web/conf/httpd.conf ; for details, see section “Configuration of the SafeKit web service” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf) ·         offer OpenID authentication ; for details see section “OpenID authentication setup” in the [*SafeKit User’s Guide*](https://customercare.evidian.com/space/OPD/1208320038/SafeKit+8.2?attachment=https://customercare.evidian.com/download/attachments/1208320038/safekit82userguideen.pdf&type=application/pdf&filename=safekit82userguideen.pdf). In Linux, when configuring OpenID with the Apache module mod\_auth\_openidc: o    all the cluster nodes must use the same version of mod\_auth\_openidc o    If mod\_auth\_openidc is >= 2.4.15, you must edit /opt/safekit/web/conf/httpd.conf to uncomment the line: # Define openidc\_2\_4\_15 | | | | --- | --- | | Commentaire important contourCommentaire important contour | Since SafeKit 8.2.3, OpenID authentication works only with HTTPS. | ·         Client certificate authentication is no more documented while still supported. ·         Since SafeKit 8.2.1, the user is automatically logged out after 8 hours of inactivity. This is the default value as defined by the SessionMaxAge variable into SAFE/web/conf/httpd.conf. ### 2.1.3          SafeKit logs enhancement #### 2.1.3.1       System log Since SafeKit 8.2, main module log messages are also logged into the system log. To display SafeKit messages: ·         in Windows, in a PowerShell console, run Get-EventLog -Logname Application -Source Evidian.SafeKit  ·         in Linux, in a terminal, run journalctl -r -t safekit #### 2.1.3.2       Module log Module log messages have been requalified and now include levels: ·         U(ser) for action executed by the user (start/stop of the module…) ·         E(vent) for major events on the module (state changes…) ·         C(ritical) for critical events that require attention ·         S(cript) for user script execution (start\_prim/stop\_prim…) Other levels are for support and debug purpose.   In previous SafeKit releases, some users used to search for the keyword *atleast* to look for process/service monitoring error detection. For instance, errd used to log: | 2023-10-12 10:15:42:447000|errd | E | event atleast on proc idsyncsrv.exe Since SafeKit 8.2, errd logs: | 2023-10-12 10:15:42:447000 | errd | E | Process idsyncsrv.exe not running #### 2.1.3.3       Module scripts log Before SafeKit 8.2, output messages of user scripts were stored into **SAFEVAR/modules/AM/userlog.ulog**(where AM is the module name). Since SafeKit 8.2, a log is created on each user script execution and is stored into  **SAFEVAR/modules/AM/userlog\_AAAA\_MM\_DDThhmmss\_