4

I have configured my magento 2.2.3 in server and checked the mode. It was "default". Then I tried to change the mode to production with this command,

php bin/magento deploy:mode:set production

After executing the above command, some repositories and proxy generation scripts are automatically executed and the "Compilation completed" message had shown. After that "Starting deployment of static content" message showed and it still showing after 30-40 minutes. Is there anything to do to complete the step?

Note: I have enabled the css minify, js minify, merge and bundling from magento admin.

Server: Digital ocean with 8 GB RAM and 4 core processor.

Improve this question

2 Answers 2

Reset to default
1

When you got stuck then cancel that process by ctrl+c.

By doing that you can get your production mode set perfectly but then you will need to fix the deploy error.

Following are the steps to track the error.

Run the following command:

php bin/magento setup:static-content:deploy -vvv

By doing that you can see the all processes which is performing at backend and then when it stops then you can check that module. The error must come from that module. So, you can either disable it or fix it.

You can disable it temporarily and then run the deploy command again to check if there any other error or not. If deploy process don't stuck then you will need to fix that disable extension/module.

Improve this answer
0

Do you see anything in your system.log or exception.log? The issues I've run into the most with static content deployment have been permission or LESS related. Also, is this a custom theme or Luma / Blank?

Improve this answer
3
  • Nothing found in system and exception log files. And the theme is default luma. in debug.log file has this content code main.DEBUG: cache_invalidate: {"method":"GET","url":"http:/","invalidateInfo":{"tags":["interception","CONFIG"],"mode":"matchingTag"}} [] code
    – Arun SS
    Commented Mar 27, 2018 at 11:57
  • When I try to "bin/magento setup:static-content:deploy", In this section it stucks. code adminhtml/Magento/backend/en_US 1804/2119 =======================>---- 85% % 13 secs
    – Arun SS
    Commented Mar 27, 2018 at 12:13
  • What happens when you run the site in developer mode? If there's an issue compiling LESS, running the site in developer mode with frontend LESS compilation enabled may help you flush out the problem. Do you see anything in your /var/log/apache2/error.log file?
    – Harry Manback
    Commented Mar 29, 2018 at 2:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.