Issue Bug Closed

#109290DatabaseWriter does not set tstamp, causing TableGarbageCollectionTask to delete all logging framework entries from sys_log immediately

Sebastian Michaelsen 03/19/26, 11:26 updated 03/31/26, 08:09

Description

TYPO3\CMS\Core\Log\Writer\DatabaseWriter inserts log records into sys_log but never sets tstamp, leaving it at the column default of 0. At the same time, EXT:scheduler registers sys_log for garbage collection using tstamp as the dateField:

// EXT:scheduler ext_localconf.php
‘sys_log’ => [‘dateField’ => ‘tstamp’, ‘expirePeriod’ => 180]

Since 0 will be interpreted as January 1st 1970, TableGarbageCollectionTask deletes every entry written by DatabaseWriter on every run — regardless of actual age. This is a silent data loss.

Steps to reproduce

1. Configure any namespace to log via DatabaseWriter.
2. Set up a TableGarbageCollectionTask targeting sys_log
3. Run the task — all entries written by DatabaseWriter are gone.

Proposed fix

DatabaseWriter::writeLog() should set tstamp alongside time_micro, consistent with how BackendUserAuthentication::writelog() populates the field:

$fieldValues = [
‘request_id’ => $record->getRequestId(),
‘time_micro’ => $record->getCreated(),
‘tstamp’ => (int)$record->getCreated(), // add this
‘component’ => $record->getComponent(),
‘level’ => LogLevel::normalizeLevel($record->getLevel()),
‘message’ => $record->getMessage(),
‘data’ => $data,
];

Reviews 2

History 49

  1. Sebastian Michaelsen changed subject DatabaseWriter does not set tstamp, causing TableGarbageCollectionTask to delete all framework log entries from sys_log immediately DatabaseWriter does not set tstamp, causing TableGarbageCollectionTask to delete all logging framework entries from sys_log immediately <span data-processor="relativetime" data-value="2026-03-19T11:40:58+00:00" > 03/19/26, 11:40 </span>

  2. Garvin Hicking commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-03-19T12:59:41+00:00" > 03/19/26, 12:59 </span>

    Sounds good, would you like to create a gerrit patch?

  3. Gerrit Code Review pushed patch set 1 for main to change 93278 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2026-03-19T13:38:56+00:00" > 03/19/26, 13:38 </span>

  4. Sebastian Michaelsen commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-03-22T16:45:10+00:00" > 03/22/26, 16:45 </span>

    Applied in changeset commit:fc2a6881ab7d3a6456192294475fd2707aaafb57.