Troubleshooting
Problem
FP28 has been re-published on the 11 Jan 2023 to include a fix for APAR IJ44645: FP28 FAILS ON SYSTEM WITH LDAP AUTHENTICATION.
Previous downloads of FP28 (from before 11 Jan 2023) should be discarded.
However, if previous downloads of FP28 were installed on non-LDAP authenticated systems, then there is no action take. The original FP28 only caused an issue on LDAP authenticated systems.
Symptom
The following WARNING message is seen at the start of the upgrade process: IMPACTIN0279W Cannot ping the LDAP server at host:port. Make sure the LDAP server is running before proceeding with the upgrade. The upgrade process may fail when Impact server(s) cannot authinticate with the LDAP server.
The warning message "IMPACTIN0279W Cannot ping the LDAP server at", does not prevent the upgrade from taking place.
After upgrading to FP28, the impact backend server will start, but doesn't function. The impactserver.log file says it cannot connect to nameserver.
Diagnosing The Problem
The impactserver.log shows this message:
ERROR [ClusterMember] Unable to login to configured name servers [host [hostname], port [9080], location [/nameserver/services], SSL enabled [false], host [hostname], port [9080], location [/nameserver/services], SSL enabled [false]]; will reattempt after 10000 milliseconds.com.micromuse.response.common.RespException: Unable to login to any of the Nameservers in the cluster!
com.micromuse.response.common.RespException: Unable to login to any of the Nameservers in the cluster!
com.micromuse.response.common.RespException: Unable to login to any of the Nameservers in the cluster!
The web.xml file for the nameserver.war shows corrupted values
<context-param>
<param-name>REPLICANT.0.HOST</param-name>
<param-value>__NAMESERVER_HOST__</param-value>
</context-param>
<param-name>REPLICANT.0.HOST</param-name>
<param-value>__NAMESERVER_HOST__</param-value>
</context-param>
<context-param>
<param-name>REPLICANT.0.PORT</param-name>
<param-value>__NAMESERVER_PORT__</param-value>
</context-param>
<param-name>REPLICANT.0.PORT</param-name>
<param-value>__NAMESERVER_PORT__</param-value>
</context-param>
<context-param>
<param-name>REPLICANT.0.LOCATION</param-name>
<param-value>/nameserver/services</param-value>
</context-param>
<param-name>REPLICANT.0.LOCATION</param-name>
<param-value>/nameserver/services</param-value>
</context-param>
Resolving The Problem
If FP28 has not yet been installed, download the updated Netcool/Impact FP28, which was refreshed on the 11 Jan 2023, and upgrade using this new download.
If previous (before 11 Jan 2023) downloads of FP28 were installed on non-LDAP authenticated systems, then there is no action take. The original FP28 only caused an issue on LDAP authenticated systems.
If the original FP28 has already been installed on systems with LDAP authentication, then these systems need to be "fixed" so they can be rolled back in order that the updated FP28 can be cleanly installed. The steps are below. However, if in doubt, open a Salesforce case to contact IBM Support for assistance.
The repair_impact_for_FP28_rollback.sh script needs to be updated by the end-user (as shown in steps 1 - 3). In addition to this, there are two interactive actions to be taken (per steps 5 and 6).
NOTE: The Impact fix pack *VERSION and server name, as well as, cluster name can be found here: $IMPACT_HOME/install/buildimpact.properties
Action to edit and run the repair_impact_for_FP28_rollback.sh script:repair_impact_for_FP28_rollback.sh
- Copy the script to the tmp directory where the script needs to be run from
- Issue the chmod command to make the script executable: chmod +x /tmp/repair_impact_for_FP28_rollback.sh
- Edit the script "/tmp/repair_impact_for_FP28_rollback.sh" and update the following four lines:
- export PREVIOUS_VERSION=7.1.0.nn
- export IMPACT_HOME=/opt/IBM/tivoli/impact
- export BACKUP_DIR=/opt/IBM/tivoli/impact/backup
- export SERVERNAME=NCI
- Execute/run the "/tmp/repair_impact_for_FP28_rollback.sh" script
- The script will inform you that the file "$IMPACT_HOME/wlp/usr/servers/NCI/apps/NCI.ear/META-INF/application.xml" needs to be edited and will automatically place you in edit mode once one replies "y/Y" to continue (at the first prompt)
- The script will also inform you that the file "/opt/IBM/tivoli/impact/install/buildimpact.properties" needs to be updated and will place you in edit mode after one replies "y/Y" at the second prompt.
- Once the script completes, start the Impact server and then perform the Impact 7.1.0.28 rollback process.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSB2GF","label":"Netcool\/Impact - SSB2GF"},"ARM Category":[{"code":"a8m500000008ZvjAAE","label":"Impact-\u003EInstallation-\u003EUpgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.0"}]
Was this topic helpful?
Document Information
Modified date:
11 January 2023
UID
ibm16852605