#55099PHP Warnings after clearing configuration cache in BE
Description
Steps to reproduce
- rm -rf typo3temp/*
- Open BE, Page module
- Click on some random page in the tree
- Clear the configuration cache via toolbar icon
- Click on some page again in the tree
An extdirect exception popups at the bottom of the BE
Warning: rename(/var/www/html/master/typo3temp/Cache/Data/cache_classes/52d9026814521.temp,/var/www/html/master/typo3temp/Cache/Data/cache_classes/typo3_cms_extbase_property_typeconverter_fileconverter): No such file or directory in ..../typo3/sysext/core/Classes/Cache/Backend/SimpleFileBackend.php on line 244
(the affected class looks rather random, but it is always the same line 244)
You can continue at this point to work in BE, but
if you clear the configuration cache again and
*quickly* click on a page in the tree, the complete BE fails.
The warning above is displayed again and additionally this is displayed:
PHP Warning: Class 'TYPO3\CMS\Core\Log\Loggerphp' not found in ..../typo3/sysext/core/Classes/Core/ClassAliasMap.php line 270 or PHP Warning: Class 'TYPO3\CMS\Core\Resource\ResourceInterfacer\AbstractController' not found in ..../typo3/sysext/core/Classes/Core/ClassAliasMap.php line 270
One has to clear typo3temp manually in order to get the BE back to work.
I’ve no clue what’s going on here, looks like some timing issue and/or race condition.
Note: I’ve activated this setting in the installer in order to really see all (otherwise silent) warnings:
[‘SYS’][‘exceptionalErrors’] => ‘28674’
Reviews 2
Related issues 7
- Feature #47712Refactor Locking
- Bug #54768t3lib_pageSelect* compatibility classes not loaded in backend
- Bug #54906Fatal error: Interface 'Psr\Log\LoggerInterface' not found
- Bug #55029Class Loader fails if entry in class cache is discarded
- Bug #55294Under heavy load, two request can simultaneously write to same cache file - should use locking
- Bug #57008New Installation: Could not acquire lock for ClassLoader
- Bug #67366PHP Errors after clearing cache in BE