Description of problem: Right now we configure ODL logging to use 10 karaf files which rotate after one is full. The size is also too small in comparison to the amount of logging ODL produces. We should modify the configuration to use a single file and have a very large file limit. Ideally we want ODL logging to be part of systemd journaling.
We should configure the logging to use a single large file. [1] is the link to the shell script in the upstream job for configuring a single large file. The script sets the size to 30GB but in normal practice it is less than 50MB. The final config would look like: modify file: org.ops4j.pax.logging.cfg log4j.appender.out.maxBackupIndex=1 log4j.appender.out.maxFileSize=30GB [1] https://github.com/opendaylight/releng-builder/blob/master/jjb/integration/include-raw-integration-configure-clustering.sh#L80
Upstream pacthes cherry-picked for Carbon: https://git.opendaylight.org/gerrit/#/c/60759/
> Ideally we want ODL logging to be part of systemd journaling ==> Bug 1475951 ...
Cherry-pick to stable carbon https://git.opendaylight.org/gerrit/#/c/60816/
With this change, there would be 2 files generated of size 10 GB each.
Verified with opendaylight-6.1.0-2.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462