Bug #95969
closedException\InvalidArgumentException after update from 10.4.20 to 10.4.21
0%
Description
After updating from 10.4.20 to 10.4.21 using the install tool, I got the following error:
(1/1) Symfony\Component\DependencyInjection\Exception\InvalidArgumentException
Expected to find class "VendorName\ExtensionName\DataProcessing\CsvFileProcessor" in file "/var/www/path/public/typo3conf/ext/my_extension/Classes/DataProcessing/CsvFileProcessor.php" while importing services from resource "../Classes/*", but it was not found! Check the namespace prefix used with the resource.
OS: Ubuntu 20.04.3 LTS / Debian 8
PHP-Version: 7.4.3
This issue occurred on two different servers.
I've tried different solutions suggested in other reports with similar issues (Bug #93134 and Bug #93169).
- dropping typo3temp/var/cache/code
- calling opcache_reset(); manually
- deleting the old sources
Unfortunaly nothing worked.
I tried to revert the update by manually setting the symlinks to the old source but the error persisted.
Files
Updated by Georg Ringer about 3 years ago
- Status changed from New to Needs Feedback
Thanks for reporting the issue. Some questions:
- Is the class
CsvFileProcessor
really there? - Where is it referenced?
Updated by Oliver Hader about 3 years ago
Can you please post the Services.yaml
configuration of your custom chronotours_theme
extension?
Updated by Robert Griebel about 3 years ago
Yes, the CsvFileProcessor is really there. It is not referencend anywhere at the moment.
Here is the content of the Service.yaml
services:
_defaults:
autowire: true
autoconfigure: true
public: false
In2code\Powermail\:
resource: '../Classes/*'
As I mentioned this issue happend on two different servers. The first one is the dev environment and the second one is the production environment. The problem first occurred at the production server after updating from 10.4.20 to 10.4.21 using the install tool. Since it was the production server and none of the suggested solutions worked, we restored the system from a backup. Unfortunaly there are no more error messages or log files from the production server. After that we tried to reproduce the issue at the Dev-Server. The above error message and the stack trace come from the dev server. The errors on both systems were almost identical except for the file referenced in the message. On the production server the file was a controller.
I checked the dev server today and the problem seems to be gone. No changes have been made since this report was submitted.
Updated by Georg Ringer about 3 years ago
closing the issue as the error is gone
Updated by Georg Ringer about 3 years ago
- Status changed from Needs Feedback to Closed
Updated by Robert Griebel about 3 years ago
Unfortunately, the error is not gone. It seems to be gone on the dev system but I can't update the production system and when the error occurs just wait 3 days for it to resolve itself.
Today I updated the dev server for another completely independent project via the typo3 backend and the problem started appearing there too. There where no issues before the update. Stacktrace is attached above.
All files are where they should be.