Issue Bug Resolved

#109834Problem on https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.0/Feature-100926-IntroduceRotatingFileWriterforLogRotation.html

Oliver Thiele 05/14/26, 09:38 updated 09/19/26, 12:15

Description

I noticed a potentially dangerous side effect in the TYPO3 documentation example for the RotatingFileWriter configuration:

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.0/Feature-100926-IntroduceRotatingFileWriterforLogRotation.html
(The link is the same for TYPO3 v14)

The examples currently include:

DatabaseWriter::class => [], // this is part of the default configuration

This can easily be misunderstood as a harmless or recommended addition when enabling log rotation.

In a real-world production system, this caused a massive sys_log growth because PSR-3 log entries were additionally written into the database. In our case, a frequently triggered frontend logger call resulted in millions of sys_log rows within hours and filled the root partition completely.

The problematic part is that developers may copy the example mainly to enable RotatingFileWriter, without realizing that the DatabaseWriter remains active and continues writing to sys_log.

It might help to clarify in the documentation that:

DatabaseWriter is optional
it will continue writing to sys_log
high log volume can cause severe database growth
many installations may prefer file-only logging in production

For example, a safer minimal example could omit the DatabaseWriter entirely:

$GLOBALS['TYPO3_CONF_VARS']['LOG']['TYPO3']['CMS']['Core']['Resource']['ResourceStorage']['writerConfiguration'][LogLevel::ERROR] = [
    RotatingFileWriter::class => [
        'interval' => Interval::DAILY,
        'maxFiles' => 5,
    ],
];

Reviews 3

History 26

  1. Lina Wolf commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-19T12:15:09+00:00" > 09/19/26, 12:15 </span>

    Applied in changeset commit:1546b25ef6f30f99140d040d5c974d73a9c90544.