Bug #98583
closed
LocalConfig empty after low space condition
0%
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.
Updated by Stefan Froemken over 1 year ago
- Status changed from New to Closed
Hello Mordamir,
thank you for providing this issue to us.
TYPO3 will never know the "real" free webspace because of quotas, chroot env and other restricting services. It's the job of a sysadmin to interprete the error messages and check for enough webspace before installing TYPO3.
I will close the ticket now. If you feel this is the wrong decision, let me know, and I will re-open it.
Stefan