'Readiness Check' fail.

[zolotokrylin]

Magento is out of the box. Clean, without any sample data.

Can not pass the readiness check, because of the: "We found conflicting component dependencies.".
And the troubleshooting doesn't give any hint, what components have conflict.

What should I do, so I can fix it?

If you're attempting System Upgrade, I strongly advise you to wait. There are known upgrade issues that should be resolved very soon. It's simpler to leave your system at 2.0.0 until the resolution is announced.

If you're trying Component Manager, the issue appears to be with your cron setup. When I run the readiness check, the message is:

Check Updater Application Availability
Updater application is available.

Check Cron Scripts
Cron script readiness check passed.

It appears as if your cron scripts are running frequently enough. You might pass the readiness check if you try it now but we'd recommend you review your cron setup.

[mazhalai]

@hommedeplage is there anything in var/log/system.log? What about server and php logs?

[zolotokrylin]

@xcomSteveJohnson thank you for advice, but I think this is not the reason.
I have the 2.0.1v from the zip file.
I changed the cron frequency to lower, as no need to do it every minute on the dev machine. Before it was every minute cron job, but the same issue was appearing.

@mazhalai this is the system.log:
[2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'notification.messages' element cannot be added as child to 'header', because the latter doesn't exist [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'header.inner.left' element cannot be added as child to 'header', because the latter doesn't exist [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'header.inner.right' element cannot be added as child to 'header', because the latter doesn't exist [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'logo' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'logo', but their parents are different: 'header' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'user' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'page.actions.toolbar' tries to reorder itself towards '', but their parents are different: 'page.main.actions' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'system_messages' tries to reorder itself towards '', but their parents are different: 'notifications' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'unread_system_messages' tries to reorder itself towards 'system_messages', but their parents are different: 'notifications' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'notification.messages' tries to reorder itself towards 'user', but their parents are different: 'header' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'header.inner.left' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'header.inner.right' tries to reorder itself towards 'header.inner.left', but their parents are different: 'header' and '' respectively. [] [] [2016-01-29 03:30:24] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and '' respectively. [] [] [2016-01-29 03:30:39] main.INFO: Cache file with merged layout: LAYOUT_adminhtml_STORE2_391fccd54da687afc76a5d6559b714906: Please correct the XML data and try again. [] [] [2016-01-29 03:30:39] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 03:30:39] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 03:30:39] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] [] [2016-01-29 03:31:06] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 03:31:06] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] [] [2016-01-29 03:31:06] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []

The server error.log:
[Fri Jan 29 03:43:34.482951 2016] [:error] [pid 2106] [client 192.168.33.1:51439] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 1278473 bytes) in /vagrant/magento/vendor/composer/composer/src/Composer/Cache.php on line 71, referer: http://vr-test.local/setup/

[zolotokrylin]

Fixed it by executing the following actions: http://devdocs.magento.com/guides/v2.0/release-notes/tech_bull_201-upgrade.html#resolution2

[webspeaks]

Readiness check is failing in case of upgrading from 2.0.2 to 2.0.3

Error:
Check Component Dependency
We found conflicting component dependencies. Hide detail
For additional assistance, see component dependency help .

I see that an AJAX call fails during readiness check. Please see below screenshots:
http://joxi.ru/Q2KpV7qI9J5Q7A
http://joxi.ru/p275O7Ec0gyker

[Microstudioweb]

I have same problem of @arvind07
Tring to upgrade form system upgrade, but get error on check component dependency

[hempienl]

I've managed to fixed the Check Component Dependency by increasing my php_memory_limit from 256 to 512mb. I hope it helps anyone.

[webspeaks]

@hempienl It did not work for me :(

[Microstudioweb]

@hempienl Thanks, it works for me.
@arvind07 Can you check via phpinfo(); if your server has incerease the memory limit? because on my case I have to modify a domain php.ini, not the global file.

[webspeaks]

@hempienl @Microstudioweb Thanks, ma bad!
I am running on nginx. And Magento's nginx.cong.sample has PHP memory limit set to 256M
fastcgi_param PHP_VALUE "memory_limit=256M \n max_execution_time=600";
Thats why my php.ini changes were not reflecting. I updated the nginx.cong.sample and it worked.

[webspeaks]

However I bumped into another issue: Cannot allocate memory.
See: http://joxi.ru/RmzqekQfWNp7Yr

I have 1 GB RAM. I think that should be enough.

[hempienl]

@arvind07 I also got errors during the installation, so i decided to update it using composer
http://magento.stackexchange.com/questions/99813/how-to-update-magento2-from-2-0-0-to-2-0-2

[quienti]

composer require magento/product-community-edition 2.0.3 --no-update
composer update

[ayodio]

Increasing the memory_limit worked for me too but I had to increase it to 600M (512M was enough).