Hello, We have 5 async logs in our log4j2 configuration that rotates every day at 00:01. This is the config for one of them:
<RollingRandomAccessFile name="ACCESS_LOG" fileName="${sys:log.dir}vproxy_access" filePattern="${sys:log.dir}vproxy_access.%d{yyyy-MM-dd}" append="true" immediateFlush="false"> <PatternLayout><Pattern>%m%d{HH:mm:ss.SSS}%n</Pattern></PatternLayout> <Policies><CronTriggeringPolicy schedule="1 0 0 * * ?" evaluateOnStartup="true" /></Policies> </RollingRandomAccessFile> <Logger name="LOGGER_ACCESS" level="info" includeLocation="false" additivity="false"> <AppenderRef ref="ACCESS_LOG"/> </Logger> So at 5 Feb 00:01 we expected to have 5 logs with the '2020-02-04' extension, but we see files with '2020-02-05' extension. This sometimes happens to some files, sometimes to other files ... it's not always happening to the same files. Some days rotation is ok, some days rotation fails just in 1 file, sometimes in 2 files, ... -rw-r-----. 1 root root 1649483171 Feb 5 16:22 vproxy_access -rw-r-----. 1 root root 225670559 Feb 5 00:00 vproxy_access.2020-02-04 -rw-r-----. 1 root root 42650335 Feb 5 16:29 vproxy_cluster -rw-r-----. 1 root root 8052 Feb 4 17:58 vproxy_cluster.2020-02-04 -rw-r-----. 1 root root 1222846577 Feb 5 17:26 vproxy_datametrycs -rw-r-----. 1 root root 167707641 Feb 5 00:00 vproxy_datametrycs.2020-02-05 -rw-r-----. 1 root root 1448754527 Feb 5 16:22 vproxy_error -rw-r-----. 1 root root 199048217 Feb 5 00:00 vproxy_error.2020-02-04 -rw-r-----. 1 root root 3683378 Feb 5 17:41 vproxy_system -rw-r-----. 1 root root 2238045 Feb 4 23:59 vproxy_system.2020-02-05 Is this a bug or some misconfiguration in our log4j.xml file? Thanks for any help you can provide, Joan. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org