Magento 2 Installation fails at 27% - php

I have this exception when running the installation for Magento 2. Couldn't find further information on how to fix this anywhere, error thrown was not very clear either. Anyone has any ideas? This happens after it says 'Running schema recurring...'
Module 'Magento_Amqp':
[ERROR] LogicException: Request schema definition for topic "shared.catalog.product.price.updated" should reference existing service class. Given "Magento\AsynchronousOperations\Api\Data\OperationInterface" in /var/www/tpb.com/html/vendor/magento/framework/Communication/Config/Validator.php:71
Stack trace:
#0 /var/www/tpb.com/html/vendor/magento/framework/Communication/Config/Reader/XmlReader/Converter.php(204): Magento\Framework\Communication\Config\Validator->validateRequestSchemaType('Magento\\Asynchr...', 'shared.catalog....')
#1 /var/www/tpb.com/html/vendor/magento/framework/Communication/Config/Reader/XmlReader/Converter.php(111): Magento\Framework\Communication\Config\Reader\XmlReader\Converter->extractTopicRequestSchema(Object(DOMElement))
#2 /var/www/tpb.com/html/vendor/magento/framework/Communication/Config/Reader/XmlReader/Converter.php(84): Magento\Framework\Communication\Config\Reader\XmlReader\Converter->extractTopics(Object(DOMDocument))
#3 /var/www/tpb.com/html/vendor/magento/framework/Config/Reader/Filesystem.php(171): Magento\Framework\Communication\Config\Reader\XmlReader\Converter->convert(Object(DOMDocument))
...

Related

Prestashop 1.7 - Error 503 - Service Unavailable

We started to have an issue on our prestashop backoffice. First, everything was super slow and now it isn´t even possible to access administration because of error 503.
I tried to delete the cache, checked all resources in cpanel (everything good). I found something in error_log, but have no idea if this can be cause by this.
[04-Feb-2023 23:03:03 US/Central] PHP Fatal error: Uncaught InvalidArgumentException: Invalid resource type: array in /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Utils.php:337
//UPDATED:
Stack trace: #0 /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Request.php(57): GuzzleHttp\Psr7\Utils::streamFor(Array)
#1 /home/plexrgvc/public_html/modules/ps_eventbus/src/Api/GenericClient.php(178): GuzzleHttp\Psr7\Request->__construct('POST', Object(GuzzleHttp\Psr7\Uri), Array, Array)
#2 /home/plexrgvc/public_html/modules/ps_eventbus/src/Api/EventBusProxyClient.php(138): PrestaShop\Module\PsEventbus\Api\GenericClient->post(Array)
#3 /home/plexrgvc/public_html/modules/ps_eventbus/src/Service/ProxyService.php(76): PrestaShop\Module\PsEventbus\Api\EventBusProxyClient->uploadDelete('repeat:9740b8b0...', '{"collection":"...')
#4 /home/plexrgvc/public_html/modules/ps_eventbus/src/Service/DeletedObjectsService.php(51): PrestaShop\Module\PsEventbus\Service\ProxyService->delete('repeat:9740b8b0...', Array)
#5 /home/plexrgvc/public_html in /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Utils.php on line 337
[04-Feb-2023 23:03:04 US/Central] PHP Fatal error: Uncaught InvalidArgumentException: Invalid resource type: array in /home/plexrgvc/public_html/modules/ps_eventbus/vendor/guzzlehttp/psr7/src/Utils.php:337
I tried to manually disable this module in phpmyadmin, but didn´t work. Any idea? Thanks

PHP fatal error uncaught exception after installing magento2

I have installed magento2 in my linux centos7. After installing magento2 successfully while accessing the web page is getting following error with empty content.
{{menuState.title}}
PHP version:7.1.3
OS: centos7
And the PHP-fpm error log has following error.
PHP Fatal error: Uncaught TypeError: Argument 1 passed to Zend_Controller_Plugin_Abstract::setResponse() must be an instance of Zend_Controller_Response_Abstract, instance of Magento\Framework\HTTP\PhpEnvironment\Response given, called in /var/www/magento2/lib/internal/Magento/Framework/Profiler/Driver/Standard/Output/Firebug.php on line 61 and defined in /var/www/magento2/vendor/magento/zendframework1/library/Zend/Controller/Plugin/Abstract.php:70
Stack trace:
#0 /var/www/magento2/lib/internal/Magento/Framework/Profiler/Driver/Standard/Output/Firebug.php(61): Zend_Controller_Plugin_Abstract->setResponse(Object(Magento\Framework\HTTP\PhpEnvironment\Response))
#1 /var/www/magento2/lib/internal/Magento/Framework/Profiler/Driver/Standard.php(195): Magento\Framework\Profiler\Driver\Standard\Output\Firebug->display(Object(Magento\Framework\Profiler\Driver\Standard\Stat))
#2 [internal function]: Magento\Framework\Profiler\Driver\Standard->display()
#3 {main}
thrown in /var/www/magento2/vendor/magento/zendframework1/library/Zend/Controller/Plugin/Abstract.php on line 70
How can I resolve this error?
This was a Magento Bug reported ...
But it's already been ...
https://github.com/magento/magento2/issues/7068
So, come on ...
Did you update the magento? What is the current version?
I found this information at the base of Magento: https://devdocs.magento.com/guides/v2.3/config-guide/bootstrap/mage-profiler.html
You have this option ...
The temporary fix is install symfony / yaml from dev branch and then our module:
              composer require symfony/yaml: dev-issue-814
    
          composer require mirasvit/module-profiler
