TYPO3 Core

Now that I read this here, I dimly remember having seen such an issue on a 6.2 instance as well. I thought of a realurl bug and moved to the version of helhum.

I'll install the original realurl again and will re-test.

Currently we do not use an OPcode cache, so there should not be the Problem. Our TYPO3 Version is 6.2.12 and the realurl version is 1.13.3.

I found out how to reproduce the two errors mentioned in my posting above. We use the extension igldapssoauth for backend login. So this error is raised in the following cases:

• Backend login attempt if typo3temp/Cache/Data/cache_classes is empty
• Backend login refresh with Ajax if typo3temp/Cache/Data/cache_classes is empty
• Call on "typo3/cli_dispatch.phpsh extbase something" if typo3temp/Cache/Data/cache_classes is empty

The realurl error is shown on a FE call only.

I have seen a third error mentioning a classname of one of our own extensions, but until now i do not know how to reproduce this one. It is used in a long running process called by crontab. Perhaps it occurs when the process is running and the folder typo3temp/Cache/Data/cache_classes is cleared in the meanwhile...

I was told this issue should be resolved in 6.2.13, which will be released in the next few hours. Please test again with .13 then.

This must have been some issue in the class loader as I could verify the empty cache files. As I said, I'm not able to reproduce again and I'm sure I had no concurrent requests running.

Hi,

I am having nearly the same problem. I am not completely sure if it is exactly the same.

When you have too much traffic on your page the cache is not cleared completely before new cache entries arrive.
That is why I get the following error:
"PHP Fatal error: Class 'Tx_Solr_PluginCommand' not found in <path>/typo3temp/Cache/Code/cache_core/ext_localconf_97bba9aa9ddf78aa54d1ba36d6ec429832fc4c76.php"
But this is just an example.

Like Alexander Ließmann initially stated, this error message seams to be random, because the error can occure on every cached class. And if you test that at midnight (with nearly no traffic) everything works fine.

This is the test I can reproduce the error.

1. Use wget to read the hole page recursivly (to make traffic)
- I did this on our testing environment, because the live page has enough traffic to allways have the error
2. Clear the Cache in the Install Tool (TYPO3 6.2.9 and 6.2.13)
- And you get a white page with a 'random' error message.

Could someone else reproduce this problem on TYPO3 Version 6.2.13?

Greetings Kerstin

I'm having this issue as well. I'm getting 0 KB (empty) cache files in cache_classes on those classes it cannot find.

I don't know whether this is symptomatic or the cause.

Thats the cached result, that it didn't find the classes.

Please always specify the exact TYPO3 version you are using. Thanks.

Maybe this Issue is related to https://forge.typo3.org/issues/54984 ?

Hi guys,

I just can confirm on instances after upgrading from 6.2.12 to 6.2.14, I get an error after "clear all caches" in install tool immediately after clicking the button like:
PHP Warning: require_once(.../htdocs/typo3temp/Cache/Code/cache_core/ClassLoader_75fde3487a164478ad1b5ce95564b364.php): failed to open stream: No such file or directory in .../typo3_src/typo3/sysext/core/Classes/Cache/Backend/SimpleFileBackend.php on line 364

We have OpCache enabled. On my local machine I cannot reproduce this with or without OpCache enabled.
Reloading the backend gives a white page for about 7 seconds, then the cache is up again and the system works again as expected.

Maybe this helps.

Regards
merzilla

@Ralf Merz

This looks like another issue. You may find "Could not acquire look" error messages in your log files.

We got this error:

Fatal error: Class 'tx_realurl_apiwrapper'  not found in /var/www/typo3conf/ext/realurl/class.tx_realurl.php on line 177

We also got the "typo3temp/Cache/Data/cache_classes/" with empty files when calling page from backend in production environment.
The patch in #67246 resolved this issue.

Seems like same problem still exists in TYPO3 8.7.25. We are getting strange errors for some requests just right after clearing caches in backend - but only if there is some traffic on the website (multiple users online) - then some of the users get error 500 and others not - this happens in about up to first 30 seconds after clearing cache. However since our website is quite high traffic that means many users get error 500 during that time.

Example error is:

"Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1166546734: Package "realurl" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive). | TYPO3\CMS\Core\Package\Exception\UnknownPackageException thrown in file .......vendor/typo3/cms/typo3/sysext/core/Classes/Package/PackageManager.php in line 500. Requested URL: ......................."

I was able to reproduce that locally too. When I do that manually on local/dev etc I am just opening several (10 is usually enough) subpages of my website in another browser. Then I am clearing cache and then after that I am refreshing those pages as fast as possible. Usually few of them return error 500 while some others return 200 OK.
So it is matter of sending some requests to the page right after clearing cache.

Can you reproduce this on a plain new (empty) TYPO3 instance, or does it require some/certain extensions to be installed?
Can you maybe provide the list of extensions you have activated?

I've just made clean installation of TYPO3 8.7.25 and installed introduction package so that I have some frontend displayed. And I am able to reproduce that problem.

In order to reproduce I need to set memory_limit on my server as low as possible - however it should be high enough so that server is not returning "PHP Fatal error: Allowed memory size of ..... bytes exhausted (tried to allocate ....bytes)". In my case if I set 16M memory_limit I am getting that error but if I set 32M memory_limit then I am not getting that error anymore but instead TYPO3 error. So I am proceeding with 32M memory limit to be able to reproduce that error.

Then I am proceeding as described in previous comment already. Opening 5-10 subpages, clearing caches in backend and then refreshing those pages (incognito) as fast as possible. In that case I am getting errors like (however not always but only sometimes):

Core: Exception handler (WEB): Uncaught TYPO3 Exception: syntax error, unexpected ''/var/www/vhosts/................' (T_ENCAPSED_AND_WHITESPACE) | ParseError thrown in file /var/www/vhosts/.............../....................../web/typo3temp/assets/bootstrappackage/lessphp_ng44dxe9mhc840cg80cocs00s8k8wko.lesscache in line 1. Requested URL: http://......................./index.php?id=2