Edit

Also delete all /var/log/cdmserver/out.log files once this is released

i found a second issue:

The rolling daily file appender only works if the custom loj4j.properties are defined in the /etc/default/cdmserver

#
# user custom loj4j.properties
#
JAVA_OPTIONS="$JAVA_OPTIONS -Dlog4j.configuration=file:///opt/cdmserver/.cdmLibrary/log4j.properties"

The rolling daily file appender should be used in default configuration.

third issue:

unfortunately you committed all changes to the master branch:

* 469b75d - Fri, 12 Oct 2018 11:26:09 +0200 (7 days ago) (origin/master, origin/HEAD)
|   ref #7085 Adjust log path - Patrick Plitzner
* 0465659 - Fri, 12 Oct 2018 10:47:59 +0200 (7 days ago)
|   ref #7085 Set logging to daily rollover - Patrick Plitzner
* 72c3d33 - Fri, 12 Oct 2018 09:18:02 +0200 (7 days ago)
|   ref #7085 Adjust log path - Patrick Plitzner
* b78e167 - Thu, 11 Oct 2018 17:13:40 +0200 (8 days ago)
|   Revert "ref #7085 Use DailyRollingFileAppender (in code)" - Patrick Plitzner
* 02ef1e4 - Thu, 11 Oct 2018 16:57:36 +0200 (8 days ago)
|   ref #7085 Use DailyRollingFileAppender (in code) - Patrick Plitzner
* 99c113d - Thu, 11 Oct 2018 16:43:44 +0200 (8 days ago)
|   ref #7085 Use DailyRollingFileAppender to generate one log per day - Patrick Plitzner
*   c172618 - Mon, 17 Sep 2018 11:28:56 +0200 (5 weeks ago) (tag: 5.3.0)
|\    jenkins merging release branch into master (strategy: theirs) - jenkins
| * 9efc161 - Mon, 17 Sep 2018 11:28:15 +0200 (5 weeks ago)
| |   updating poms for branch'release/5.3.0' with non-snapshot versions - jenkins
* |   83415cd - Fri, 17 Aug 2018 16:08:00 +0200 (9 weeks ago) (tag: 5.2.0)

This will break the next release since git-flow can not deal with intermediate commits to the master branch, we will run into merge conflicts. Your changes being committed to the master branch could also be the reason why the daily rolling fileappender is not working in those servers which are not configured to use the custom log4j.properties

Please fix the git repo. The clone at git hub must also be fixed. You must whipe out your changes completely from master. A git revert might not be enough in this case.

BTW: Did you replace the old log4j.properties on the edit-test server or did exchange the old appender by the daily rolling fileappender?

we can use the Log4J config provided as

-Dlog4j.configuration=file:///opt/cdmserver/.cdmLibrary/log4j.properties

in the /etc/default/cdmserver as preliminary solution. But this is not reliable since it does not work out of the box when the cdm-server is installed newly.

Interestingly with -Dlog4j.configuration the log4j.properties is used in the bootloader and in the instances. In contrast to that consistent configuration seems to be hard to achieve out of the Bootloader, see cdm-server|bb431d84

for the coming release I will add the following configuration to edit-int, edit-test and edit-production:

##
## NOTICE !!!!
## no need to configure a FileAppender here
## use eu.etaxonomy.cdm.remote.config.LoggingConfigurer instead
##
#--------------------------------------------------------------------------------------------------
# as interim solution in order to have a daily rolling file appender we configer it here
# see https://dev.e-taxonomy.eu/redmine/issues/7085
log4j.appender.FILE=org.apache.log4j.DailyRollingFileAppender
log4j.appender.FILE.File= ${LOGGING_FOLDER}/cdmserver.log
log4j.appender.FILE.ImmediateFlush=true
log4j.appender.FILE.Threshold=debug
log4j.appender.FILE.Append=true
log4j.appender.FILE.DatePattern='.'yyyy-MM-dd
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.ConversionPattern=%d %p [%c] - %m%n
#--------------------------------------------------------------------------------------------------

This needs to be removed once the DailyRollingFileAppender is being applied out of the cdm-server.