Try using / installing php7.2
See this Magento Project reference >>>
https://magento.stackexchange.com/questions/49000/magento-2-is-there-a-profiler
Be sure to back up before the above procedures ...
Since I don't know the correct version of your current Magento, I looked for alternatives to fix.
I hope it helps you ...
Good luck! Send news about your progress ...

Laravel Cannot declare class Symfony\Component\HttpFoundation\AcceptHeader, because the name is already in use

I just took a project from a couple of months ago which was made in Laravel. This project also utilizes Laravel Voyager - the admin panel package.
After browsing to http://example.com/admin, I got this weird error which came out of nowhere and I'm also unsure how to debug it. It looks like this:
Fatal error: Cannot declare class Symfony\Component\HttpFoundation\AcceptHeader, because the name is already in use in /c/Users/User/Code/example-website/vendor/symfony/http-foundation/AcceptHeader.php on line 22
Fatal error: Uncaught Error: Class 'Symfony\Component\HttpFoundation\AcceptHeaderItem' not found in /c/Users/User/Code/example-website/vendor/symfony/http-foundation/AcceptHeader.php:61 Stack trace: #0 [internal function]: Symfony\Component\HttpFoundation\AcceptHeader::Symfony\Component\HttpFoundation\{closure}(Array) #1 /c/Users/User/Code/example-website/vendor/symfony/http-foundation/AcceptHeader.php(57): array_map(Object(Closure), Array) #2 /c/Users/User/Code/example-website/vendor/symfony/http-foundation/Request.php(1664): Symfony\Component\HttpFoundation\AcceptHeader::fromString('text/html,appli...') #3 /c/Users/User/Code/example-website/vendor/laravel/framework/src/Illuminate/Http/Concerns/InteractsWithContentTypes.php(54): Symfony\Component\HttpFoundation\Request->getAcceptableContentTypes() #4 /c/Users/User/Code/example-website/vendor/laravel/framework/src/Illuminate/Http/Concerns/InteractsWithContentTypes.php(44): Illuminate\Http\Request->wantsJson() #5 /c/Users/User/Code/example-website/vendor/laravel/framework/src/Illumina in /c/Users/User/Code/example-website/vendor/symfony/http-foundation/AcceptHeader.php on line 61
This error is very expected and I've never seen it before in my project (or anywhere else for that matter).
How can I debug this issue?
As a sanity check, delete the vendor directory and then run composer install to re-fetch your dependencies and see if the error is resolved. If not, then attempt composer update to fetch the latest versions of your dependencies in which this issue may have been resolved.

ServiceNotFoundException' 'Unable to resolve service "Router" to a factory

i'm using zend framework 3 with doctrine 2 and it giving me this error i dnt know why
Fatal error: Uncaught exception
'Zend\ServiceManager\Exception\ServiceNotFoundException' with message
'Unable to resolve service "Router" to a factory; are you certain you
provided it during configuration?' in
C:\xampp\htdocs\zendf\vendor\zendframework\zend-servicemanager\src\ServiceManager.php:681
Stack trace: #0
C:\xampp\htdocs\zendf\vendor\zendframework\zend-servicemanager\src\ServiceManager.php(757):
Zend\ServiceManager\ServiceManager->getFactory('Router') #1
C:\xampp\htdocs\zendf\vendor\zendframework\zend-servicemanager\src\ServiceManager.php(200):
Zend\ServiceManager\ServiceManager->doCreate('Router') #2
C:\xampp\htdocs\zendf\vendor\zendframework\zend-mvc\src\Application.php(158):
Zend\ServiceManager\ServiceManager->get('Router') #3
C:\xampp\htdocs\zendf\vendor\zendframework\zend-mvc\src\Application.php(273):
Zend\Mvc\Application->bootstrap(Array) #4
C:\xampp\htdocs\zendf\public\index.php(40):
Zend\Mvc\Application::init(Array) #5 {main} thrown in
C:\xampp\htdocs\zendf\vendor\zendframework\zend-servicemanager\src\ServiceManager.php
on line 681
I got the same problem while upgrading an app from zf2 to zf3.
I solved the problem by loading the module Zend\Router. There are some more modules coming with ZF3, so I ended up using this in the modules.config.php:
return [
'Zend\Cache',
'Zend\Form',
'Zend\Hydrator',
'Zend\InputFilter',
'Zend\Paginator',
'Zend\I18n',
'Zend\Filter',
'Zend\Router',
'Zend\Validator',
'Zend\Navigation',
...
];
I got the modules.config.php and the new application.config.php from the zf3 skeleton application.

Lumen 5.3 & PHP 7: Symfony Error ExceptionHandler

We have a project that uses Lumen 5.3, however when we always install PHP7 on the server it gives this error:
[Symfony\Component\Debug\Exception\FatalErrorException]
Uncaught TypeError: Argument 1 passed to Symfony\Component\Debug\ExceptionHandler::handle() must be an instance of Exception, instance of Error given in /var/www/retail-api/vendor/symfony/symfony/src/Symfony/Component/Debug/Excepti
onHandler.php:105
Stack trace:
#0 [internal function]: Symfony\Component\Debug\ExceptionHandler->handle(Object(Error))
#1 {main}
thrown
When we revert it back to PHP5.6 it works. Based on my research this was supposed to be fixed in Symfony > 2.6 is this correct? If so why is this happening on our environment. Most of our Laravel projects are already using PHP7. This, however is an exception, is there something that I am missing?

Categories