Log Analysis 1.3.8 fix pack 1

Fix pack overview

Downloading the fix pack

For more information, see 1.3.8-TIV-IOALA-FP1-signed.

Included fixes

A collect_logs error is resolved.

The following error in IBM Operations Analytics Log Analysis 1.3.8 is resolved with 1.3.8 fix pack 1.

./collect_logs: line 63: /opt/IBM/LogAnalysis/apache-ant-1.10.9/bin/ant: No such file or directory

A ManageSolrNodes error and warning are resolved.

The following error and warning appear in the log file even though installation was supposed to work without a password.

2024-01-11 16:16:28,409 WARN [ManageSolrNodes] Password-less SSH has either not been configured or is not working
2024-01-11 16:17:09,040 ERROR [ManageSolrNodes] Could not connect to <server> as no valid password was provided

If you use the following methods to enable Secure Shell (SSH) without a password, the ManageSolrNodes error and warning appear.

• The error and warning can appear after you set up SSH to use key-based authentication. For more information, see Setting up Secure Shell to use key-based authentication.
• The error and warning can appear after you enable SSH without a password during a remote Apache Solr installation. For more information, see ssh_config.properties.

The error and warning are resolved with 1.3.8 fix pack 1.

An encrypted password warning is resolved.

To avoid entering an SSH password for remote Apache Solr access during a unity.sh operation, you can set up file-based password entry for remote Apache Solr. When the password was in encrypted form, the following warning appeared during the unity.sh operation. This warning is resolved with 1.3.8 fix pack 1.

Getting status of Solr on <server>
Could not connect using the given password, try again(Y/N)? [Y]:

For more information about file-based password entry, see File based password entry for remote solr ssh.

Known issues

An error appears after Logstash plug-ins are installed.

For Logstash on a Windows configuration, you need to manually install the logstash-input-eventlog and logstash-filter-date_formatter plug-ins. For more information about the plug-ins, see Logstash configuration file reference.

In IBM Operations Analytics Log Analysis 1.3.8 fix pack 1, Logstash version 8.11.3 replaces Logstash version 8.7.1. The following error appears when you install the logstash-input-eventlog and logstash-filter-date_formatter plug-ins.

"Using bundled JDK: C:\myWork\Logstash\logstash-8.11.3\jdk\bin\java.exe"
Gem::LoadError: You have already activated ffi 1.16.3, but your Gemfile requires ffi 1.15.5. Since ffi is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports ffi as a default gem.

To avoid this error, use Logstash version 8.7.1. For more information about downloading and setting up Windows Logstash version 8.7.1, see Installing Logstash on Windows based servers.

Logstash installation is unsuccessful after an uninstallation.

After a remote installation and uninstallation of Logstash, subsequent installations of Logstashon the same directory fail.

To avoid installation failure, use a different remote directory name. This issue appears on IBM Operations Analytics Log Analysis 1.3.8 fix pack 1 only.

Vulnerability fixes

For more information, see 1.3.8.1 in the Log Analysis Security Bulletin List.