Bug #93461
closed
fresh installation of V11.0 Bootstrap.php problem
0%
Description
I cannot install V11. A fatal error happened by executing Bootstrap::init. Is looking for "cache_core". But it should only "core" I guess!
Have the same problem with V10 but not with V9!
Running Server 2019 with IIS.
PHP Version 7.4.15
I have to solve this problem asap!
Mon, 08 Feb 2021 11:43:39 +0100 [CRITICAL] request="c8451e01071c6" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1203699034: A cache with identifier "cache_core" does not exist. | TYPO3\CMS\Core\Cache\Exception\NoSuchCacheException thrown in file C:\inetpub\wwwroot\typo3\sysext\core\Classes\Cache\CacheManager.php in line 138. Requested URL: https://v11.althoff-fam.de/ - {"TYPO3_MODE":"FE","exception":"TYPO3\\CMS\\Core\\Cache\\Exception\\NoSuchCacheException: A cache with identifier \"cache_core\" does not exist. in C:\\inetpub\\wwwroot\\typo3\\sysext\\core\\Classes\\Cache\\CacheManager.php:138\nStack trace:\n#0 C:\\inetpub\\wwwroot\\typo3\\sysext\\core\\Classes\\Core\\Bootstrap.php(109): TYPO3\\CMS\\Core\\Cache\\CacheManager->getCache('cache_core')\n#1 C:\\inetpub\\wwwroot\\index.php(24): TYPO3\\CMS\\Core\\Core\\Bootstrap::init(Object(Composer\\Autoload\\ClassLoader))\n#2 C:\\inetpub\\wwwroot\\index.php(25): {closure}()\n#3 {main}"}
Updated by Christian Kuhn about 3 years ago
- Status changed from New to Needs Feedback
This looks as if your PHP sources are not up to date:
- In v9, the 'getCache(cache_core)' is in Bootstrap line 109, just as shown in your backtrace above
- In v10, there is no such call, it is 'static::createCache('core', $disableCaching);' in line 104 instead
- Similar in v11.
Please check your php source locations / webserver socket/fpm/cgi routing.
Updated by
Updated by Hans-Georg Althoff about 3 years ago
Christian,
you are right.
I have looked into bootstrap.php and find out that on line 109, there is an empty line.
Here my folder structure:
..\inetpub\wwwroot\typo3(V9 installation)
..\inetpub\wwwroot\Typo3V10\typo3\(V10 installation)
..\inetpub\wwwroot\Typo3V11\typo3\(V11 installation)
Why is Typo3 reading the file in the wwwroot directory and not in the right sub directory?
This maybe the problem.
The installation files are upto date!
Updated by Christian Kuhn about 3 years ago
- Status changed from Needs Feedback to Closed
This smells like an instance / setup related issue. You may need to review your webserver fpm/cgi related setup and sockets or links.
I'll close here since this is not a core issue but a setup problem.
If you're struggling with details on this, feel free to ask for additional help in #typo3-cms on slack.
Updated by Hans-Georg Althoff about 3 years ago
Christian,
that cannot be a setup problem. I have checked it several times.
Typo3 is starting to generate the Typo3temp directory but than is calling the right file in a wrong directory.
Even Let's Encrypt is working correct in this sub domain.
If I am using V9 it works fine with the same setup in this sub domain.
It is not right to close the bug!!!!
Updated by Benni Mack about 3 years ago
Hans-Georg Althoff wrote in #note-5:
Christian,
that cannot be a setup problem. I have checked it several times.
Typo3 is starting to generate the Typo3temp directory but than is calling the right file in a wrong directory.
Even Let's Encrypt is working correct in this sub domain.
If I am using V9 it works fine with the same setup in this sub domain.It is not right to close the bug!!!!
Hey Hans-Georg,
can you please provide me with details to reproduce this issue? Can you ping me on slack to sort this out. I am also 99.99% sure this is a setup problem, but none-the-less, happy to support you with this issue. Maybe we can do a screen-share or something along the lines? Feel free to DM me in slack to sort this out.
Benni.