-
Notifications
You must be signed in to change notification settings - Fork 197
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
'Remaining Time: 5 days' then 'MySQL server has gone away' during migration from Magento 1.7.0.2 via Docker #17
Comments
Please show migration process output in debug mode: |
Thanks for the response. Here's the output with debugging on:
The migration hangs after that final line of output. |
hard to say, need additional data... |
I have same problem. I checked customer_entity table and It has 45157 records. |
I have 17105 rows in the |
Hi
url_rewrite_id, store_id, id_path, request_path, target_path, is_system, options, description, category_id, product_id |
Hello, i also had this problem with customer step that was blocking at 0% (32K records). |
@JoJuhasz thank you, solved the same problem for me. About 90k customers |
@JoJuhasz Thanks - this fixed things for me too. Much appreciated. 30k records. |
I can successfully migrate settings from my Magento 1.7.0.2 database, having gone through the process of tweaking the appropriate mappings file.
When running the data migration, all the integrity checks pass. However, when the tool reaches [stage: data migration][step: Customer Attributes step], the output announces "Remaining Time: 5 days" and does not progress past 0%.
The source database is on the same DB server as the target. However, I'm using a docker setup as per http://mageinferno.com/blog/magento-2-development-docker-os-x which may be causing issues.
I'm running the data migration tool in a bash terminal started using docker exec.
It seems as if the docker setup might have something to do with this problem, although I haven't come across any issues during normal Magento 2 operation, or the settings step of the migration, which completes very quickly.
EDIT: During this apparently static phase of the migration tool operation, there are no MySQL processes shown by
SHOW PROCESSLIST
.The text was updated successfully, but these errors were encountered: