magento2: Magento v2.1.2: Check Component Dependency We found conflicting component dependencies.

Preconditions

Magento v 2.1.2
PHP 5.6

Steps to reproduce

Install an module from Magento Store
Component Manager
Install Store Module
Readiness Check

Expected result

Continue to Step 2 to install the module
The Readiness Check stuck on error:

Check Component Dependency
We found conflicting component dependencies. Hide detail

For additional assistance, see component dependency help .

Actual result

[Screenshot, logs]

The: http://xxxxxx.de/setup/index.php/dependency-check/component-dependency 500 (Internal Server Error) tell me:

An error occurred during execution; please try again later.

Additional information:

Exception

File:
/var/www/share/xxxxxx.de/htdocs/vendor/magento/framework/App/ErrorHandler.php:61
Message:
Warning: Invalid argument supplied for foreach() in /var/www/share/xxxxxx.de/htdocs/setup/src/Magento/Setup/Controller/DependencyCheck.php on line 73
Stack trace:
#0 /var/www/share/xxxxxx.de/htdocs/setup/src/Magento/Setup/Controller/DependencyCheck.php(73): Magento\Framework\App\ErrorHandler->handler(2, 'Invalid argumen...', '/var/www/share/...', 73, Array)
#1 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-mvc/src/Controller/AbstractActionController.php(82): Magento\Setup\Controller\DependencyCheck->componentDependencyAction()
#2 [internal function]: Zend\Mvc\Controller\AbstractActionController->onDispatch(Object(Zend\Mvc\MvcEvent))
#3 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-eventmanager/src/EventManager.php(444): call_user_func(Array, Object(Zend\Mvc\MvcEvent))
#4 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-eventmanager/src/EventManager.php(205): Zend\EventManager\EventManager->triggerListeners('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#5 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-mvc/src/Controller/AbstractController.php(118): Zend\EventManager\EventManager->trigger('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#6 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-mvc/src/DispatchListener.php(93): Zend\Mvc\Controller\AbstractController->dispatch(Object(Zend\Http\PhpEnvironment\Request), Object(Zend\Http\PhpEnvironment\Response))
#7 [internal function]: Zend\Mvc\DispatchListener->onDispatch(Object(Zend\Mvc\MvcEvent))
#8 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-eventmanager/src/EventManager.php(444): call_user_func(Array, Object(Zend\Mvc\MvcEvent))
#9 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-eventmanager/src/EventManager.php(205): Zend\EventManager\EventManager->triggerListeners('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#10 /var/www/share/xxxxxx.de/htdocs/vendor/zendframework/zend-mvc/src/Application.php(314): Zend\EventManager\EventManager->trigger('dispatch', Object(Zend\Mvc\MvcEvent), Object(Closure))
#11 /var/www/share/biokamine.de/htdocs/setup/index.php(31): Zend\Mvc\Application->run()
#12 {main}

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 4
Comments: 36 (12 by maintainers)

Most upvoted comments

Solved the same issue local php values in .htaccess and .user.ini were overriding master php values in php.ini

increased php local memory_limit in .htaccess and .user.ini to 2G php master memory_limit was already 2G

hope this helps someone.

nittn on Apr 6, 2019

@nittn THANK YOU!! This resolved my issue! I successfully upgraded from 2.3.0 -> 2.3.1.

I noticed that .htaccess and .user.ini are still set to 756M in 2.3.1. Unless there is a good reason for them to be this then I would suggest devs to make the change. I won’t make a pull request myself as I don’t want to encroach on something I’ve got no knowledge of!!

TechnoBuddhist on Apr 17, 2019

@engcom-backlog-nazar I explained the whole problem behind the issue in https://github.com/magento/magento2/issues/7917#issuecomment-453583809, https://github.com/magento/magento2/issues/7917#issuecomment-453658759 and https://github.com/magento/magento2/issues/7917#issuecomment-453690781

Nothing has changed on the 2.3-develop branch:

.htaccess still has php_value memory_limit 756M
nginx.conf.sample still has fastcgi_param PHP_VALUE "memory_limit=756M \n max_execution_time=600";

dandelionred on Apr 5, 2019

@orlangur

default memory limit is correct according to

The string from nginx.conf.sample I referenced above was inside location ~* ^/setup($|/) {}. Hence the stock nginx config sample suggests 756M for /setup/ even though the doc says 2G for Installing and updating Magento components. Since dependency check takes over 1G the thing doesn’t work at all out-of-the-box.

So, I believe there must be at least some warning in case of lower memory limit.

I’m sure the main problem here is there is no feedback on the server-side error. It treats anything but OK as “We found conflicting component dependencies”.

Back to the heavy cpu usage during dependency check

It’s Composer, dude, and such behavior is correct 😃

Strangely enough, installing an extension with composer require ... has no such problems. You said above the web UI for managing extensions is a wrapper around composer. The wrapper is probably wrapped too much!

dandelionred on Jan 11, 2019