Issue Bug Closed

#98583LocalConfig empty after low space condition

Mordamir 10/12/22, 09:03 updated 06/25/23, 00:56

Description

Maybe i choose the wrong category, this is somehow related to the bootstrapping process.

Unfortunatelly we had a no space condition on our typo3 server. Its ok to behave erronous in such an exceptional condition, but it should work if the condition vanishes. The problem resulted by the no space condition was, that typo3 wrote out an empty LocalConfiguration.php while there was no space on the server. And because the LocalConfiguration.php is empty and not removed, typo3 does not use a default configuration here.

The expected behaviour should be, that typo3 should not write the LocalConfiguration if there is no space on the server.

It seems that typo3 is rewriting the LocalConfiguration on every request on our server (the timestamp of the file is always current), maybe this is caused by an extension, but i dont know how to find that out.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.