7.3.0 Patch 5 - August 2024

Issue: Uploading a new lookup file with the On LoggerFile 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.

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

Issue: In a few documented cases, after a LoggerL8000 Appliance has functioned for a certain period of time, under normal EPS loads, a higher CPU usage and performance deterioration has been noticed.

Workaround: Open Text recommends applying this workaround to all Logger L8000 Appliances (even if not currently experiencing this issue) to optimize their performance:

1. Execute the following commands:

   cd /opt/softlogger/userdata/logger/user/logger
   cp -p logger.properties logger.properties.<date>

2. Make the following changes to the logger.properties file:

   Current property value	Optimized value:
   ros.chunk.deflater.thread.count=5	ros.chunk.deflater.thread.count=1
   ros.post.processor.thread.count=5	ros.post.processor.thread.count=1
   ros.post.processor.queue.size=25	ros.post.processor.queue.size=5
   ros.column.chunk.queue.size=200	ros.column.chunk.queue.size=100
   ros.event.processor.thread.count=40	ros.event.processor.thread.count=20
   ros.chunk.writer.thread.count=10	ros.chunk.writer.thread.count=5
   ros.event.queue.size=60	ros.event.queue.size=30
   	receiver.serialize.timeout=365

3. Save the changes, and restart Logger.

Issue: In a Logger L7700 appliance running on RHEL 8.8 (therefore applicable to versions: 7.3.0 Patch3, Patch 4 and Patch 5), even though the configuration backup files are generated correctly, the restore procedure is not able to decompress them due to a missing RHEL 8.8 required parameter. Therefore, after executing the system requested reboot, the data will not be restored.

Workaround:

1. Reach out to ArcSight support to obtain the replacement backupcheck file and checksum.

2. Save the new file in the /tmp directory.

3. Navigate to the /opt/arcsight/aps/bin directory and backup the current backupcheck file with the following commands:

   cd /opt/arcsight/aps/bin
   cp -p backupcheck backupcheck.original

4. Replace the current file with the new one saved in the /tmp directory with this command:

   cp /tmp/backupcheck ./backupcheck

5. Validate permissions and ownership of the replacement file with this command:

   ls -lht backupcheck

   Expected output example:

   -rwx------. 1 root arcsight 37K Jan 22 2024 backupcheck

6. You can proceed working without a system restart.

7.3.0 Patch 5 (8475)

L7700

L8000

Certified on:

RHEL Linux 8.8

Rocky Linux 8.8

Supported on:

RHEL Linux 8.6

Rocky Linux 8.6

Microsoft Edge *

Firefox *

Chrome *

7.3.0 Patch 3 (8455)

7.3.0 Patch 4 (8469)