Skylar One 12.5.23 Release Notes

ScienceLogic strongly recommends that you review the installation and upgrade instructions, important upgrade notes, and known issues for this release before installing or upgrading to Skylar One 12.5.23.

Skylar One 12.5.23 includes platform and security updates and addresses several issues from previous releases.

These release notes provide a comprehensive list of the features, enhancements, and addressed issues that are included in the Skylar One 12.5.23 release.

To view the updates that are included in previous Skylar One releases, see the following release notes:

• 12.5.20
• 12.5.21
• 12.5.22

Before You Proceed

If you are planning to consume Skylar One 12.5.23, be advised of the following:

• The 12.5.23 release is available as both an ISO and patch.

• All Python 2 functionality was removed from Skylar One with the 12.5.1 release. If you still use Python 2 for custom code, you cannot upgrade to this or any later releases until your custom code is Python 3-compatible.

• You can perform upgrades from one minor version to any later minor version within the 12.5.x series. However, as with all updates, ScienceLogic strongly recommends that you perform such upgrades in a test environment before implementing the upgrades in production environments.

• The ScienceLogic-validated upgrade paths to version 12.5.23 are outlined below.

  • 12.5.22 > 12.5.23

  • 12.5.20 > 12.5.23

  • 12.5.8 > 12.5.23

  • 12.5.4 > 12.5.23

  • 12.5.1 > 12.5.23

  • 12.3.15 > 12.5.23

  • 12.3.11 > 12.5.23

• 12.5.23 supports STIG deployments. However, STIG-compliant users should contact their ScienceLogic account managers for important information about upgrading to this release.

• AWS deployments that are using Aurora 3 can upgrade to this release.

• The Enterprise Key Management Service (EKMS) is enabled by default in 12.5.23.

• If you are currently on a version of Skylar One prior to 12.5.20 and you use local authentication with an MD5-hashed password, you must reset your password when upgrading to Skylar One 12.5.20 or later.

For more information about issues that might impact your upgrade, see the Important Upgrade Notes and Known Issues sections.

New Features and Enhancements in Skylar One 12.5.23

This section describes the new features and enhancements that are included in Skylar One 12.5.23.

Access Control

• Reverted an enhancement from Skylar One version 12.5.20 that required users to have the AP_ACCESS access hook aligned to their user policy to log in to either the default Skylar One user interface (AP2) or the classic user interface.

Platform and Security

• Skylar One version 12.5.23 includes package updates to improve security and system performance.

Issues Addressed in Skylar One 12.5.23

This section describes the issues that were addressed in Skylar One 12.5.23.

Device Management

• Ensured that you can enter multiple, comma-separated device names in the Names Contain field of the Device Bulk Merge modal, making it easier to search for multiple devices. (Case: 00685762) (Jira ID: EM-80510)

• Resolved an issue where manually deleting a device from the user interface appeared to fail, even though the deletion completed successfully in the background. (Case: 00461971) (Jira ID: EM-66827)

• Addressed an issue that prevented vanished devices from being purged when they were vanished for longer than the Component Purge Timeout setting value. (Case: 00675537) (Jira ID: EM-80375)

Discovery

• Added Server Name Indication (SNI) support to the SSL certificate discovery process. (Case: 00504202) (Jira ID: EM-73065)

PowerPacks

• Resolved an issue that prevented you from adding content objects from the Skylar One user interface to a PowerPack on STIG-compliant systems. (Jira ID: EM-80874)

Reporting

• Resolved an issue that resulted in report templates being deleted from the Central Database during daily maintenance if the data retention setting for ad hoc and scheduled reports was set to anything greater than 0 days. (Case: 00706562) (Jira ID: EM-81023)

Run Book Automation

• Addressed an issue that caused run book automation actions to intermittently fail with a "Failed to acquire lock" error after upgrading to Python 3-based run book automation. (Case: 00676951) (Jira ID: EM-80438)

System Update

• Addressed an issue where installing an incorrect, platform-specific patch hook during the package import phase caused inconsistencies in the patch hook versioning. (Jira ID: EM-80550)

• Resolved an issue where the preupgrade status did not include already deployed appliances when the check was re-executed after a deployment completed. (Jira ID: EM-80138)

Installing and Upgrading Skylar One

For a detailed overview of Skylar One, see the Introduction to Skylar One manual.

For detailed instructions on performing a new installation of Skylar One, see the Installation and Initial Configuration manual.

For detailed instructions on upgrading Skylar One, see the section on Updating Skylar One in the System Administration manual and the upgrade notes that are included in this document.

Skylar One Extended Architecture

For existing on-premises deployments of Skylar One Extended Architecture, see the section on Upgrading Skylar One Extended Architecture in the System Administration manual for upgrade instructions. For help with technical issues, contact ScienceLogic Customer Support.

 New installations of Skylar One Extended Architecture are available only on SaaS deployments.

Important Upgrade Notes for Skylar One 12.5.23

This section includes important notes for upgrading existing Skylar One systems to the 12.5.23 release.

