When RollingFileAppender moves file to another folder, it tries to use ATOMIC_MOVE option as most strong one approach.
In many common production cases this approach always fails, and RollingFileAppender fallbacks (which is good) to use File.renameTo method. One of such common case - using network filesystem for cold logs (E.g. CIFS).
When atomic move fails it prints error to the log. Something like this:
Such logs are very distracting and can lead to unnecessary monitoring alerts.
I suggest to lower logging level for such case to INFO or WARN. As it's expected scenario.