7.3.0 Patch 8 - May 2025

The 7.3.0 Patch 8 release includes fixes and enhancements provided in previous releases.

Fixed Issues

The following issues are fixed in this release.

Issue

Description
OCTCR33I889130 Issue: When a search is run, the Field Summary component doesn't automatically load the fields from the selected default custom fieldset.
OCTCR33I974084 Issue: Exporting the results of a search that included the rex operator generates output files with empty columns or columns with gibberish names.
OCTCR33I977127 Issue: Queries containing a combination of the where and eval operators are not returning the properly filtered results.
OCTCR33I979229 Issue: On Software and L7700 Appliance Loggers running on RHEL or Rocky Linux versions 8.x and 9.x, the system fails to create its configuration backup file. There is no notification of the issue, which only shows in the logger_server.log file.
OCTCR33I992096

Issue: In environments with very low network latency, when a search returns only one to three events, the search results might not be displayed at times.
OCTCR33I994111 Issue: Logger's default date format has been updated from 'YYYY' (week year format) to 'yyyy' (calendar year format) to allow for searches that include a new year that starts in the middle of the week.

Known Issues

The following known issues apply to this release. Micro Focus strives to ensure that our products provide quality solutions for your enterprise software needs. If you need assistance with any issue, visit Micro Focus Support, then select the appropriate product category.

Issue

Description
OCTCR77JK4815909
Issue: Logger Reset Password link not working after upgrade to v7.3.0P8
Workaround: 
  • Change the file path, depending on whether the environment is Logger software or an Appliance.
  • Reach out to Support for patching assistance of Logger.
          Follow the below commands to apply the workaround: 
•	cp -p <install_dir>/current/arcsight/aps/webapps/core-service/WEB-INF/lib/jakarta.mail-1.6.7.jar <install_dir>/current/arcsight/aps/webapps/platform-service/WEB-INF/lib/
•	cp -p <install_dir>/current/arcsight/aps/webapps/core-service/WEB-INF/lib/jakarta.mail-1.6.7.jar <install_dir>/current/arcsight/aps/webapps/storage-service/WEB-INF/lib/
•	cp -p <install_dir>/current/arcsight/logger/lib/commons-httpclient-3.1.jar <install_dir>/current/arcsight/aps/webapps/platform-service/WEB-INF/lib
•	cp -p <install_dir>/current/arcsight/logger/lib/commons-httpclient-3.1.jar <install_dir>/current/arcsight/aps/webapps/storage-service/WEB-INF/lib/
•	cp -p <install_dir>/current/arcsight/logger/lib/commons-httpclient-3.1.jar <install_dir>/current/arcsight/aps/webapps/core-service/WEB-INF/lib
OCTCR33I867120

Issue: Uploading a new lookup file with the On Logger File Location option results in a "Please specify a path and a file" error when the name of the file is too long.

Workaround:

  1. Place the new lookup file in your local machine.

  2. Follow the Uploading Lookup Files procedure using Local as File location option.
OCTCR33I896042

Issue: After a Logger appliance has been upgraded to RHEL 8.8, the root password cannot be changed.

Workaround:

  1. Open the system-auth file with this command:

    vi /etc/pam.d/system-auth

  2. Update the /lib/security/$ISA/pam_unix.so path to:

    /lib64/security/pam_unix.so
OCTCR33I872028

Issue: The permissions of two files (CommuterLicFile.xml and autopass.properties) located inside Logger's autopass/data directory get resetted to 772, even when set back to 770.

Supported Platforms

 Version
 Release Date Appliance Models Standard Installations of the Following Operating Systems Supported Browsers Upgrade Path

7.3.0 Patch 8 (8511)

 May 2025

L7700

L8000

Certified on:

  • RHEL Linux 8.10

  • Rocky Linux 8.10

  • RHEL 9.4

  • Rocky Linux 9.4

Supported on:

  • RHEL 9.2

  • Rocky Linux 9.2

Microsoft Edge *

Firefox *

Chrome *

7.3.0 Patch 5 (8475)

7.3.0 Patch 6 (8481)

7.3.0 Patch 7 (8493)

An asterisk (*) next to a browser version indicates that the browser version supported is the one current at the date of release.

Customers running on platforms not provided in the Technical Requirements or with untested configurations will be supported until the point Micro Focus determines the root cause is the untested platform or configuration. According to the standard defect-handling policies, Micro Focus will prioritize and fix issues we can reproduce on the tested platforms.