Unless otherwise stated, the information in this section applies to all users who are upgrading from previous versions.

ScienceLogic strongly recommends that you review these notes in their entirety before upgrading to version 12.5.23.

Supported Upgrade Paths

The ScienceLogic-validated upgrade paths to version 12.5.23 are outlined below.

• 12.5.22 > 12.5.23

• 12.5.20 > 12.5.23

• 12.5.8 > 12.5.23

• 12.5.4 > 12.5.23

• 12.5.1 > 12.5.23

• 12.3.15 > 12.5.23

• 12.3.11 > 12.5.23

For more information about supported upgrade paths for Skylar One releases, see the Skylar One Recommended Upgrade Paths section in the System Administration manual.

Pre-Import Script for Upgrade Efficiency

Beginning with 12.5.1, the system update import experience was improved to make it faster and more efficient by allowing you to run concurrent imports. This feature is not enabled by default. To enable it, download the patch bundle you want to import, then run the following script:

silo_mysql -e "INSERT INTO master.system_settings_patcher (param, value, description) VALUES ('use_concurrent_import', 1, 'Use concurrent patch import');"

After running the script, you can start the import process.

STIG Support

STIG-compliant users can deploy this release as an ISO.

12.2.x and 12.3.x STIG-compliant users should contact their ScienceLogic account managers for information about upgrading to this release.

When deploying a STIG-compliant configuration, port 7700, the Web Configuration Utility, and the Database Tool page are all disabled. In addition, concurrent network interface collection is not supported for these deployments.

Upgrading MariaDB and Rebooting Skylar One

All Skylar One versions include important package security updates. To apply these updates, you must upgrade MariaDB and then reboot all Skylar One appliances. The following table specifies the required MariaDB version for each Skylar One version:

Skylar One Release	Release Type	Required MariaDB Version
12.5.23	ISO and upgrade	10.11.16
12.5.22	Upgrade only	10.11.16
12.5.21	Upgrade only	10.11.16
12.5.20	ISO and upgrade	10.11.16
12.5.8	Upgrade only	10.6.21
12.5.7	Upgrade only	10.6.21
12.5.6	Upgrade only	10.6.21
12.5.5	Upgrade only	10.6.21
12.5.4	ISO and upgrade	10.6.21
12.5.3	Upgrade only	10.6.21
12.5.2	Upgrade only	10.6.21
12.5.1	ISO and upgrade	10.6.21
12.3.15	Upgrade only	10.6.18
12.3.14	Upgrade only	10.6.18
12.3.13	Upgrade only	10.6.18
12.3.12	Upgrade only	10.6.18
12.3.11	ISO and upgrade	10.6.18
12.3.10	Upgrade only	10.6.18
12.3.9	Upgrade only	10.6.18
12.3.8	Upgrade only	10.6.18
12.3.7	ISO and upgrade	10.6.18
12.3.6	Upgrade only	10.6.18
12.3.5	Upgrade only	10.6.18
12.3.4	Upgrade only	10.6.18
12.3.3	Upgrade only	10.6.18
12.3.2	Upgrade only	10.6.18
12.3.1	ISO and upgrade	10.6.18
12.3.0	ISO and upgrade	10.6.18

Clearing Cache Post-Upgrade

After upgrading to version 12.5.23, you should clear your system cache to remove cached items from Skylar One (SL1) and prevent several potential issues that can occur post-upgrade due to caching. To do so, go to Misc > Clear SL1 Cache.

Required Ports

Beginning with SL1 12.2.0, if you have a firewall between your Database Server, data engine, and Administration Portal appliances, you should open TCP port 8200 to facilitate communication between those appliances.

For a full list of ports that must be open on each Skylar One (SL1) appliance, see the section on Required Ports for Skylar One in the Installation and Initial Configuration manual.

Python 3.9 Execution Environment Support Deprecation

The 12.3.0 release removed support for Python 3.9 and added support for Python 3.11. For more information, see the section Important Notes on Creating ScienceLogic Libraries in the ScienceLogic Libraries and Execution Environments manual.

Pre-Upgrade Script for Avoiding Database Synchronization Failures

There is a known issue that might cause the upgrade to 12.5.23 to fail during post-update with a "Database Synchronization failed after 3 attempts" error in both the UI logs and the /var/log/em7/patch_manager.log file. For more information about this issue, including a pre-upgrade script you can run to avoid it, see https://support.sciencelogic.com/s/article/21802.

PowerPack Encryption When Upgrading from 12.3.x and Earlier

When upgrading Skylar One to version 12.5.23 from 12.3.x or earlier, PowerPacks that use legacy encryption will become read-only. This issue does not impact upgrades from previous 12.5.x releases. For more information about this issue, including resolution steps, see https://support.sciencelogic.com/s/article/20806.

Use of tmux When Using SSH

In Skylar One (SL1) versions 12.3.4 and later, the tmux utility is disabled by default if you are on a non-STIG deployment and access a Skylar One system using SSH. ScienceLogic strongly encourages non-STIG users on these versions to enable the tmux utility prior to using SSH sessions, such as for upgrading MariaDB, to avoid SSH sessions timing out after 15 minutes.

If you are on a STIG-compliant Skylar One deployment, or if you are on a non-STIG deployment between versions 12.2.1.1 and 12.3.3, the tmux utility is enabled by default.

The tmux utility, which is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen, strengthens session-control mechanisms and aligns with industry-wide security practices.

If tmux is enabled, sessions are automatically locked after 15 minutes of idleness or if an unclean SSH disconnect or dropped SSH connection occurs. Upon login, Skylar One checks for and attaches any detached tmux session if it finds one; otherwise, it starts a new session.

The utility also facilitates advanced features like scroll-back buffering with search, built-in clipboarding, multiple sessions and panes, detaching or attaching sessions, and session supervision or sharing.

To enable the tmux utility in non-STIG deployments: 

1. Either go to the console of the Skylar One appliance or use SSH to access the appliance.

2. Open a shell session on the server.

3. Type the following at the command line to edit the silo.conf file:

   sudo visilo

4. Change the following line in the [OS_HARDENING] section of the file to enable tmux:

   TMUX = true

   If the [OS_HARDENING] heading does not already exist in the silo.conf file, you must add that immediately above the TMUX = true setting.

5. Save and quit the file. (:wq).

6. Log out of Skylar One and then log back in. The tmux utility is now enabled.

For more information about tmux shortcuts and usage, see https://tmuxcheatsheet.com/.

Changes to High Availability and Disaster Recovery Configurations

In Skylar One (SL1) 12.3.2, the web server configuration for the vault service was updated to improve behavior between multiple database and data engine appliances. This was done to prevent false system events indicating that passive databases could not connect to Skylar One Collectors in high-availability (HA), disaster recovery (DR), or HA+DR configurations. With this update: 

• On new installations, you must run the following command after all database and data engine appliances are licensed, to populate the list of allowed locations where vault could be running: sudo /opt/em7/share/scripts/vault_add_servers.sh. If the list is populated successfully, the output tells you to restart nginx for the change to take effect. Upon updating, the list of allowed locations is generated automatically.

• If you are upgrading and you have not modified the default configuration file, then it is updated to this new configuration automatically.

• If you are upgrading and you have modified the default configuration file, the updated web server configuration is installed as /etc/nginx/conf.d/vault.conf.rpmnew. In this scenario, you must merge your modifications into the new configuration and then remove the .rpmnew extension.

System Update Notes

• Skylar One updates overwrite changes to the configuration file /opt/em7/nextui/nextui.env. (For more details, see https://support.sciencelogic.com/s/article/1423.) ScienceLogic recommends that you back up this file before applying an update and then reapply your changes to this file.
• ScienceLogic recommends that you run backups of your Skylar One system before performing a system update.
• The Skylar One user interface will be unavailable intermittently during system update.
• During the normal system update process, multiple processes are stopped and restarted. This might result in missed polls, gaps in data, and/or unexpected errors. ScienceLogic recommends that you always install Skylar One releases during a maintenance window.
• The Skylar One system update process starts a background process that can perform any required post-upgrade tasks. The post-patch update process is automatically stopped after 24 hours. However, depending on the size of your database as well as the version from which you are upgrading, the post-upgrade tasks can take several days to perform. If the post-patch update process is stopped after 24 hours, the process will automatically restart and continue processing from the point at which it was stopped. If you see an event that indicates the post-patch update process was stopped, you do not need to contact ScienceLogic support for assistance until you see the same event for three consecutive days.
• When upgrading a large number of Skylar One appliances, you might encounter an issue where the deployment summary shows that deployment timed out for many of the appliances but, upon further inspection, you discover that the appliances actually deployed correctly. This is due to a lag in the deployment status reaching the Database Server after the default timeout value of 3600 seconds (1 hour). If you check back later, the issue should fix itself. If you would rather work around this issue, you can increase the timeout value. For instructions, see the section on Adjusting the Timeout for Slow Connections in the "Updating Skylar One" chapter of the System Administration manual.
• When upgrading Skylar One on AWS stacks, you might receive an error message that the Data Engines failed to patch correctly. If this occurs, re-run the pre-upgrade tests and then run the patch again; this should result in the Data Engines updating correctly and the correct version then being reflected on the Appliance Manager page (System > Settings > Appliances).
• After upgrading, to ensure proper data collection, you should go to the Appliance Manager page (System > Settings > Appliances), locate one of the Data Collector or Message Collector appliances, and click the lightning bolt icon to force configuration push for that appliance.

Known Issues for Skylar One 12.5.23

ScienceLogic strongly recommends that you review all Known Issues for Skylar One. For more information, see https://support.sciencelogic.com/s/known-issues#sort=relevancy.

The following known issues exist for Skylar One 12.5.23:

Deployment and Configuration

• Deployment might fail on remote appliances with a "Vault configuration error: decrypt" message. This typically occurs during the payload upload phase. To work around this issue, rerun the deployment task. (Jira ID: EM-79783)

System Upgrade

• 12.2.x and 12.3.x STIG-compliant users should contact their ScienceLogic account managers for information about upgrading to this release.
• The Patch hook task might fail on secondary Database Server and Administration Portal appliances when concurrent import is enabled during an upgrade. To work around this issue, manually upgrade the siloupdate RPM on the affected appliances. (Jira ID: EM-79882)
• When upgrading Skylar One to version 12.5.23 from 12.3.x or earlier, PowerPacks that use legacy encryption become read-only. This issue does not impact upgrades from previous 12.5.x releases. For more information about this issue, including resolution steps, see https://support.sciencelogic.com/s/article/20806. (Jira ID: EM-73018)
• If a system has consumed many Skylar One (SL1) patch imports, the master_filestore.storage_system_patch database table might grow too large. This causes login attempts to either fail with the error "The table 'organizations_log' is full" in the default Skylar One user interface (AP2), or fail silently in the classic user interface. To work around this issue, clean up previous patch import files after each version deployment. For more information, see https://support.sciencelogic.com/s/article/18285. (Jira ID: EM-75727)
• After updating your system, you might experience an issue where the user interface is not displaying or working as intended. If this occurs, clear your browser cache. (Jira ID: EM-73859)
• During deployment, the siloupdate-deploy-local service might display the following log messages, although in both cases, the deployment task still ultimately completes:
  • On primary databases, it displays "Failed to enqueue storage object. Error: 'charmap' codec can't encode…" in journalctl. (Jira ID: EM-78481)
  • On secondary databases, it displays "ERROR 2002 (HY000): Can't connect to MySQL server on '127.0.0.1' (115)" in journalctl from the sl-otelcol post-install scriptlet. (Jira ID: EM-78479)
• If MariaDB has an interruption during the postupdate process, the deployment is initially marked as failed. After MariaDB becomes available again, the Version Update reruns and the appliance deployment is marked as complete. (Jira ID: EM-78499)
• The MariaDB upgrade process might fail with an error stating that /opt/em7/services/config.env does not exist. This prevents the siloupdate utility from stopping ScienceLogic services before proceeding with the database upgrade. (Jira ID: EM-75840)
• During a patch staging retry, an appliance that completes staging successfully might still be incorrectly reported as "Failed" in the staging summary. This is a reporting error and does not necessarily mean the files were not staged. (Jira ID: EM-79600)

Access Control

• You might be able to delete an account policy even if it is currently assigned to active accounts or authentication resources, which can cause you to experience orphaned configurations and authentication issues. (Jira ID: EM-79801)
• The system erroneously enables you to create an empty access key if you click Save without filling in any fields, which can lead to invalid or non-functional permission configurations. (Jira ID: EM-76409)

Agent

• Clicking the Upgrade button on the Agents page results in a message immediately appearing at the bottom of the page indicating that the upgrade was successful, though the upgrade was merely initiated. The actual upgrade process can take several minutes to complete. (Jira ID: EM-74365)
• When attempting to install a Gen-1 agent on an AWS stack, the installation user interface displays an incorrect IP for download, which results in the download attempt failing. (Jira ID: EM-74307)
• You might experience a scenario where an agent's polled data configuration is cleared unintentionally. (Jira ID: EM-74364)
• Discovery via Streamer Prime fails for Gen-1 Agent devices if the existing device record has a class_type of 0. This typically occurs when a device aligns before its backing PowerPack is fully installed or populated. (Jira ID: EM-79395)
• The Dead Letter Queue (DLQ) for streamer_push might erroneously indicate that it has exceeded its threshold. (Jira ID: EM-77934)

API

• Deleting a user account via the REST API (DELETE /api/account/<uid>) does not archive the account in the master_access.accounts_deleted database table, thus allowing the next account created to reuse the deleted account’s user ID (uid). (Jira ID: SLS-2044)
• The account API prevents the Aligned_organizations field from being set to null. As a result, users cannot disable additional organizations for a user via the API. (Jira ID: SLS-2081)
• Attempts to update device filesystem or Dynamic Application thresholds using the API (POST/PUT) might result in a "System internal error". (Jira ID: EM-76562)

Asset Management

• When creating or editing an asset, the values entered in the Administrator and Technician fields might not be saved. (Jira IDs: EM-74258, EM-76664)

Authentication

• A known issue with session cache management might cause Skylar One to log you out unexpectedly, or prevent you from logging in again after a recent session. If you experience either issue, you can work around it by clearing the cache of your web browser before you log into the Skylar One user interface. For more information, see https://support.sciencelogic.com/s/article/13701. (Jira ID: SLUI-21011)
• The Single Instance Login setting, which can be set on the Behavior Settings page (System > Settings > Behavior), is not working as designed for ASCII ADFS user accounts. (Jira ID: SLS-1559)
• If you create an empty authentication resource with no values filled in and assign it to an empty authentication profile, upon logging out of the system, the user interface becomes inaccessible. (Jira ID: EM-76608)
• You might intermittently encounter an error message when attempting to change your password or submit preference changes on the Account Preferences page (Preferences > Account > Preferences). (Jira ID: SLS-1949)
• If you attempt to save a single sign-on authentication resource without providing the required IdP Certificate, the form displays an error and resets all other fields, forcing you to re-enter all configuration data. (Jira ID: EM-79836)
• Password policy fields (Password Expiration, Password Shadowing, Require Password Reset, Password Strength) may appear as null in user account policies and cannot be updated through the user interface. These fields can be set directly via the Skylar One REST API using the following fields: 
  • passwd_expiration. Valid values are 0 (never) or 30, 60, 90, 180, or 365 (days).
  • passwd_prev_count. Valid values are 0 (last year), 1–10 (cannot reuse last [#] passwords).
  • passwd_reset_required. Valid values are 0 (no) or 1 (yes).
  • passwd_strength. Valid values are 0 (good), 1 (strong), or 2 (very strong).

Backup Management

• You should not use the SFTP protocol option when configuring backups at this time due to a known issue. (Jira ID: EM-81157)

Business Services

• The Anomalies tab on the Service Investigator page for device services might incorrectly display devices that have anomaly detection disabled, rather than showing only those devices with anomaly detection enabled. (Jira ID: EM-62884)

Credential Management and Discovery

• For an unguided device discovery, the Search box that displays for creating a new credential does not work. (Jira ID: SLUI-20777)
• When using the SNMP Public V2 credential to discover devices, you might see an unhandled exception in the system log near the end of the discovery session, despite the devices being discovered successfully. (Jira ID: EM-59380)
• The Credentials page in the default user interface (AP2) fails to display credentials that are not aligned with an organization, but displays these credentials correctly in the classic Skylar One user interface on the Credential Management page. (Jira ID: SLUI-20947)
• On the Credentials page, if you have more than 50 credentials and at least one of the first 50 credentials is not aligned with an organization, the page displays duplicates of these credentials. (Jira ID: SLUI-20947)
• You might get an error when trying to open SOAP/XML credentials that have been imported from a PowerPack. (Jira ID: EM-74291)

Dashboards

• Creating an Interface widget with the Leaderboard visualization, applying an advanced filter, and adjusting the data time span using the Time span filter results in an error. (Jira ID: SLUI-22200)
• When editing the scale prefix of a Device widget using the Leaderboard visualization, the Storage Used column does not update in that widget's table. (Jira ID: SLUI-22198)
• When editing an Events widget and setting the Refresh Mode field to None, the widget's events table shows the refresh mode as automatic, despite the change. (Jira ID: SLUI-21947)
• In classic dashboards, if you create a Traffic Light widget, the ability to control context in other subscribing widgets is not working as intended. (Jira ID: EM-76527)
• You might encounter incorrect values in Business Service dashboards and device metric trend charts when viewing physical memory aggregations due to a mapping error in the normalized database views causing physical memory sum data to track CPU activity instead. (Jira ID: EM-79948)
• The "Shared: Interface Billing" dashboard might generate a large number of console errors when loading, particularly on STIG systems. (Jira ID: EM-77611)
• When imported via a PowerPack, the "Custom Table: Journal Apps" dashboard widget's settings might appear, but selections do not display correctly. (Jira ID: EM-76599)
• The "Event Counts by Severity" widget fails to display any data when the event state is set to "Acknowledged," even if acknowledged events exist in the system. The widget correctly displays data only when set to "Unacknowledged." (Jira ID: EM-76286)

Data Collection and Retention

• If you include an invalid or incorrectly typed value in silo.conf, such as a word or phrase where it should be an integer, the data pull process crashes and cannot start. (Jira ID: EM-74238)
• When aligning a Dynamic Application that discovers a dynamic component map tree using Latin-1 and UTF-8 encoded device names and identifiers, you might receive "Illegal mix of collations" data storage errors in the system logs. (Jira ID: EM-74263)
• Some performance metrics and alert formulas display values with excessive decimal places instead of rounding to two. (Jira ID: EM-79390)
• Disabling interface collection can cause the "Interface Magic" service in the collector pipeline to crash with a ZeroDivisionError. (Jira ID: EM-72808)

Device Management

• On the Devices page, when sorting your search by the Organization column, the inventory table sorts by Organization ID instead. (Jira ID: SLUI-21459)
• The assigned organization for devices might not always update, even after performing a bulk alignment organization action on the Devices page. To work around this issue, refresh your browser immediately after completing the bulk alignment action. (Jira ID: SLUI-21483)
• When sorting by columns on the Device Investigator page in Firefox, the table might repeatedly fail to retrieve results. (Jira ID: SLUI-21095)
• The Device Categories page (Devices > Device Categories) fails to load properly whenever there is a category with a null ID. To work around this issue, go to the Device Categories page (System > Customize > Device Categories), locate the category with the null ID, and then remove that category by clicking the delete icon () next to the category. (Jira ID: SLUI-20731)
• The number of unacknowledged events in the Device Overview panel of the Device Investigator page does not update despite acknowledging alerts on a device. To work around this issue, add a new "unackEvents" subquery to the "Device Insights" query, then use that subquery to collect and retrieve information on unacknowledged events. (Case: 00471966) (Jira ID: SLUI-20858)
• When attempting to bulk delete devices or device components, a dialog message might indicate that some or all of the devices or components failed to delete, when they were actually deleted. (Jira ID: EM-74351)
• Device reports generated from the Classic Devices page (Devices > Classic Devices) might result in an "Uncaught TypeError" message appearing in the browser console, despite most reports generating correctly. (Jira ID: EM-74225)
• HTML device journal reports might generate with no data. (Jira ID: EM-74286)
• The checkbox to select all items on the Device Dashboards page (System > Customize > Device Dashboards) might select only the items that appear on your current page rather than all available device dashboards. (Jira ID: EM-74215)
• Event messages in device logs for multi-match events might display with the incorrect event ID. (Jira ID: EM-74409)
• After upgrading to 12.5.23, you might see multiple Attributes tabs on the Device Administration panel in the classic user interface. This issue does not affect ISO deployments. (Jira ID: EM-79933)
• The trend checkboxes on the Performance tab of the Device Reports panel do not always accurately update the graph display. Additionally, unchecking a trend does not hide the area fill, and re-checking it causes the trend to disappear entirely. (Jira ID: EM-79776)
• After successfully updating a device class on the Device Properties page, the system might erroneously display a "Device Class/Type Update Failed" error message. (Jira ID: EM-79472)
• After un-aligning a custom attribute from a device, the Custom Attribute Subscriber modal might incorrectly display all devices in the system. This is a visual issue only; it does not impact the actual alignment status. (Jira ID: EM-76508)
• Saving changes to a device's custom attributes might cause unset integer-based attributes to be automatically set to 0 rather than remaining null. (Jira ID: EM-76481)
• Changes made to a device template during the "Modify By Template" process are not saved to the template itself, even when you select the Save When Applied & Confirmed checkbox, preventing you from updating persistent templates while applying them to devices. (Jira ID: EM-74696)
• Nightly discovery might trigger a "TypeError" exception when updating interfaces for PowerShell-monitored devices. This issue appears in the storage process logs and affects the accuracy of interface IP updates. (Jira ID: EM-73781)
• You cannot submit bulk administrative requests on the Device Components or Device Hardware pages in the classic user interface. A "Loading…" message appears on the page and the submitted request fails. For more information, see https://support.sciencelogic.com/s/article/18343. (Jira ID: EM-73389)
• The "System Vitals Performance" graph might display a blank screen if a device is missing a collection label. (Jira ID: EM-77642)

Enterprise Key Management Service (EKMS)

• You might experience an issue where the EKMS state and vault contents disappear from your Data Collectors. If this occurs, you can work around the issue by going to the Appliance Manager page (System > Settings > Appliances) and manually running the Enterprise Database: Collector Config Push process to run on the impacted appliances. (Jira ID: EM-78522)
• Configuration backups do not include the master.vault_token table, so restoring from a config backup does not restore Vault token data. Users who depend on full database restores for recovery should ensure this information is backed up by other means. (Jira ID: SLS-1948)

Events and Alerts

• Deviation alerting does not support the use of double quotes in indices. To work around this issue, use single quotes. (Jira ID: EM-72050)
• The events on the Events page cannot be sorted by the Organization column. (Jira ID: SLUI-20903)
• From the Event Policies page (Events > Event Policies), you can delete only a single event policy at a time, even if you select multiple event policies for bulk deletion. (Jira ID: SLUI-20853)
• On the Event Statistics page, after changing the graph type (for example, from line to stepline), the checkboxes for showing or hiding trends and selections might stop functioning. The boxes remain unresponsive even if the graph type is changed back to the original setting. (Jira ID: EM-79888)

Global Manager

• The devices on the Devices page in Global Manager systems cannot be sorted by the IP Address column. (Jira ID: SLUI-21108)
• On Global Manager systems, the View Event Policy option in the Actions menu () on the Events page does not work as expected. (Jira ID: SLUI-21133)
• On Global Manager systems, the Events page does not display events from child stacks. To work around this issue, clear all system caches on both the child stacks and the Global Manager parent stack, then restart the NextUI service. (Jira ID: SLUI-21134)

GraphQL

• The "harProviderOnDemandProcessing" GraphQL (GQL) query incorrectly creates a service table in the "data_har" database when executed with invalid or non-existent service IDs. (Jira ID: SLUI-21135)
• Clicking the Run Now button for any Dynamic Application on the Collections tab of the Device Investigator displays the following GQL error message in the Skylar One server console: "Variable "$procId" of non-null type "ID!" must not be null." (Jira ID: SLUI-21070)

Logging

• System logs related to backup start, stop, and failure events are not being generated as intended. While a backup might complete successfully, you cannot use the system logs to validate backup timelines or troubleshoot issues. (Jira ID: EM-79904)
• A known issue might cause several log configuration files to conflict, which could cause you to see errors for the sl_vault and slsctl logs or potentially block log rotation in some cases, depending on the order in which the files are executed. To work around this issue, delete the config files ~sl_vault and ~slsctl. (Jira IDs: SLS-1105, EM-62134)
• The php-error.log does not track actions for non-administrator local users. (Jira ID: EM-77688)

Platform

• You might receive an "Internal Server Error" when attempting to configure an IP address on a heartbeat interface using the Web Configuration Tool. To work around this issue, configure heartbeat IP addresses using the command line interface. (Jira ID: EM-79886)

PowerPacks

• When installing or importing a PowerPack, you might not be able to adjust the PowerPack's embedded license or license key type. (Jira IDs: EM-71507, EM-72515, EM-72716)
• You might encounter an issue that prevents you from deleting a PowerPack through the user interface. (Jira ID: EM-76085)
• After updating the "ScienceLogic: Default Internal Events" PowerPack, the PowerPack Manager page might incorrectly display version 12.5.2 instead of version 100. (Jira ID: EM-79963)
• If you use the "IBM: DB2" PowerPack, component information might not be available when the "IBM DB2: Dynamic Application Alignment" run book policy and action is run and the name of the parent component is unavailable to the run book action. This results in the additional Database-level Dynamic Applications being aligned with the Default SNMP credential. For more information, see https://support.sciencelogic.com/s/article/20838.
• When creating a new PowerPack, attempting to save modifications without first refreshing the page might trigger an "Error: License key is not valid" message. To work around this issue, refresh the PowerPack Editor page. (Jira ID: EM-73201)

Reporting

• If you create a PDF report about a single device from the Devices or Classic Devices pages (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface), some tables might not display as intended. (Jira ID: EM-79587)
• The DEV_REPORT_CREATOR access hook currently only restricts the print icon on the classic Device Registry page. Users without this hook can still generate reports on the Device Properties page, on the Device Summary page, and in the default user interface (AP2). (Jira ID: EM-79956)
• If you attempt to load a performance report with images, it fails if the Percentile option is enabled on the graph. Reports without images are unaffected, but any report that includes visual graph data fails to load in this state. (Jira ID: EM-79893)
• The Notes section of generated User Report PDFs might display raw HTML tags instead of the intended rich text formatting. (Jira ID: EM-79867)
• On the Report Output Styles page (Reports > Management > Report Output Styles), the Style Name column has values with non-breaking spaces that are displayed as HTML code. This issue does not prevent you from creating or running reports. (Jira ID: EM-80296)

Schedule Management

• A large number of stored procedure calls over time can lead to memory growth in the scheduler process as well as delays in processing schedules. (Jira IDs: EM-76720, EM-75045)

Skylar AI

• The sl-otelcol-mgmt.py script shows blank values for the sl-otelcol, em7-platform-core, and nextui versions when connecting to Skylar AI, making it unclear which versions are actually installed, even though the status output reports the versions correctly. (Jira ID: EM-78655)
• Anomaly Detection and Predictive Alerting are not created for Dynamic Applications that are not associated with a PowerPack. (Jira ID: EM-73074)
• Supplying an Open Telemetry Collector endpoint URL with a trailing slash can cause the endpoint to be rejected or fail validation. As a workaround, remove any trailing slash from the URL before saving. (Jira ID: EM-77859)
• If the Skylar AI endpoint is unavailable, the Open Telemetry Collector might receive data from Skylar One but fail to send it to Skylar AI without notifying the sender. (Jira ID: EM-78343)

Subscription Billing

• The Bandwidth Billing interface filter might become unusable after the initial search, even if the filter is cleared. To work around this issue, click Reset. (Jira ID: EM-76511)

System Administration

• On the Appliance Manager page (System > Settings > Appliances), clicking the wrench icon for an appliance whose MariaDB credentials are stored as null causes the page to go blank instead of loading the appliance's settings. This typically occurs when the Database Server and Message Collector share the same MariaDB credentials. (Jira ID: EM-81082)
• When editing a collector group from the Collector Groups page (Manage > Collector Groups) by clicking its Actions menu (ellipsis icon) and unchecking two or more organizations in the Limit access to specific organizations field of the Edit Collector Group modal, the Organizations column on the Collector Groups page shows that only one organization was deselected, even if multiple were. (Jira ID: SLUI-22167)
• Message Collectors on the Collector Groups page (Manage > Collector Groups) cannot be sorted by the Message Collectors column. (Jira ID: SLUI-22099)
• Default account policies might automatically align with the organization that is alphabetically ranked lowest, potentially causing unexpected policy assignments. (Jira ID: SLS-2084)

User Interface

• For user accounts that are derived from user policies, fields on the Account Permissions page (Registry > Accounts > User Accounts > edit user account) that should display as disabled might appear to be editable in Skylar One 12.5.20 and later. (Jira ID: SLS-2324)
• The Access Keys page (System > Manage > Access Keys) might not count administrator-level users in the value displayed in the # Aligned Users column. To work around this issue, go to the Account Permissions page (Registry > Accounts > User Accounts > wrench icon) for the administrator-level users and re-save their permissions. (Jira ID: EM-74241)
• When you bulk-select multiple event policies to align with a run book automation policy, additional event policies that you did not select might become aligned with that automation policy as well. (Jira ID: EM-70690)
• Name changes to nodes on the Nodes page (Manage > Nodes) are not saved. (Jira ID: SLUI-22248)
• In the default user interface (AP2), when opening the Account Permissions page (Registry > Accounts > User Accounts > wrench icon) for an existing user account, the Theme/Brand drop-down field does not initially display on the page. To work around this issue, refresh the page. (Jira ID: EM-76478)
• On the OID Browser page (System > Tools > OID Browser), the Where Symbolic is like drop-down option for the Search where field might not work as intended. (Jira ID: EM-74326)
• In the classic user interface, the filter for Edit Date is not working as intended on the Inbound Email page (Registry > Events > Inbound Email). (Jira ID: EM-75291)
• When using a dark mode theme, if you click on a calendar icon to select a date, some dates might not be visible on the calendar. (Jira ID: EM-76629)
• The final row might not appear on the Select Objects page (System > Customize > Select Objects) when viewed in the default user interface (AP2) using a Firefox browser. (Jira ID: EM-74222)
• When using Active Directory Federation Services (ADFS) to authenticate, the system opens to the default landing page rather than the last page the user visited. (Jira IDs: SLS-1764, SLS-1765)
• If you create a new network on the IPv4 Networks page (Registry > Networks > IPv4 Networks), it might not appear on the page after you save it. However, the network should still be available for selection in other operations. (Jira ID: EM-76666)
• In AWS deployments, the % Used column on the IPv4 Networks page (Registry > Networks > IPv4 Networks) might erroneously display values over 100%. (Jira ID: EM-76672)
• When saving a change on the Quality of Service Threshold Defaults page (System > Settings > Thresholds > Quality of Service), the page might continuously state that it is saving until you refresh the page. Despite this messaging issue, the system should save the changes correctly. (Jira ID: EM-74336)
• If you select a normalized option for a service usage graph, the Date Range Selection pane changes to the year 1970 and the graph is not visible, even if you correct the start and end dates. (Jira ID: EM-74331)
• When creating an uptime OID, the system might display an error alert if the OID is invalid but still save the OID anyway. (Jira ID: EM-74227)
• On the Process Manager page (System > Settings > Admin Processes), if you deselect the appliance type(s) that a process should run on and then save that change, it prevents that process from starting in the future. (Jira ID: EM-74236)
• If you click the Save button on the User Policy Properties Editor page (Registry > Accounts > User Policies > create or edit) for an existing user policy, the system mistakenly saves the user policy again as a separate entry rather than overwriting the existing policy with the updated information. (Jira ID: SLS-1773)
• The Sharing Permissions drop-down field on the Appliance Settings page incorrectly displays Private by default, even though the system treats the setting as Shared. (Jira ID: SLS-1870)
• Going to some pages or performing certain actions in the classic user interface might trigger "PHP Deprecated" notices in the error logs. These notices do not impact page functionality and can be safely ignored. (Jira IDs: EM-79898, EM-75356, EM-75310)
• The Save As button for Database type credentials might be invisible or partially obscured when using the Firefox browser. This issue specifically affects systems that have upgraded through multiple versions and is not present in other browsers. (Jira ID: EM-79885)
• After performing an initial search in the Bandwidth Billing Policy Editor, the Filter button can become inactive, preventing users from changing the filter text. To work around this issue, click the Reset button. (Jira ID: EM-79847)
• Sorting by the Organization column on the SSL Certificate Monitoring page might produce inaccurate results due to the system sorting by the organization ID rather than the organization name. (Jira ID: EM-79843)
• In classic Service Provider Utilities, Service Usage policies might fail to save selections if you choose more than one device. (Jira ID: EM-79809)
• On the User Policy Membership page (Registry > Accounts > User Policies) in the classic user interface, sorting by the First Name, Phone, or Mobile columns might cause all rows to disappear, preventing administrators from managing policy members while the sort is active. (Jira ID: EM-74702)

Known Issues Resolved in Available Releases

• The following known issues impacting this release are fixed if you upgrade to the AP2 version 9.13.1-14 (Quesito) release or later after upgrading to 12.5.23:

  • In systems with Skylar AI enabled, the sorting feature for columns on the Anomaly Detection page only sorts by the data currently displaying on the page, which might not include all anomaly detection data. (Jira ID: SLUI-22523)

  • Filtering the Collector Groups column on the Device Investigator page with multiple group names can cause the page to not load correctly. (Jira ID: SLUI-21035)

  • The column widths on the Device Investigator page do not adjust when resized. (Jira ID: SLUI-20081)