Auto-delete log have unusual level logged

[SK-Yang]

I'm using log4j-core 2.25.3 and log4j-1.2-api 2.25.3 with maven right now. It works good but there is one thing: it appear will log wrong level of log into console-log(server log in my case). So I get warnings at midnight from Prometheus stating that my server got some errors.

After reviewed those logs, I notice that there are nothing unusual and they are just mentioning that the daily auto-delete routine is starting up. I'm not sure if this is a bug or feature that those word could be opted to correct form, so I post this under question category.

2026-03-06 14:53:25,826 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.826140807Z default task-1 TRACE PatternProcessor.getNextTime returning 2026/03/07-00:00:00.000, nextFileTime=2026/03/06-00:00:00.000, prevFileTime=2026/03/05-00:00:00.000, current=2026/03/06-14:53:25.825, freq=DAILY
2026-03-06 14:53:25,827 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.827011548Z default task-1 DEBUG Formatting file name. useCurrentTime=false. currentFileTime=1772780005826, prevFileTime=1772640000000
2026-03-06 14:53:25,828 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.828035139Z default task-1 DEBUG Current file: /home/APData/Log/WSI.log
2026-03-06 14:53:25,828 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.828657668Z default task-1 DEBUG Eligible files: {}
2026-03-06 14:53:25,828 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.828845294Z default task-1 DEBUG Formatting file name. useCurrentTime=false. currentFileTime=1772780005826, prevFileTime=1772640000000
2026-03-06 14:53:25,829 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.829070219Z default task-1 TRACE DefaultRolloverStrategy.purge() took 2.0 milliseconds
2026-03-06 14:53:25,830 ERROR [stderr] (default task-1) 2026-03-06T06:53:25.830521548Z default task-1 DEBUG OutputStream closed
...

[vy]

Those DEBUG/TRACE lines are emitted by Status Logger to stderr. It by defaults emits log events at severity >=WARN. I guess you've configured it to a lower severity, and hence seeing them. See the Status Logger manual for details on how to configure it.