#109105Website down if sys_log is full
Description
It would be very nice and useful if TYPO3 can detect and warn before the sys_log reaches 4294967295 entries (INT) and not show an error 403 in this situation to the website user. We have changed the column type to BIGINT at this installation. Maybe this is a workaround in general.
We have a big and old multi domain website and of course tidy up our sys_log, but don’t touch the auto increment value.
Thank you.
Reviews 1
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch
- Commit message
-
[BUGFIX] Website down if sys_log is full Resolves: #109105 Releases: main
Files 1
History 46
-
Simon Schaufelberger commented <span data-processor="relativetime" data-value="2026-02-26T22:09:14+00:00" > 02/26/26, 22:09 </span>
-
Stefan Maischner commented and changed attached Bildschirmfoto 2026-02-27 um 00.09.03.jpg <span data-processor="relativetime" data-value="2026-02-27T06:08:33+00:00" > 02/27/26, 06:08 </span>
Could be in the reports. Or via the notification badge. Or per email.
-
Garvin Hicking commented and changed status
NewAccepted <span data-processor="relativetime" data-value="2026-02-27T06:34:18+00:00" > 02/27/26, 06:34 </span>We’ll raise to bigint as a first step. Reporting/warning could be done as a followup if still needed.
Thanks for bringing it up.
-
Gerrit Code Review pushed patch set 1 for main to change 93025 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-02-27T15:52:56+00:00" > 02/27/26, 15:52 </span> -
Gerrit Code Review pushed patch set 2 for main to change 93025 <span data-processor="relativetime" data-value="2026-02-27T16:13:36+00:00" > 02/27/26, 16:13 </span>
-
Garvin Hicking commented and changed status
Under ReviewNew <span data-processor="relativetime" data-value="2026-03-09T07:34:10+00:00" > 03/09/26, 07:34 </span>Sadly, things never are as easy as it seems.
Raising from INT to BIGINT for UIDs will create trouble in PHP scope, because at PHP_MAX (9223372036854775807) integers get converted from INT to STRINGs, and that would break quite a few integer type declarations in our code. So sadly this is not an option for our framework.
We’ll likely have to move to UUIDs for these tables, but that will be a breaking change.
For now, on project level, you can continue to adjust this to BIGINT and you’ll live long and prosper until you reach that 9223372036854775807 threshold. That’s quite some breathing room so we hope we’ll solve the UUID issue before this really breaks. ;-)
How would you expect that TYPO3 warns you?