Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot upgrade to Magento 2.0.4 #4013

Closed
jaimestuardo opened this issue Apr 5, 2016 · 14 comments
Closed

Cannot upgrade to Magento 2.0.4 #4013

jaimestuardo opened this issue Apr 5, 2016 · 14 comments
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@jaimestuardo
Copy link

When Trying to upgrade from 2.0.2 to 2.04 using system upgrade, I get the following errors in Readiness Check:

Check Cron Scripts

Cron script readiness check failed. Hide detail

Error from Updater Application Cron Script:
Found non-writable path(s):
/home/depasa/public_html/app/design/frontend/Desytec/depasa_v1/Magento_Checkout/web/template/cart/totals
/home/depasa/public_html/webpay/cgi-bin/maestros/privada.pem
/home/depasa/public_html/webpay/cgi-bin/maestros/tbk_public_key.pem
/home/depasa/public_html/webpay/cgi-bin/maestros/backup
/home/depasa/public_html/webpay/cgi-bin/log/backup
/home/depasa/public_html/webpay/cgi-bin/datos/tbk_param_20160324.txt
/home/depasa/public_html/pub/static/frontend/Desytec/depasa_v1/es_ES/Magento_Checkout/js/form/element/region.js

For additional assistance, see cron scripts help.
Check Component Dependency

We found conflicting component dependencies. Hide detail

For additional assistance, see component dependency help .

All of them are nonsenses and help does not really help.

Regards
Jaime

@mazhalai
Copy link
Contributor

mazhalai commented Apr 5, 2016

@jaimestuardo so as suggested, did you check the file permissions? Looks like pub/static needs to be writable. Not sure about the other files.

@jaimestuardo
Copy link
Author

Of course. all permissions are correct, unless I have to set 777 permissions for all files and folders. Furthermore, what about app/design/frontend/Desytec/depasa_v1/Magento_Checkout/web/template/cart/totals? why that folder needs to be writable? it is my custom template.

And /webpay folder is a custom folder I am using with my own payment method. It contains CGI files that of course should not be writable. Is this a bug in cron validation which is validating something that it should not validate?

@mazhalai
Copy link
Contributor

mazhalai commented Apr 5, 2016

Yes I agree about the unnecessary files. Created MAGETWO-51544 to investigate and fix.

@mazhalai mazhalai added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development and removed Progress: needs update labels Apr 5, 2016
@jaimestuardo
Copy link
Author

Meanwhile, is there a way to upgrade by bypassing that verification?

@mazhalai
Copy link
Contributor

@jamescowie I would suggest to either move the files out of magento root during upgrade, and then copy them back or give full write permissions(not recommended) but as long as you change it back as soon as upgrade is done.

@andparsons
Copy link

I'm getting the same error while trying to upgrade via the web interface.
I've moved the custom theme outside the root folder, but it seems to have cached the error as it still shows the same paths are an issue.
I've tried clearing the cache from the flush cache page, but to no avail.
Can you help me find where this would be being cached?

@mazhalai
Copy link
Contributor

@andparsons there are a number of files created in the var directory that begin with . check .update_cronjob_status and remove it. Wait for cron to run again, or run the commands manually, and you should be able to continue.

@jaimestuardo
Copy link
Author

This is very annoying. I have removed the cache after I move the folders out of Magento root, and I got more errors now: PHP Version Check, PHP Settings Check, etc and etc. All those checks were correct before, and in fact, all of them are correct. I have removed .setup_cronjob_status and .update_cronjob_status according to this page http://devdocs.magento.com/guides/v2.0/comp-mgr/trouble/cman/component-depend.html but nothing works now.

@mazhalai
Copy link
Contributor

@jamescowie can you please very that are your cronjobs running as expected? It should create new .setup_cronjob_status and .update_cronjob_status files.

@jaimestuardo
Copy link
Author

Only .update_cronjob_status:

-rw-r--r-- 1 depasa depasa 148 abr 11 19:09 .update_cronjob_status

@mazhalai
Copy link
Contributor

@jaimestuardo you need a total of 3 cronjobs /bin/magento setup:cron:run creates . setup_cronjob_status Can you verify it is running? You can try running the command manually too.

@jaimestuardo
Copy link
Author

Now, this is the error I am getting:

PHP Settings Check
Need Help?
PHP Documentation
Your PHP Version is 5.6.20, but always_populate_raw_post_data = 0. $HTTP_RAW_POST_DATA is deprecated from PHP 5.6 onwards and will be removed in PHP 7.0. This will stop the installer from running. Please open your php.ini file and set always_populate_raw_post_data to -1. If you need more help please call your hosting provider.

This is nonsense,since my php.ini has already that option with -1.

magento-team pushed a commit that referenced this issue May 13, 2016
- Added functionality on setup cron side to prepare list of directories and files
  that updater application will need write permissions to perform upgrade
- Updated updater application to just consider this file list while doing file permissions
  check
magento-team pushed a commit that referenced this issue May 13, 2016
- Code update to fix unit and integration test failures
magento-team pushed a commit that referenced this issue May 13, 2016
- Code updates based on review comments
- Updates to fix failing unit tests
magento-team pushed a commit that referenced this issue May 13, 2016
magento-team pushed a commit that referenced this issue May 13, 2016
- Code review comment updates.
- Added unit test for PathBuilder.php
magento-team pushed a commit that referenced this issue May 13, 2016
- Code updates based on review comments
- Enhanced PathBuilder::build() logic.
- Added couple of new error scenario tests to PathBuilderTest.php
magento-team pushed a commit that referenced this issue May 13, 2016
- Code review comment update.
- Consider ["extra"]["map"] section absence in base package a valid scenario
magento-team pushed a commit that referenced this issue May 13, 2016
- Minor update to address code review comment.
- Moved variable assignment towards end of the block
magento-team pushed a commit that referenced this issue May 13, 2016
@piotrekkaminski
Copy link
Contributor

This should be fixed in the upcoming 2.1 version. please try on the develop branch.

@rafaelstz
Copy link
Member

rafaelstz commented Nov 29, 2016

Did not be fixed in 2.1 CE


Error from Updater Application Cron Script:

Found non-writable path(s):
/www/www.mystore.com/html/app/design/adminhtml/Magento
/www/www.mystore.com/html/app/design/frontend/Magento

Is necessary to create these empty folders to continue.

magento-engcom-team pushed a commit that referenced this issue Apr 8, 2019
[MPI] Braintree payment method not supported in multi-shipping
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

5 participants