PPM logs stop updating sometime after restart, what could be the reason for this?

book

Article ID: 104091

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM SaaS - Application Clarity PPM On Premise

Issue/Introduction



PPM logs stop updating sometime after restart, what could be the reason for this?

Environment

Release: CODFSS99000-15.4.1-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:

Resolution

There are two possible reasons for an application log such as app-ca.log or bg-ca.log to stop updating:

1.    Issue with logger.xml

To fix this, replace the logger with a template file:


Steps:
a. Backup the file $PPM_HOME/config/logger.xml
b. Replace $PPM_HOME/config/logger.xml with $PPM_HOME/.setup/templates/config/logger.xml
c. Restart the service
d. Repeat on all servers in cluster


2.    If the above only fixes the issue temporarily, and after a while the logs stop updating, we recommend looking into the custom jobs running on your environment. We have had issues in which custom java jobs use CA PPM log4j.jar and this can lead to issues with logging

To prove this is the case:
a.    Stop the suspect job from running and restart the services
b.    Ensure the log is updating
c.    Wait for some time and see if the log stops updating

Our recommendations to avoid this are:

1. Try using the standard Java IO stream, or entries to the database as logging instead of the existing log4j.jar.
2. Alternatively, disable the logging on your custom job for now until you are able to rework it to avoid the log corruption. This should allow you to still use the job while keeping the environment stable.