Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.13.3
-
None
Description
Current Situation
- With
JS-1869we updated JobScheduler release 1.13.3 to use the log4j2 framework due to some vulnerabilities in the predecessor log4j framework. - During this move the log configuration for the handling of output to the scheduler.out log file was not considered.
- As a result output similar to what is written to the scheduler.log file is added to scheduler.out. This creates a problem for some users as the scheduler.out log file is growing and can consume some GB disk space. By design the scheduler.out log file is not considered for log rotation. The file is overwritten on restart of the JobScheduler Master only.
Desired Behavior
- The scheduler.out file should include log output of warnings and errors only that occur e.g. during start up and that cannot be redirected to other log files
Workaround
- Replace the missing log configuration in the file ./lib/log4j2.xml file like this:
- Insert this configuration towards the end of the file:
<Logger name="JobScheduler" level="fatal"/>
- Insert this configuration towards the end of the file:
-
- The end of your log42j2.xml file should look like this:
… <Logger name="JadeReportLog" additivity="false" level="off"> <AppenderRef ref="JadeReportLogAppender" /> <AppenderRef ref="JadeReportLogHTMLAppender" /> </Logger> <Logger name="JobScheduler" level="fatal"/> </Loggers> </Configuration>
- The end of your log42j2.xml file should look like this:
- Then restart the Master.