Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Log path changes in prlogging.xml file not working

SA-25573

Summary



User has changed the log path in the prlogging file for Pega logs, alert security. But logs are still to written to the old path location.
 

Error Messages



Not applicable


Steps to Reproduce



1.Access the prlogging file on server through command prompt.
2. Update the log path below for Value field:
<appender name="PEGA" class="com.pega.pegarules.priv.util.DailySizeRollingFileAppenderPega">
<param name="FileNamePattern" value="'@{web.tmpdir}/PegaRULES-'yyyy-MMM-dd'.log'"/>
3. Restart the server.


Root Cause



User wanted a log file for each JVM and for it to be placed in its own specific directory, they did not know how to achieve this.

Resolution



Apply the following local-change to resolve the issue:

1. For each JVM create a system property which reflects the instance for example, JVM_NAME then add a JVM argument similar to this

    -Dpega.log.path=/AppVol/$JVM_NAME 

2. Then in the prlogging.xml for the path have: 

    <param name=”FileNamePattern” value=”’${pega.log.path}/PEGARULES-‘yyyy-mm-dd’”>

 

Published August 23, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us