Bug #93169
closed
500 error, [CRITICAL] request="42945d6a42cae"
0%
Description
After upgrade from 10.4.9 to 10.4.12 i got the following error:
Fri, 25 Dec 2020 09:17:28 +0100 [CRITICAL] request="42945d6a42cae" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Expected to find class "TYPO3\CMS\Core\Context\FileProcessingAspect" in file "/var/www/....de/httpdocs/typo3cms/typo3_src-10.4.12/typo3/sysext/core/Classes/Context/FileProcessingAspect.php" while importing services from resource "../Classes/*", but it was not found! Check the namespace prefix used with the resource. | Symfony\Component\DependencyInjection\Exception\InvalidArgumentException thrown in file /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/vendor/symfony/dependency-injection/Loader/FileLoader.php in line 206. Requested URL: https://www.....de/typo3/index.php?route=%2Fmain&token=--AnonymizedToken-- - {"TYPO3_MODE":"BE","exception":"Symfony\\Component\\DependencyInjection\\Exception\\InvalidArgumentException: Expected to find class \"TYPO3\\CMS\\Core\\Context\\FileProcessingAspect\" in file \"/var/www/....de/httpdocs/typo3cms/typo3_src-10.4.12/typo3/sysext/core/Classes/Context/FileProcessingAspect.php\" while importing services from resource \"../Classes/*\", but it was not found! Check the namespace prefix used with the resource. in /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/vendor/symfony/dependency-injection/Loader/FileLoader.php:206\nStack trace:\n#0 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/vendor/symfony/dependency-injection/Loader/FileLoader.php(99): Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->findClasses('TYPO3\\\\CMS\\\\Core\\\\', '../Classes/*', Array)\n#1 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/vendor/symfony/dependency-injection/Loader/YamlFileLoader.php(611): Symfony\\Component\\DependencyInjection\\Loader\\FileLoader->registerClasses(Object(Symfony\\Component\\DependencyInjection\\Definition), 'TYPO3\\\\CMS\\\\Core\\\\', '../Classes/*', NULL)\n#2 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/vendor/symfony/dependency-injection/Loader/YamlFileLoader.php(233): Symfony\\Component\\DependencyInjection\\Loader\\YamlFileLoader->parseDefinition('TYPO3\\\\CMS\\\\Core\\\\', Array, '/var/www/vhosts...', Array)\n#3 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/vendor/symfony/dependency-injection/Loader/YamlFileLoader.php(153): Symfony\\Component\\DependencyInjection\\Loader\\YamlFileLoader->parseDefinitions(Array, '/var/www/vhosts...')\n#4 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/typo3/sysext/core/Classes/DependencyInjection/ContainerBuilder.php(119): Symfony\\Component\\DependencyInjection\\Loader\\YamlFileLoader->load('Services.yaml')\n#5 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/typo3/sysext/core/Classes/DependencyInjection/ContainerBuilder.php(84): TYPO3\\CMS\\Core\\DependencyInjection\\ContainerBuilder->buildContainer(Object(TYPO3\\CMS\\Core\\Package\\PackageManager), Object(TYPO3\\CMS\\Core\\DependencyInjection\\ServiceProviderRegistry))\n#6 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/typo3/sysext/core/Classes/Core/Bootstrap.php(141): TYPO3\\CMS\\Core\\DependencyInjection\\ContainerBuilder->createDependencyInjectionContainer(Object(TYPO3\\CMS\\Core\\Package\\PackageManager), Object(TYPO3\\CMS\\Core\\Cache\\Frontend\\PhpFrontend), false)\n#7 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/typo3/index.php(25): TYPO3\\CMS\\Core\\Core\\Bootstrap::init(Object(Composer\\Autoload\\ClassLoader))\n#8 /var/www/....de/httpdocs/typo3cms/typo3_src-10.4.9/typo3/index.php(26): {closure}()\n#9 {main}"}
Updated by Riccardo De Contardi almost 4 years ago
Hi can you give more details? For example which steps did you follow to update TYPO3?
I performed an update 10.4.9 > 10.4.12 using composer and did not have this error.
Updated by Helmut Winkelbach almost 4 years ago
after changing the symlink i could see the login page for a second and the error appeared.
After deleting var/cache the same, 1 second login page the error appeared.
Updated by Riccardo De Contardi almost 4 years ago
so far, I have understood that you are using the "plain" installation method with symlinks;
I assume you have already tried to perform deep cache cleaning and dump autoload from the Install Tool...
Updated by Michael Sollmann over 3 years ago
Can confirm this.
It seems that on some servers we have to delete the old sources to get the error gone.
Related to https://forge.typo3.org/issues/93134
Updated by Christian Weiske over 3 years ago
- Related to Bug #93134: Exception\InvalidArgumentException class FileProcessingAspect not found added
Updated by Thomas Sperling over 3 years ago
I had the same problem. Deletion of old source did not work.
I had to call opcache_reset(); manually.
Updated by Christian Kuhn over 3 years ago
- Status changed from New to Closed
Hey.
Thanks for your feedback on this.
When DI changes between versions, it may result in backend fatals. Dropping typo3temp/var/cache/code should help.
For patch level upgrades in non-composer mode done via the install tool, this is done automatically, the DI cache can also be cleared in the install tool with 'clear all cache' which also resets opcode, if possible.
opcache is by default configured to detect file changes automatically, so usally, a manual reset isn't required. Still, core has some places to do that automatically at some places. However, if your hosting is configured to not detect file changes in opcache automatically, it may depend on your deployment strategies if you need to trigger this within your deployment scripts.
I think there isn't much we can do at the moment in core. I'll go ahead and close this issue for now. Please open a new one if you think there is something left to do.