-
Notifications
You must be signed in to change notification settings - Fork 197
Migration process kills automatically while migrating from magento 1.9.2.4 to magento 2.1.0. #341
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
Comments
#303 similar issue |
Still getting error100% [============================] Remaining Time: 1 sec [Exception] ========================= Then changed the max limit for mysql, again the process got killed ===========
|
increased RAM to 4.5 GB, still that process kills itself. bash-4.1$ php bin/magento migrate:data vendor/magento/data-migration-tool/etc/ce-to-ce/1.9.2.4/config.xml ======= |
Hi I too getting the same error and I dont find way to proceed to next step: Please help us to resolve this Here is the error log: [5680233.641853] php[3367]: segfault at 7ffd4c8e0ff8 ip 00007f1d061d9c15 sp 00007ffd4c8e1000 error 6 in libpcre.so.3.13.1[7f1d061bc000+3d000] |
php bin/magento migrate:data -r vendor/magento/data-migration-tool/etc/ce-to-ce/1.9.2.4/config.xml
========
[2017-08-01 07:14:55][INFO][mode: data][stage: data migration][step: Map Step]: started
32% [=========>------------------] Remaining Time: 2 mins Killed
-bash-4.1$
after some browsing, got a clue to check kernel logs
========
CT-26626-bash-4.1# dmesg | grep php
[65925374.412442] Out of memory in UB 26626: OOM killed process 12514 (php) score 0 vm:2330532kB, rss:1793452kB, swap:0kB
[65926087.231422] Out of memory in UB 26626: OOM killed process 12799 (php) score 0 vm:2323364kB, rss:1788396kB, swap:0kB
[65926338.670874] Out of memory in UB 26626: OOM killed process 12888 (php) score 0 vm:2328488kB, rss:1792244kB, swap:0kB
Already provided 2 GB limit for php.
===============
php -ini | grep memory_limit
memory_limit => 2G => 2G
1#
I watched RAM usage using watch command, the usage increased with in 2 secounds from 1 GB to 2.5 GB GB. Server has 2.5 GB total RAM.
The text was updated successfully, but these errors were encountered: