Resolved issues for Standalone Sentry

For resolved issues fixed in previous releases, see the "Resolved issues" section in the release notes for those releases.

General resolved issues for Standalone Sentry 9.13.0

The following issues are resolved in this release:

  • AL-12694: Previously, Sentry miaudit log files were not purged/rotated correctly and system log file was flooded with 'mi-logrotate: ALERT exited abnormally with [1]'.
    This issue is now fixed.

  • AL-14616: Previously, after 2 GB of device cache entries, new entries were not being reported.
    This issue is now fixed.
    A cleanup occurs every 10 minutes, which removes the oldest entry and the new entry is appended to all devices.

  • AL-15200: Previously, for IpTunnel, Sentry had a maximum HTTP header size of 8192 and the value was not configurable.
    This issue is now fixed.

  • AL-15311: Previously, rebooting a physical appliance would sometimes result in network interface card (NIC) swapping, which caused problems with interface configuration.
    This issue is now fixed.

  • AL-15321: Previously, when a virtual machine was configured with 2 hard disks of same size, the upgrade from Sentry 9.9.0 to Sentry 9.12.0 failed.
    This issue is now fixed

  • AL-15411: Previously, show system top CLI command failed with 'permission denied' error message.
    This issue is now fixed.

  • AL-15416: Previously, the iptables enable/disable status was not displayed correctly with show service command.
    This issue is now fixed.

Standalone Sentry resolved issues for Access

There are no new resolved issues found in this release.

Standalone Sentry resolved issues for Core

There are no new resolved issues found in this release.

Standalone Sentry resolved issues for Cloud

There are no new resolved issues found in this release.