Magento compilation hangs!
running bin/magento setup:di:compile hangs at 14% forever. Already allocated 1G RAM and incrased execution time 18000
running again with
bin/magento setup:di:compile -vvv
after 20 minutes
Compilation was started.
Proxies code generation... 0/7 [>---------------------------] 0% 1 sec 61.2
MiProxies code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 M
Repositories code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 MiB
magento2 compiler
asked Apr 1 '16 at 17:16
fefefefe
4122821
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 2 more comments
running bin/magento setup:di:compile hangs at 14% forever. Already allocated 1G RAM and incrased execution time 18000
running again with
bin/magento setup:di:compile -vvv
after 20 minutes
Compilation was started.
Proxies code generation... 0/7 [>---------------------------] 0% 1 sec 61.2
MiProxies code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 M
Repositories code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 MiB
magento2 compiler
asked Apr 1 '16 at 17:16
fefefefe
4122821
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
2
not sure if that leads somewhere, but could you try to execute it with bin/magento setup:di:compile -vvv ? This should trigger the debug output. Maybe you can find something in there
– David Verholen
Apr 1 '16 at 17:20
Do you have xdebug enabled? If you, could you try to disable it?
– BuskaMuza
Apr 1 '16 at 23:47
no I do not have xdebug
– fefe
Apr 2 '16 at 6:14
4
Did you ever find a resolution to this? I'm experiencing the same issue. Stuck at 14% onRepositories code generation... 1/7 [====>------------------] 14% 7 secs 44.0 Mib. I've tried allocating some more ram to my VM and trying my old Ubuntu 14.04 vm and the new Ubuntu 16.04, both with PHP7 (no xdebug).
– jmbertucci
Sep 7 '16 at 5:35
3
Any luck on this one? I'm getting the same issue:Repositories code generation... 1/7 [====>-----------------------] 14% 16 secs 87.5 MiB
– Danny Nimmo
Sep 20 '16 at 10:24
|
show 2 more comments
running bin/magento setup:di:compile hangs at 14% forever. Already allocated 1G RAM and incrased execution time 18000
running again with
bin/magento setup:di:compile -vvv
after 20 minutes
Compilation was started.
Proxies code generation... 0/7 [>---------------------------] 0% 1 sec 61.2
MiProxies code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 M
Repositories code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 MiB
magento2 compiler
asked Apr 1 '16 at 17:16
fefefefe
4122821
running bin/magento setup:di:compile hangs at 14% forever. Already allocated 1G RAM and incrased execution time 18000
running again with
bin/magento setup:di:compile -vvv
after 20 minutes
Compilation was started.
Proxies code generation... 0/7 [>---------------------------] 0% 1 sec 61.2
MiProxies code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 M
Repositories code generation... 1/7 [====>-----------------------] 14% 2 mins 70.2 MiB
magento2 compiler
magento2 compiler
asked Apr 1 '16 at 17:16
fefefefe
4122821
asked Apr 1 '16 at 17:16
fefefefe
4122821
edited Apr 1 '16 at 17:34
fefe
asked Apr 1 '16 at 17:16
fefefefe
4122821
asked Apr 1 '16 at 17:16
fefefefe
4122821
asked Apr 1 '16 at 17:16
fefefefe
4122821
4122821
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
2
not sure if that leads somewhere, but could you try to execute it with bin/magento setup:di:compile -vvv ? This should trigger the debug output. Maybe you can find something in there
– David Verholen
Apr 1 '16 at 17:20
Do you have xdebug enabled? If you, could you try to disable it?
– BuskaMuza
Apr 1 '16 at 23:47
no I do not have xdebug
– fefe
Apr 2 '16 at 6:14
4
Did you ever find a resolution to this? I'm experiencing the same issue. Stuck at 14% onRepositories code generation... 1/7 [====>------------------] 14% 7 secs 44.0 Mib. I've tried allocating some more ram to my VM and trying my old Ubuntu 14.04 vm and the new Ubuntu 16.04, both with PHP7 (no xdebug).
– jmbertucci
Sep 7 '16 at 5:35
3
Any luck on this one? I'm getting the same issue:Repositories code generation... 1/7 [====>-----------------------] 14% 16 secs 87.5 MiB
– Danny Nimmo
Sep 20 '16 at 10:24
|
show 2 more comments
2
not sure if that leads somewhere, but could you try to execute it with bin/magento setup:di:compile -vvv ? This should trigger the debug output. Maybe you can find something in there
– David Verholen
Apr 1 '16 at 17:20
Do you have xdebug enabled? If you, could you try to disable it?
– BuskaMuza
Apr 1 '16 at 23:47
no I do not have xdebug
– fefe
Apr 2 '16 at 6:14
4
Did you ever find a resolution to this? I'm experiencing the same issue. Stuck at 14% onRepositories code generation... 1/7 [====>------------------] 14% 7 secs 44.0 Mib. I've tried allocating some more ram to my VM and trying my old Ubuntu 14.04 vm and the new Ubuntu 16.04, both with PHP7 (no xdebug).
– jmbertucci
Sep 7 '16 at 5:35
3
Any luck on this one? I'm getting the same issue:Repositories code generation... 1/7 [====>-----------------------] 14% 16 secs 87.5 MiB
– Danny Nimmo
Sep 20 '16 at 10:24
2
2
not sure if that leads somewhere, but could you try to execute it with bin/magento setup:di:compile -vvv ? This should trigger the debug output. Maybe you can find something in there
– David Verholen
Apr 1 '16 at 17:20
not sure if that leads somewhere, but could you try to execute it with bin/magento setup:di:compile -vvv ? This should trigger the debug output. Maybe you can find something in there
– David Verholen
Apr 1 '16 at 17:20
Do you have xdebug enabled? If you, could you try to disable it?
– BuskaMuza
Apr 1 '16 at 23:47
Do you have xdebug enabled? If you, could you try to disable it?
– BuskaMuza
Apr 1 '16 at 23:47
no I do not have xdebug
– fefe
Apr 2 '16 at 6:14
no I do not have xdebug
– fefe
Apr 2 '16 at 6:14
4
4
Did you ever find a resolution to this? I'm experiencing the same issue. Stuck at 14% on
Repositories code generation... 1/7 [====>------------------] 14% 7 secs 44.0 Mib. I've tried allocating some more ram to my VM and trying my old Ubuntu 14.04 vm and the new Ubuntu 16.04, both with PHP7 (no xdebug).– jmbertucci
Sep 7 '16 at 5:35
Did you ever find a resolution to this? I'm experiencing the same issue. Stuck at 14% on
Repositories code generation... 1/7 [====>------------------] 14% 7 secs 44.0 Mib. I've tried allocating some more ram to my VM and trying my old Ubuntu 14.04 vm and the new Ubuntu 16.04, both with PHP7 (no xdebug).– jmbertucci
Sep 7 '16 at 5:35
3
3
Any luck on this one? I'm getting the same issue:
Repositories code generation... 1/7 [====>-----------------------] 14% 16 secs 87.5 MiB– Danny Nimmo
Sep 20 '16 at 10:24
Any luck on this one? I'm getting the same issue:
Repositories code generation... 1/7 [====>-----------------------] 14% 16 secs 87.5 MiB– Danny Nimmo
Sep 20 '16 at 10:24
|
show 2 more comments
2 Answers
2
active
oldest
votes
I just fixed this exact error. I disabled all my 3rd party modules one by one and surprisingly the compile was still hanging up in the same spot.
The solution to get compiling to work for me was to delete all the module files using the command rm -rf app/code/* from the Magento directory.
I'm not sure why disabled modules affect compilation, but this will be useful for others to know. Also, this should go without saying, make sure you back up your app/code/ directory before hand or you can try deleting/moving one module at a time to find out which was causing the issue.
answered Jun 15 '17 at 22:46
jamiljamil
564425
add a comment |
From command prompt type
php bin/magento setup:di:compile [enter]
you will see the error.
In my case I found the error
"cannot declare interface MagentoBackendAppConfigInterface, because
the name is already in use in
vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface"
then I change the namespace "MagentoBackendApp" to "MagentoCheckoutHelperMagentoBackendApp" in vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface.php
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
answered Dec 23 '16 at 15:06
user48637user48637
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f109067%2fmagento-compilation-hangs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just fixed this exact error. I disabled all my 3rd party modules one by one and surprisingly the compile was still hanging up in the same spot.
The solution to get compiling to work for me was to delete all the module files using the command rm -rf app/code/* from the Magento directory.
I'm not sure why disabled modules affect compilation, but this will be useful for others to know. Also, this should go without saying, make sure you back up your app/code/ directory before hand or you can try deleting/moving one module at a time to find out which was causing the issue.
answered Jun 15 '17 at 22:46
jamiljamil
564425
add a comment |
I just fixed this exact error. I disabled all my 3rd party modules one by one and surprisingly the compile was still hanging up in the same spot.
The solution to get compiling to work for me was to delete all the module files using the command rm -rf app/code/* from the Magento directory.
I'm not sure why disabled modules affect compilation, but this will be useful for others to know. Also, this should go without saying, make sure you back up your app/code/ directory before hand or you can try deleting/moving one module at a time to find out which was causing the issue.
answered Jun 15 '17 at 22:46
jamiljamil
564425
add a comment |
I just fixed this exact error. I disabled all my 3rd party modules one by one and surprisingly the compile was still hanging up in the same spot.
The solution to get compiling to work for me was to delete all the module files using the command rm -rf app/code/* from the Magento directory.
I'm not sure why disabled modules affect compilation, but this will be useful for others to know. Also, this should go without saying, make sure you back up your app/code/ directory before hand or you can try deleting/moving one module at a time to find out which was causing the issue.
answered Jun 15 '17 at 22:46
jamiljamil
564425
I just fixed this exact error. I disabled all my 3rd party modules one by one and surprisingly the compile was still hanging up in the same spot.
The solution to get compiling to work for me was to delete all the module files using the command rm -rf app/code/* from the Magento directory.
I'm not sure why disabled modules affect compilation, but this will be useful for others to know. Also, this should go without saying, make sure you back up your app/code/ directory before hand or you can try deleting/moving one module at a time to find out which was causing the issue.
answered Jun 15 '17 at 22:46
jamiljamil
564425
answered Jun 15 '17 at 22:46
jamiljamil
564425
answered Jun 15 '17 at 22:46
jamiljamil
564425
answered Jun 15 '17 at 22:46
jamiljamil
564425
564425
add a comment |
add a comment |
From command prompt type
php bin/magento setup:di:compile [enter]
you will see the error.
In my case I found the error
"cannot declare interface MagentoBackendAppConfigInterface, because
the name is already in use in
vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface"
then I change the namespace "MagentoBackendApp" to "MagentoCheckoutHelperMagentoBackendApp" in vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface.php
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
answered Dec 23 '16 at 15:06
user48637user48637
1
add a comment |
From command prompt type
php bin/magento setup:di:compile [enter]
you will see the error.
In my case I found the error
"cannot declare interface MagentoBackendAppConfigInterface, because
the name is already in use in
vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface"
then I change the namespace "MagentoBackendApp" to "MagentoCheckoutHelperMagentoBackendApp" in vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface.php
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
answered Dec 23 '16 at 15:06
user48637user48637
1
add a comment |
From command prompt type
php bin/magento setup:di:compile [enter]
you will see the error.
In my case I found the error
"cannot declare interface MagentoBackendAppConfigInterface, because
the name is already in use in
vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface"
then I change the namespace "MagentoBackendApp" to "MagentoCheckoutHelperMagentoBackendApp" in vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface.php
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
answered Dec 23 '16 at 15:06
user48637user48637
1
From command prompt type
php bin/magento setup:di:compile [enter]
you will see the error.
In my case I found the error
"cannot declare interface MagentoBackendAppConfigInterface, because
the name is already in use in
vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface"
then I change the namespace "MagentoBackendApp" to "MagentoCheckoutHelperMagentoBackendApp" in vendormagentomodule-checkoutHelperMagentoBackendAppConfigInterface.php
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
answered Dec 23 '16 at 15:06
user48637user48637
1
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
edited Dec 23 '16 at 15:21
Raphael at Digital Pianism
53.4k19112270
53.4k19112270
answered Dec 23 '16 at 15:06
user48637user48637
1
answered Dec 23 '16 at 15:06
user48637user48637
1
answered Dec 23 '16 at 15:06
user48637user48637
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f109067%2fmagento-compilation-hangs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
not sure if that leads somewhere, but could you try to execute it with bin/magento setup:di:compile -vvv ? This should trigger the debug output. Maybe you can find something in there
– David Verholen
Apr 1 '16 at 17:20
Do you have xdebug enabled? If you, could you try to disable it?
– BuskaMuza
Apr 1 '16 at 23:47
no I do not have xdebug
– fefe
Apr 2 '16 at 6:14
4
Did you ever find a resolution to this? I'm experiencing the same issue. Stuck at 14% on
Repositories code generation... 1/7 [====>------------------] 14% 7 secs 44.0 Mib. I've tried allocating some more ram to my VM and trying my old Ubuntu 14.04 vm and the new Ubuntu 16.04, both with PHP7 (no xdebug).– jmbertucci
Sep 7 '16 at 5:35
3
Any luck on this one? I'm getting the same issue:
Repositories code generation... 1/7 [====>-----------------------] 14% 16 secs 87.5 MiB– Danny Nimmo
Sep 20 '16 at 10:24