[TYPO3-dev] malformed cached config files

[Roland Hager]

Hi List,

We recently had some problems with malformed cached config files[1].
We had
   - unfinished files which gives us a syntax error
   - corrupted files with some bytecode in it.


Obviously this only happens when the config cache has to be regenerated. 
Sometimes the error occurs although no one cleared the config cache 
manually. So under which conditions the config cache files will be 
regenerated? Can anyone point me to the corresponding piece of code? 
Maybe we can add some debug infos to track down the cause.


The problem occurs mainly under high load and is quite rare. Our 
environment consists of four separated webservers with a shared network 
storage. To eliminate the network storage as point of failure we moved 
the typo3conf dir to each servers local storage but the problem 
persists. Additionally we than had problems with incomplete cached 
config files (extension missing on some webserver after installing it 
via EM). So even a single server seems to break the cached config files 
from time to time. We then moved them back to the shared storage.


So in short here are my two questions:

  1. When will those cached config files be regenerated and where is the 
corresponding code?

  2. Does anyone ever had similar problems and therefore some hints or - 
even better - a solution?


Thanks for your suggestions
Roland Hager

[1] typo3conf/tmp_CACHED_(FE)?_STRING_ext_(tables|localconf).php