Question
Accenture
US
Last activity: 19 Jul 2018 10:17 EDT
PEGA log rotation not occuring on PEGA
Support,
We are having issues with logs rotation on PEGA 7.3.1 Portal. Every morning we have to reboot PEGA to be able to see the updated logs on PEGA portal. The logs are being updated at the server level but unable to see the updated logs from that date on PORTAL, it only shows logs from yesterday.
Designer Studio > System > Operation > Logs: "Log Files" -- it only shows logs from a day before, unless we reboot or do ResetALL from SMA.
Prlog4j2.xml has the following format:
<RollingRandomAccessFile name="PEGA" fileName="${sys:middleware.server.log.dir}/${sys:middleware.host.name}.PegaRULES-${date:yyyy-MM-dd}.log" filePattern="${sys:middleware.server.log.dir}/${sys:middleware.host.name}.PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">
***Edited by Moderator Marissa to update platform capability tags***
Pegasystems Inc.
GB
Are the actual files on the server rolling over but you unable to see the new day log files via Designer Studio > System > Operation > Logs?
Accenture
US
Prlog4j2.xml has the following formats for server logs:
<RollingRandomAccessFile name="PEGA" fileName="${sys:middleware.server.log.dir}/${sys:middleware.host.name}.PegaRULES-${date:yyyy-MM-dd}.log" filePattern="${sys:middleware.server.log.dir}/${sys:middleware.host.name}.PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">
<PatternLayout>
<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>
</PatternLayout>
<Filters
Prlog4j2.xml has the following formats for server logs:
<RollingRandomAccessFile name="PEGA" fileName="${sys:middleware.server.log.dir}/${sys:middleware.host.name}.PegaRULES-${date:yyyy-MM-dd}.log" filePattern="${sys:middleware.server.log.dir}/${sys:middleware.host.name}.PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">
<PatternLayout>
<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>
</PatternLayout>
<Filters>
<!--Deny message logged under ALERT log level-->
<ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="NEUTRAL"/>
</Filters>
<Policies>
<TimeBasedTriggeringPolicy interval="12"/>
<SizeBasedTriggeringPolicy size="250 MB"/>
</Policies>
<DefaultRolloverStrategy max="20"/>
</RollingRandomAccessFile>
We also have Application logs in this format. we added ""-a"" (ignore quotes) for AM/PM.
<RollingRandomAccessFile name="App_log" fileName="${sys:pega.nfs.log.location}/${sys:middleware.host.name}.App-Log-${date:yyyy-MM-dd-a}.log" filePattern="${sys:pega.nfs.log.location}/${sys:middleware.host.name}.App-Log-%d{MM-dd-yyyy}-%i.log.gz">
<PatternLayout>
<Pattern>%d [%t] %-5p %c- %m%n</Pattern>
</PatternLayout>
<Filters>
<!--Deny message logged under ALERT log level-->
<ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="NEUTRAL"/>
</Filters>
<Policies>
<TimeBasedTriggeringPolicy interval="12"/>
<SizeBasedTriggeringPolicy size="250 MB"/>
</Policies>
<DefaultRolloverStrategy max="20"/>
</RollingRandomAccessFile>
So couple things:
1. We are seeing the current day application log file being generated on the server and we are not able to see the logs file from that day on PEGA portal. We are seeing the Application logs from yesterday.
To resolve this issue we have to reboot PEGA. Then we are able to see all the updated logs from that day. And even if they are not on servers (for some) they will be updated as well on both end.
Questions:
1. What files are being used by prlog4j2.xml that we should be updating if we make any change to **filename appender ** with PEGA 7.3.1?
2. Could this be related to SizeBasedTriggeringPolicy or TimeBasedTriggeringPolicy?