ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The install.log will not capture installation specific data following a Clarity 16.0.2 installation or an upgrade to Clarity 16.0.2

book

Article ID: 241353

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

The install.log will not capture installation specific data following a Clarity 16.0.2 installation or an upgrade to Clarity 16.0.2

Steps to Reproduce: 

  1. Start a fresh installation or upgrade to to 16.0.2 as per documentation 
  2. Review the install.log 

Expected Results: Install.log should have the installation specific date related to install or upgrade 

Actual Results: Install.log only has single line is written to the install.log all other output is only sent to stdout.

5/09/22 1:30 PM (ant) No log4j.properties in build area

Cause

This is a defect DE65030

Environment

Release : 16.0.2

Component : Clarity Install and Upgrade

Resolution

This issue will be resolved in the Clarity 16.0.3 release (targeting Aug-2022). 

Workaround: 

  1. Extract the install.jar to a temporary directory, for example: \temp\Extract
  2. Navigate to the extracted directory, and then browse to lib folder for example: \temp\Extract\tools\lib
  3. Remove the below files
    • log4j-1.2-api.jar
    • log4j-api.jar
    • log4j-core.jar
  4. Download the file attached to this knowledge document, log4j_1652279930171.jar , rename the file to log4j.jar and place under the extracted directory \temp\Extract\tools\lib
  5. Start the upgrade or install 

 

 

Additional Information

Note:

  • With upgrade to Clarity 16.0.2 its using Log4j version 2.17.2
  • If an install was successfully completed prior to completing these steps, no further action is required in order for Clarity to function. These steps are only required in order for the install.log to successfully update during the install or upgrade  process. This would be required if the install were failing, and the logs are needed to troubleshoot the issue, or if the install logs needed to be retained for some other specific purposes.

Attachments

log4j_1652279930171.jar get_app